Bridged tokens use chain-specific contracts because each network keeps its own ledger. A bridge carries value between ledgers by locking or burning tokens on one side and crediting a mapped representation on the other.
- A token’s ticker does not identify its contract.
- Lock-and-mint keeps the destination supply backed by source-chain assets.
- Check the destination contract and app compatibility before sending.
Each chain needs its own token contract
Ethereum and Mantle Network record balances separately, so an ERC-20 on Ethereum cannot simply appear at the same address on Mantle. The receiving network needs a local contract that its wallets and apps can read and transfer.
If you need to move a supported asset between Ethereum and Mantle Network, the Mantle Bridge transfer uses the canonical route for that deposit or withdrawal. Check which representation arrives and whether your app accepts it; matching names and tickers alone do not establish that two contracts are interchangeable.
A token’s symbol, such as USDC, is only a label. The contract address and the network together identify the asset your app will actually use. This distinction matters when an app supports one bridged version but not another, even if both display the same ticker.
Lock-and-mint ties the two representations together
In a lock-and-mint bridge, the source transaction places tokens in an escrow contract, then a verified cross-chain message tells the destination bridge to mint or release the mapped amount. The destination token is a representation backed by assets held on the source chain; it is not the original Ethereum contract copied onto another network.
For example, deposit 100 supported ERC-20 tokens from Ethereum and, if the route has a one-to-one mapping with no token-level fee, the destination can credit 100 units of its mapped representation. The bridge message carries details such as the source token, amount, and recipient, so the destination bridge can apply the correct mapping and prevent the same deposit from being credited twice.
On the return trip, the destination representation is typically burned or removed from circulation, and a confirmed withdrawal message lets the source bridge release the escrowed tokens. That supply link is the key trade-off: users rely on the bridge contracts and the process that verifies messages between chains to keep releases and credits in sync.
Match the token contract to the app you need
Before bridging for a specific app, check the app’s supported network and token contract, then compare them with the destination asset shown by the bridge. I would use the app’s own token address or a verified network explorer entry as the match criterion, rather than choosing by ticker or token logo.
- Confirm the destination network and receiving address.
- Compare the destination token contract with the app’s accepted contract.
- Check whether the route is a bridge transfer or a swap into a different asset.
- Keep enough gas on the chain where each transaction or claim must be sent.
MNT illustrates why network context matters: a token called MNT on one chain is not automatically the same contract or usable balance as MNT on another. Mantle Bridge handles transfers through its supported asset mappings, while the destination app decides which token contracts it accepts.
Fees and waiting time depend on the route
A bridge transfer usually involves network gas, and an ERC-20 deposit may also require an approval transaction. The source-chain transaction and any later destination or withdrawal claim can each require gas; the bridge interface should show the route’s current estimate before you confirm.
Deposits and withdrawals can have different settlement steps because each direction starts on a different ledger and must be recognized by the other chain. For your task, check the transaction status and the bridge’s current instructions, especially if a withdrawal requires a later proof or claim. Do not treat a displayed destination balance as proof that another chain’s app will accept that representation.
Questions to check before using a bridged token
Why does my wallet show the right ticker but the app cannot use it?
The app may be checking a specific contract address on a specific network. A bridged token can share a ticker with another version while using a different contract, so compare the address and chain shown in the app’s supported-token details with the token you received.
Does bridging a token convert it into another token?
A bridge transfer generally moves value through a mapped representation; it does not by itself exchange one asset for another. If the destination app needs a different token, you may need a separate swap, which has its own exchange rate, fees, and execution risk.