Manta BridgeWhat information does the token-list submission need?
The documented token-list entry includes Manta-side metadata, root-chain metadata, and a pull request into the Manta Pacific mainnet token-list file.
Manta's token-list documentation shows the JSON shape and says to add token information to the manta-pacific-mainnet-token-list.json file and submit a PR.
| Submission field | What it represents | Source rule |
|---|---|---|
| chainId | Manta Pacific chain identifier for the listed token entry. | The documented example uses Chain ID 169. |
| Root chain | The Ethereum-side origin chain for the canonical token. | Recorded in extension fields such as rootChainId and rootChainURI. |
| Root token address | The ERC-20 contract address on the root chain. | Recorded as rootAddress in the extension object. |
| Manta token address | The token contract address on Manta Pacific. | Recorded as address and tokenId in the Manta-side entry. |
| Submission method | Add the token information to the mainnet token-list JSON file. | Submit a pull request after adding the entry. |
Is listing permissioned or open via pull request?
The documented process is pull-request based: add token information to the mainnet token-list JSON file and submit a PR.
That does not mean every submitted token is automatically accepted or safe; it means the public documented workflow is a repository change process. Token teams should prepare accurate chain IDs, root addresses, Manta token addresses, metadata, decimals, and logo fields before submission.
For developer automation after listing, read how developers use the Manta Bridge JS SDK for ETH and ERC-20 transfers. For current user-facing token scope, use Manta native bridge supported tokens.
Does listing affect both directions of the bridge?
A correct token-list entry helps the native bridge identify the token relationship between Ethereum and Manta Pacific, but transfers still depend on the actual bridge contracts and app support.
The entry connects Manta-side metadata with root-chain metadata. That relationship is relevant for deposits and withdrawals, but a list entry should not be treated as a security audit, liquidity guarantee, or promise that every wallet and app will display the token perfectly.
The SDK bridge documentation shows the separate deposit and withdrawal methods developers may use once token configuration is in place. After listing, users can also discover use cases through what to do after bridging to Manta Pacific.
Submit clean metadata: list the real root and Manta token details, then test deposits and withdrawals in Manta Bridge before directing users.
Open BridgeHow does a token team get an ERC-20 listed on Manta Native Bridge?
Manta’s documentation says to add token information similar to the documented JSON shape in the manta-pacific-mainnet-token-list.json file and submit a pull request. Use the project’s real deployed contracts and metadata, not placeholder addresses.
What information does the token-list submission need?
The documented entry includes Manta-side fields such as chainId, chainURI, tokenId, tokenType, address, name, symbol, decimals, dates, and logoURI, plus extension fields for rootChainId, rootChainURI, and rootAddress.
Is listing permissioned or open via pull request?
The public documentation describes a pull request workflow. It tells teams to add token information to the mainnet token-list JSON file and submit a PR, which implies a reviewable repository process rather than a private form-only path.
Does listing affect both directions of the bridge?
The token-list entry describes the relationship between the root-chain token and the Manta Pacific token. That relationship is relevant to bridge display and configuration, while actual deposits and withdrawals still depend on bridge contracts, app support, and correct token setup.
Where is the token-list process documented?
The process is documented on Manta Network’s Native Bridge page titled “How to list token on Native Bridge.” That page includes the repository link, example JSON structure, and instruction to submit a pull request.