> For the complete documentation index, see [llms.txt](https://docs.liquidapps.io/liquidapps-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liquidapps.io/liquidapps-documentation/cross-chain-bridges/getting-started-with-liquidbridge/eosio-atomic-assets-less-than-greater-than-erc1155-non-fungible-tokens/evm-side-setup/setup-evm-erc1155-contract.md).

# Setup EVM ERC1155 Contract

We're going to setup our ERC1155 first, then we'll deploy the atomictokenpeg1155 contract.

![](/files/-MlL_8kXsmdUznZWd-Er)

Click `ERC11555Tradeable.sol` then move to the deployment & run transactions tab.

![](/files/-MlLcpsDG2-BmuhVcXAO)

Now to use metamask we'll change the ENVIRONMENT dropdown to `Injected Web3`

![](/files/-MlLc9TpWHOAwn274mZx)

Make sure in metamask you have your token account selected and that it is connected, take note of the last 4 digits of your address and ensure under the `ACCOUNT` tab the same account is selected.

![](/files/-MlLcCzGq0pMw2_TYneC)

Specify a name, symbol, default token URI, and the proxy address and click `Transact`.  The default URI will be used if not URI is specified in the creation of an NFT.

Example used:

* Super Cool NFT Bridge
* COOL
* <https://cloudflare-ipfs.com/ipfs/QmSXDsFeNaPa3CJKmn8WKBnA421Zv5r3Ra8n71LZhvEi9s/blocks/1mb.png>
* 0x5bCc21acdF2f15A13721E8eB93F72Ac8B85Cb76B

{% hint style="info" %}
despite the quotes seen below for the URI, the quotes are not needed
{% endhint %}

![](/files/-MlLvhF3HozvbpCpKN5X)

Click **Confirm**

In the console you should see the creation and if you click on the transaction you can copy and paste it into <https://rinkeby.etherscan.io/>

![](/files/-MlLw-nAPPecHAn_ICnZ)

From here we can see that a contract was created, let's go there and save the contract's address.

![](/files/-MlLwC89EVbHQzZksMNW)

If you click the Contract tab, you should not need to verify the source code.  If it's not verified, you can check the `/contracts/eth/flat` folder for a flattened version of the contract. Can also use this site to submit the ABI-encoded constructor arguments <https://abi.hashex.org/>.

{% hint style="info" %}
If you use the ABI hashex, do not add any quotes "" around the strings, if you do you'll get an error when trying to verify.
{% endhint %}

If you're here it means you have the green check, **congrats**!!

![](/files/-MlM7Myh4axvSXzeUfSi)

Now we'll transfer ownership of the NFT contract to the bridge contract.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.liquidapps.io/liquidapps-documentation/cross-chain-bridges/getting-started-with-liquidbridge/eosio-atomic-assets-less-than-greater-than-erc1155-non-fungible-tokens/evm-side-setup/setup-evm-erc1155-contract.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.