Mantle Bridge moves tokens through two chain transactions

Mantle Bridge moves funds from your wallet by having you approve and sign a transaction on the source network, then settling the transfer on the destination network. For a deposit from Ethereum to Mantle, that means the assets leave your Ethereum wallet first; a corresponding balance becomes available at your address on Mantle after the deposit message is processed. The two balances sit on separate chains, so the transfer is not a wallet sending tokens directly across a network boundary.

The process matters because each signature does a different job. For an ERC-20 token, an approval lets the bridge contract spend a specified amount; it does not move the funds by itself. The deposit is a separate transaction. Mantle Bridge follows that distinction in its deposit flow, and it is useful to check the token, amount, destination address and fee before signing each step.

How does a Mantle Bridge deposit move funds?

A deposit sends assets into the bridge’s Ethereum contracts, then delivers the corresponding mapped asset to your address on Mantle. First connect the wallet that holds the funds and select Ethereum as the source and Mantle as the destination. Choose a supported asset and amount. The receiving address is usually the connected wallet’s address, but check it before confirming.

If you are depositing an ERC-20 such as USDC, the contract may need an allowance before it can transfer the tokens. Your wallet will ask you to approve spending; after that transaction confirms, you still need to submit the deposit transaction. ETH deposits do not use an ERC-20 approval, but they still require a deposit signature and Ethereum gas.

On the source chain, the bridge contract holds the deposited backing asset. Once the cross-chain message is processed, the destination balance appears on Mantle as the token mapped to the Ethereum asset. This is a bridge transfer, not an exchange: if you choose the same asset on both sides, the bridge does not convert it into another token. A route that changes assets adds a swap and its exchange rate and costs.

The practical trade-off against using Ethereum directly is that you add a cross-chain settlement step, while later transactions on Mantle can use its own network and fee market. The cost is not just the bridge interface’s displayed fee: the wallet also needs enough native currency for the source transaction. Keep ETH for Ethereum gas, including any approval, and have MNT on Mantle for transactions after arrival. The asset you bridge may not pay those fees.

What happens when you withdraw from Mantle?

A withdrawal starts on Mantle and only later releases funds on Ethereum. Select Mantle as the source, Ethereum as the destination, then sign the withdrawal transaction in your wallet. The corresponding bridged balance is committed to the exit process on Mantle; it does not instantly appear in your Ethereum wallet.

The withdrawal must be included in Mantle’s state and settled on Ethereum before it can be claimed. The current flow uses a validity proof for the relevant Mantle state, which Ethereum verifies before the exit becomes ready. Proof production and Ethereum processing still take time. Older Mantle tutorials describe an optimistic-rollup challenge period, including a seven-day wait; that description reflects an earlier withdrawal model and should not be treated as a live countdown for every current withdrawal.

When the withdrawal status says it is ready, return to the same withdrawal in the bridge history, switch the wallet to Ethereum and submit the final claim. That claim is a separate Ethereum transaction and requires ETH for gas—even if the asset being withdrawn is ETH. Closing the page does not complete the claim, and starting another withdrawal does not finish the first one.

How does the canonical bridge compare with faster routes?

The canonical bridge ties the destination credit or release to the bridge’s cross-chain settlement process. That gives the user a direct path between the two networks, but it means waiting for the messages and proof or claim stages to finish. A third-party bridge or liquidity route may deliver funds sooner by providing destination-chain liquidity before the canonical exit settles. In exchange, it introduces that route’s fees, liquidity conditions and trust assumptions.

A direct wallet transfer is a different alternative: it works within one network, but cannot by itself move an Ethereum balance to Mantle. For most users who want to move the same asset and can wait for settlement, the canonical route is the clearer choice because its deposit and withdrawal steps correspond to the bridge’s own on-chain accounting. Faster liquidity can suit a time-sensitive transfer, but compare the amount received and the extra route assumptions before choosing it.

• Confirm the source and destination networks, token and receiving address.
• For ERC-20 deposits, treat approval and deposit as two separate transactions.
• Keep ETH for Ethereum transactions and MNT for Mantle transactions.
• For a withdrawal, track the original request and submit its claim when ready.

The useful signals to watch are the source transaction confirmation, the destination balance after a deposit, and the withdrawal’s proof and claim status on the way back. Those checkpoints show whether funds are still waiting for settlement or whether the wallet needs to sign the next transaction.