Manta BridgeWhat can you bridge on the native bridge?
The native bridge is for ETH and supported Ethereum ERC-20 tokens moving between Ethereum Mainnet and Manta Pacific.
Manta Bridge is the official native bridge for moving ETH and Ethereum ERC-20 tokens between Ethereum Mainnet and Manta Pacific, Manta Network's Celestia-powered Ethereum L2. In practical terms, a root asset on Ethereum Mainnet corresponds to its representation on Manta Pacific.
rootChainId: 1 for canonical bridge assets.Is every ERC-20 supported?
No. The category is Ethereum ERC-20 tokens, but the live bridge support set is curated.
The important distinction is "ERC-20 in scope" versus "ERC-20 listed right now." A token can be a normal Ethereum ERC-20 and still be absent from the native bridge UI if it has not been added to the official list.
Manta's deploy documentation also warns that fee-on-transfer or rebasing tokens are not supported because those designs can create bridge accounting problems. That is why this page does not publish an exhaustive asset list.
Where is the official token list?
The official docs point to the Manta Pacific mainnet token-list JSON and show canonical-bridge metadata for listed assets.
The Manta docs page for listing a token on Native Bridge links to manta-pacific-mainnet-token-list.json. The example includes Manta Pacific chain data, tokenType: ["canonical-bridge"], and Ethereum root-chain fields.
Use that official list and the bridge app for the current answer. A static guide should explain scope, not pose as the live token picker.
| Source | What it verifies | How to use it |
|---|---|---|
| Bridge app | The token picker and route available when you connect. | Check the exact token before signing. |
| Token-list docs | The canonical list format, including token type, address, symbol, decimals, and root metadata. | Verify support through the official list, not ERC-20 status alone. |
| Deploy docs | The deploy flow for Ethereum token representations on Manta Pacific. | Use it if you are preparing an asset for native-bridge support. |
How does a token get added?
A token generally needs Manta Pacific token metadata and, when needed, a deployed L2 token representation before it appears as a native bridge option.
The official deployment guide for deploying an Ethereum token on Manta recommends contacting the Manta team. It then outlines a developer flow: add token config, deploy on Manta mainnet, update the L2 token address, and submit a pull request.
The listing docs separately tell teams to add token information to the mainnet token-list JSON and submit a PR. For users, the takeaway is simpler: support is maintained through a token list, not granted to every Ethereum contract.
What if your token is not listed?
If the token is not listed in the native bridge, use another route only after checking support, fees, liquidity, and risk assumptions.
A non-listed token may still move through an independent provider, but that is no longer the native canonical bridge path. Third-party bridges can use different contracts, liquidity, limits, and fee models.
For route context, start with the official Manta bridge. If your asset is ETH, the cleanest starting point is the native guide on how to bridge ETH. The complete topic index is in all Manta Bridge guides.
Open Manta Bridge to check the live token picker before you bridge. The native route is canonical, but the supported token set is still a curated list.