Mantle Bridge: Check Which Token Will Arrive

To use the Mantle bridge, first choose the source and destination networks, then select the route and inspect the token shown for delivery. A canonical route transfers the same asset type across networks, where it may appear under a different token contract. A swap route also trades one asset for another. The route determines what arrives, while each transaction stage determines when it becomes available. Check both before signing: a matching ticker or dollar value does not prove that two tokens are interchangeable.

What happens when you bridge to Mantle?

For a canonical deposit, the wallet signs a transaction on the source network. If you are sending an ERC-20 token and the bridge does not already have permission to use it, the wallet asks you to approve a spending allowance first. That approval is a separate transaction; it does not move the tokens. After approval, you sign the deposit, and the bridge records the transfer so the corresponding asset can be credited on Mantle.

Think of the bridge as a cashier exchanging a ticket for a claim at another counter. The ticket is not the asset itself; the bridge’s contracts and cross-network messages record what should be released or represented on the destination. For a fuller explanation of how the mantle bridge route choice affects the transfer, see our guide to canonical and swap routes.

That process has stages. The source transaction must be confirmed, the bridge message must be processed, and the destination balance must appear in the receiving wallet. Keep the transaction record and check the destination network and address if the balance is not visible yet. A completed approval alone is not evidence that the deposit was sent.

How can you tell which token will arrive?

Read the destination token field in the route details before confirming. Check its name, ticker, and contract address where the interface provides them. The ticker is a label; the contract address identifies the token on that network. Two tokens can both display “USDC” or another familiar ticker and still be separate contracts with different issuers, backing, or app support.

For a canonical route, expect the bridge’s mapped representation of the asset you selected. For a swap route, read the destination asset and estimated output instead: the route includes a trade, so the token you receive can differ from the one you send. The quote may also change with price movement, liquidity, fees, and slippage settings. Compare the estimated amount after costs, not just the name of the route or its headline speed.

• Confirm the source and destination networks.
• Check the exact destination token and contract.
• Review the estimated amount after fees and any swap.
• Check that the wallet address and receiving app support that token.

Which route should you choose?

Choose the canonical route when your priority is to move the same asset type and you do not need a conversion as part of the transfer. It keeps the route easier to account for: one asset goes in, and its mapped version is expected on Mantle. You may still need to make a separate swap after arrival if an app requires another token.

Choose a swap route when you specifically want a different destination asset and the displayed output is acceptable. That convenience adds market execution to the transfer. A worse price, low liquidity, or slippage can reduce what arrives. Compare the full route details and consider whether making the conversion separately after bridging gives you clearer control.

Before signing, also check the wallet’s network and fee prompts. The source transaction uses that network’s gas token; later activity on Mantle needs Mantle gas. Once the transfer is underway, follow its status through the bridge interface and verify the received token on Mantle. The practical rule is simple: choose by destination contract and net amount, not by ticker alone.