> For the complete documentation index, see [llms.txt](https://docs.multichain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multichain.org/listing-and-integration/token-listing/erc20-cross-chain-options.md).
# ERC20 Cross-chain Options
**Please submit the token listing form here:** [**https://dard6erxu8t.typeform.com/to/C7RwF08A**](https://dard6erxu8t.typeform.com/to/C7RwF08A)
**Options for ERC20 cross-chain interoperability**
**Multichain V3**
{% hint style="info" %}
**In most cases, we can deploy all the needed contracts for you unless you wish to deploy yourself or have special requirements.**
{% endhint %}
| If | Then |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1️⃣ Token has already been issued on **two** or **more** chains prior to this. | We deploy [standard cross-chain contract](https://github.com/anyswap/chaindata/blob/main/deploy.md)s for you on other chains. (:smile: [Liquidity](https://app.multichain.org/#/pool) is only needed on the chains that have already issued tokens) |
| 2️⃣ Token was issued on just **one** chain and **wish to bridge** to additional chains. | We do all the work to get the bridge done by creating [standard cross-chain contract](https://github.com/anyswap/chaindata/blob/main/deploy.md)s on the destination chains. (💡No Liquidity is required) |
| 3️⃣ Token was issued on just **one** chain and **wish to bridge** to additional chains. And if you wish to create the destination contracts **yourself** and are technically **qualified.** | You can follow our deployment guide: [standard cross-chain contract](/developer-guide/how-to-develop-under-anyswap-erc20-standards.md) guide. And we will use those contracts to set up the bridge. (💡No Liquidity is required) |
| 4️⃣ Token has already been issued on **two** or **more** chains and you wish to create the destination contracts **yourself** and are technically **qualified**. | You can follow our deployment guide: standard cross-chain contract guide for the additional chains. And we will use those contracts to set up the bridge.
(😄 Liquidity is only needed on the chains that already have issued tokens)
|
| 5️⃣ Your token has tax built in or you have special requirements for your token. | You can follow our deployment guide: [standard cross-chain contract](/developer-guide/how-to-develop-under-anyswap-erc20-standards.md) guide for the additional chains. Fork our standard contract and add in extra functionalities you need. And we will use those contracts to set up the bridge. |
You can always reach us to us or fill out the form below and we'd help you decide the best option for your project.
**Free Listing Entry**
---
# 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.multichain.org/listing-and-integration/token-listing/erc20-cross-chain-options.md?ask=&goal=
```
`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.