Mantle is an Ethereum Layer 2 Network With a Canonical MNT Bridge

Walk the Ethereum-to-Mantle deposit

The Mantle canonical bridge deposit starts with MNT on Ethereum, then hands the equivalent amount to the same EVM address on Layer 2.

A parallel page documents Mantle when to use app. Before opening the transfer form, set MetaMask or Rabby Wallet to Ethereum mainnet and confirm three balances: MNT to move, ETH for execution and any MNT already committed elsewhere. Ethereum uses chain ID 1, while Mantle uses chain ID 5000. The same account appears on both networks because each uses the EVM address format. A Ledger or Trezor signer works through the connected wallet, while WalletConnect handles the session. Keep that session active until the deposit transaction receives a hash; the bridge continues processing after the browser closes. Use the account intended for receipt.

Choose the direction and amount

Set From to Ethereum and To Mantle, then select MNT rather than a similarly named asset. MNT uses 18 decimal places, so 1 MNT equals 10^18 smallest units. The interface converts the typed decimal amount into that integer quantity before asking the wallet to sign. Review the source chain, destination chain, token symbol, amount and receiving account as one complete instruction.

Approve MNT, then deposit it

Ethereum treats MNT as an ERC-20 token, so a fresh allowance produces two on-chain transactions: approval first and deposit second. The approval encodes a 20-byte spender address and a 256-bit allowance; it doesn’t move MNT. Set the spending cap at least as high as the deposit. After approval confirms, the bridge call consumes the required allowance and commits the transfer. Those two transactions use consecutive account nonces, with the later nonce exactly 1 above the earlier one when nothing else was sent between them.

Wait for the Layer 2 credit

Once the Ethereum deposit confirms, the bridge relays its cross-chain message and credits native MNT to the destination account. The bridge interface gives about 2 minutes as the typical deposit duration, although Ethereum inclusion and relay timing still determine the actual arrival. Follow the deposit entry in History and then switch the wallet to Mantle. The destination balance should rise on chain ID 5000.

Choose the bridge mode before signing

MNT route selection starts with the source and destination pair, because that choice determines the transaction type and the later exit path.

The canonical interface provides a direct Ethereum - Mantle path with an explicit Layer 1 or Layer 2 record. Bungee, Jumper and Squid Router aggregate other routes; Mantle Refuel addresses the narrower task of topping up gas. Their quotes, liquidity and displayed paths change with route conditions, while the canonical pair remains Ethereum and Mantle. For this workflow, choose MNT and the exact direction rather than accepting an automatic swap route. That keeps the output asset as MNT and leaves the later withdrawal state in the same bridge history. This boundary keeps the accounting legible.

The From and To order is the decisive field. Reversing it changes a quick deposit into a staged withdrawal, even though both forms show MNT, Ethereum and Mantle.

What happens after the Ethereum deposit is signed?

A signed Ethereum MNT deposit first becomes an Ethereum transaction, then becomes a cross-chain message that the Mantle bridge tracks through completion.

Ethereum mainnet uses chain ID 1, while Mantle mainnet uses chain ID 5000. Save the deposit hash, not only the approval hash, because the second transaction starts the bridge message. An EVM transaction hash contains 32 bytes, displayed as 64 hexadecimal digits after its prefix. Etherscan follows the Ethereum receipt, while Mantlescan follows the resulting Layer 2 activity. The bridge History view connects those records and labels the transfer as pending or completed, so a closed tab doesn’t erase the submitted operation.

The receiving account is also checkable without relying on a shortened wallet label. An EVM address contains 20 bytes, shown as 40 hexadecimal digits; adding the 2-character prefix makes the displayed address 42 characters long. Match the opening and closing characters, then inspect the complete value in the wallet. A receipt status of 1 means execution succeeded, while status 0 means the transaction reverted and created no completed deposit.

Return MNT through the withdrawal path

The Mantle withdrawal path reverses the direction, but it adds a waiting state and a separate Ethereum claim before MNT reaches Layer 1.

Initiate on Mantle

Switch the connected wallet to chain ID 5000, set From to Mantle and select MNT. Because MNT is the native asset there, the withdrawal doesn’t require an ERC-20 spending approval. Enter an amount that leaves enough MNT to pay the Layer 2 gas charge, review the Ethereum destination and sign the initiation. This transaction commits the amount to the bridge’s Layer 2 withdrawal path and creates the first of two user-facing stages.

Track the waiting state

Mantle’s official bridge states that a withdrawal to Ethereum can take up to 12 hours. The delay belongs to the optimistic settlement path: Mantle publishes the relevant state and the withdrawal waits until the bridge marks it claimable. History should move from an initiated or pending state to a claim-ready state without another transfer from the wallet. Keep the withdrawal hash because it identifies the Layer 2 action during this interval. Repeatedly starting a new withdrawal creates separate records; it doesn’t accelerate the first one.

Claim on Ethereum

When History enables the claim, switch the wallet to Ethereum mainnet, chain ID 1 and submit the Layer 1 transaction. ETH pays for this step. The claim finalizes the cross-chain message and releases the Ethereum ERC-20 MNT to the destination account. The user-facing exit therefore contains 2 on-chain stages and 2 transaction hashes: initiation on Mantle and claim on Ethereum. Treat the withdrawal as complete only after the claim receipt succeeds and the Ethereum MNT balance reflects the amount.

Gas assets at each boundary

The Mantle MNT bridge draws gas from the source chain and from Ethereum again when a return claim becomes available. An Ethereum-to-Mantle deposit consumes ETH for the approval and bridge call; it doesn’t deduct this gas from the MNT amount. A return uses MNT for Layer 2 initiation and ETH for the Layer 1 claim, giving 2 fee assets across 2 networks. Leave both balances above zero until the Layer 1 receipt shows status 1.

Confirm the destination wallet handoff

A complete Mantle bridge transfer ends with agreement among the bridge status, the destination receipt and the wallet balance for the same account. Check 3 records: the submitted amount, the successful destination event and the final balance change. On Ethereum, import the MNT ERC-20 contract 0x3c3a81e81dc49A522A592e7622A7E711c06bf354 if its balance is hidden. On Mantle, MNT appears as native currency. Both displays preserve 18 decimal places.