Why Token Support Differs by Network on Manta
Why the same ticker can represent different contracts and why chain selection matters.
Why this matters on Manta
The same ticker can exist as multiple contracts on multiple networks. Network-specific contract verification prevents one of the most common cross-chain mistakes.
Manta provides an Ethereum-compatible environment with its own network balances and application context.
Manta is part of the Ethereum scaling ecosystem. The same ticker can exist on Ethereum and on Manta as separate token contracts, so a balance seen on one network cannot be assumed to exist, or to be redeemable at the same value, on the other.
Manta: what to pay attention to
- Costs: Compare network gas with route and destination costs.
- Security: Use trusted interfaces and verify the destination before signing.
- Assets and tokens: Verify the token contract and network-specific representation.
A Manta checklist for this topic
- Keep enough native balance on Manta to pay for the transaction that starts the transfer.
- Review the final recipient address and network before confirming a cross-chain transfer.
- Confirm both the source and destination network, including whether Manta is one of them.
- Compare the quote, the minimum received amount and the total fees before signing.
Bridge from Manta
Compare network gas with route and destination costs. On the Starknet side: verify Starknet-specific asset and account details.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Manta → Starknet BRIDGE GUIDE