# EVM Side Setup

Here we're going to use <http://remix.ethereum.org/> to compile and deploy our smart contracts

* `binancetokenpeg.sol`
* `BEP20TokenImplementation.sol`

Then we will use <https://testnet.bscscan.com/> to verify our smart contract code and enable use to read/write to the contract.

Let's roll.

First let's upload all of the files in `./contracts/eth`

* BEP20TokenImplementation.sol
* binancetokenpeg.sol
* IBEP20.sol
* ApproveAndCallFallBack.sol
* IOwned.sol
* link.sol

![](/files/-Ma06C6_TXNmCXgG-ov9)

Now we're going to do some shenaningans to get this thing to compile.

* change the compiler version in the contract files on all the contracts above to `pragma solidity ^0.8.0;`

{% hint style="info" %}
Going up seems better than down in this case: <https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/math/SafeMath.sol#L6>&#x20;
{% endhint %}

* change import in BEP20TokenImplementation&#x20;

```
import "./IBEP20.sol";
```

* change import in binancetokenpeg

```
import "./link.sol";
import "./IBEP20.sol";
import "./IOwned.sol";
```

`BEP20TokenImplementation.sol` and `binancetokenpeg.sol` should both compile when you click on them.

Onto round 2.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.liquidapps.io/liquidapps-documentation/cross-chain-bridges/getting-started-with-liquidbridge/eosio-less-than-greater-than-evm/evm-side-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.