Move ETH, MNT, or supported tokens between Ethereum and Mantle Network in nine steps with Mantle Bridge, provided your wallet has gas for the transactions. To bridge from Ethereum to Mantle Network or back, use the Mantle Bridge, the official bridge app. Deposits follow Ethereum confirmation; withdrawals need a later Ethereum claim.

• Use the five deposit steps to move assets to Mantle, or the four withdrawal steps to return them to Ethereum.
• ETH pays Ethereum gas; native MNT pays gas on Mantle.
• Keep ETH for a withdrawal claim even when the asset you are withdrawing is ETH.

What Mantle Bridge transfers between the networks

Mantle Bridge moves an asset between Ethereum and Mantle Network, an Ethereum layer 2 where transactions are processed separately from Ethereum. Moving funds into Mantle is called a deposit; moving them back to Ethereum is a withdrawal. The bridge handles ETH, MNT, and supported tokens, but you must check that your particular token is available in the direction you want.

A bridge transfer is not a swap. If you deposit ETH, you receive its corresponding representation on Mantle, not MNT; bridging ETH to Mantle will not give you the token that pays Mantle gas. For a typical token deposit, a contract holds the asset on Ethereum while the corresponding balance becomes available on Mantle. A withdrawal reverses that process after Mantle’s settlement is verified on Ethereum.

Your wallet can show the same address on both networks while holding separate balances on each. Switching the wallet’s network changes which balance you see; it does not move funds. That distinction matters when a transfer has completed but the destination balance appears to be missing.

A wallet and gas must be ready before you start

You need an Ethereum compatible wallet that can connect to the bridge and use Mantle Network. WalletConnect is one way to connect a supported wallet. Mantle’s mainnet chain ID is 5000; if you add the network manually, take its current settings from Mantle’s documentation rather than an unverified search result.

Gas is the network charge for sending a transaction. Keep ETH on Ethereum for a deposit, any required token approval, and a later withdrawal claim. Keep native MNT on Mantle for a withdrawal or for using assets after a deposit. If you arrive with only bridged ETH or a stablecoin and no MNT, you will need to obtain MNT before you can send or use those assets on Mantle.

Before signing, check the bridge address, the network shown by your wallet, the token’s contract and the receiving address. A token symbol alone may identify different contracts on different networks. Never enter your recovery phrase or private key into a bridge site.

Five deposit steps move assets from Ethereum to Mantle

A deposit starts with your asset on Ethereum and ends when its corresponding balance appears on Mantle. These five steps cover both ETH and supported ERC-20 tokens, including MNT held as a token on Ethereum.

1. Connect the wallet holding the asset on Ethereum. Use the account that actually holds the ETH, MNT, or supported token you intend to transfer. The bridge transaction must be signed by that account, which also needs ETH for Ethereum gas.

2. Choose Ethereum as the source and Mantle as the destination. Select the asset and enter an amount, leaving enough ETH in your Ethereum wallet to pay for any required transactions. Check the receiving address before continuing; for a first transfer, using your own wallet address keeps the destination easy to verify.

3. Approve the token if your wallet requests an ERC-20 allowance. An allowance lets the bridge contract spend the specified token amount from your wallet. ETH deposits generally do not need this separate token approval, while ERC-20 deposits may; an approval costs ETH gas and does not itself bridge the token.

4. Sign the deposit transaction. Read the amount and Ethereum gas estimate in your wallet before confirming. This is the transaction that starts the transfer, so save its transaction hash—the identifier you can use to look it up later.

5. Check the balance on Mantle after processing. Ethereum must include the deposit transaction before Mantle can credit the corresponding asset. Switch your wallet to Mantle and check the receiving address; if the transaction succeeded but the token is hidden, add its verified Mantle token contract to your wallet.

Four withdrawal steps return assets to Ethereum

A withdrawal begins on Mantle and finishes with a separate claim on Ethereum. Plan for the gap between those transactions: the Mantle transaction records your exit, but it does not immediately put the asset in your Ethereum wallet.

1. Connect the wallet holding the asset on Mantle. Confirm that it also holds native MNT to pay Mantle gas. Choose Mantle as the source, Ethereum as the destination, and the supported asset and amount you want to withdraw.

2. Sign the withdrawal on Mantle. This transaction starts the return and records a withdrawal message. Save its transaction hash so you can identify the same withdrawal when you come back to complete it.

3. Wait until the withdrawal is ready to claim. Mantle’s current validity rollup uses a proof verified on Ethereum before the withdrawal can be finalized. Check the withdrawal’s status; a confirmed transaction on Mantle alone does not mean the funds are available on Ethereum.

4. Claim the withdrawal on Ethereum. Once it is ready, use the same wallet to sign the Ethereum claim and pay its gas in ETH. Check your Ethereum balance after that transaction confirms. The funds awaiting release cannot pay for their own claim, even if you are withdrawing ETH.

Time and fees depend on the transactions you send

Mantle Bridge deposits commonly take minutes after the Ethereum transaction is included, while withdrawals can take hours because proof generation and Ethereum settlement come first. Mantle’s current validity rollup does not use the older seven-day challenge period, but a withdrawal still is not instant. Network conditions and the transfer’s status determine when you can claim it.

The amount of gas you pay changes with network demand and the work each transaction performs. As an illustrative example, an ERC-20 approval using 50,000 gas plus a deposit using 150,000 gas, both at 5 gwei, would cost 0.001 ETH in Ethereum gas: 200,000 × 5 gwei. Your wallet’s estimates at signing are the figures to use; Mantle gas and a later Ethereum claim are separate costs.

If a deposit seems stuck, check whether you signed only the approval or also the deposit, then look up the deposit hash on Ethereum and the receiving address on Mantle. If a withdrawal is pending, return to that withdrawal’s status rather than starting another one. Its Ethereum claim remains a separate step.

Frequently asked questions

Can I use the same wallet address on Ethereum and Mantle?

Yes, an Ethereum compatible wallet can generally use the same account address on both networks. The balances remain separate: 100 tokens shown on Ethereum are not automatically 100 tokens on Mantle. After a transfer, switch to the destination network to inspect that address. If a completed transfer is absent from the wallet display, check the verified destination token contract.

Does depositing ETH give me MNT for Mantle gas?

No. The bridge moves the asset you selected, so an ETH deposit does not turn into MNT. Native MNT pays transaction gas on Mantle. Arrange some MNT before you need to send, swap, or withdraw an asset there; otherwise, you can see the deposited balance but cannot make a Mantle transaction with it.

Why did I sign an approval but receive nothing on Mantle?

An ERC-20 approval only gives the bridge contract permission to spend your token. It is a separate Ethereum transaction from the deposit, and it does not move the token across networks. Check your wallet’s transaction history: if the approval confirmed but there is no deposit transaction, return to the transfer and sign the deposit.

Can I cancel a withdrawal after it starts?

You can reject a wallet request before signing it. Once the withdrawal transaction is confirmed on Mantle, closing the page does not undo it. Keep its transaction hash, wait for the withdrawal to become claimable, and complete the Ethereum claim. You will need ETH in that wallet on Ethereum to pay for the final transaction.

Final checklist: Confirm the asset and direction, check the receiving address, reserve ETH for Ethereum gas and MNT for Mantle gas, then save each transaction hash. For a withdrawal, return to claim it on Ethereum.

To fund a Lightning channel with XMR, swap enough Monero for on-chain bitcoin, then use that BTC to open or add to a channel. The key is to size the swap for the channel balance you need after the swap and mining costs, while allowing for the channel’s reserve and confirmation time.

1. Decide which side needs liquidity

   Opening a channel with your BTC gives you outbound liquidity: the amount you can send through Lightning. Inbound liquidity is the amount others can send to you, and it sits on the peer’s side of the channel. Pick the result you need before choosing the channel size; adding more BTC to your side will not, by itself, give you more inbound capacity.

   For example, if you make frequent Lightning payments, you may want most of a new channel’s balance on your side. If you mainly receive, look for a channel arrangement that puts funds on the peer’s side, or use a separate liquidity method. A roughly balanced channel can handle both directions, but offers less capacity in either one than a channel weighted toward that use.

2. Calculate the BTC amount to acquire

   Set the channel funding amount first, then add the on-chain fee and a margin for the swap’s exchange rate and network costs. If you want a 1,000,000-sat channel output, for instance, the swap must deliver more than 1,000,000 sats so your wallet can also pay the Bitcoin transaction fee. Treat that as an example, not a fee quote: the required margin changes with the BTC fee rate and the conversion quote.

   Keep the channel reserve in mind when estimating usable balance. BOLT #2 says 1% of the channel’s total capacity is a suggested reserve, but the reserve is negotiated with the peer and is not a universal fixed charge. Funds constrained by the reserve cannot be spent freely, so a channel’s advertised capacity is not always its immediately usable payment balance.

3. Swap XMR for BTC before opening the channel

   Use a Monero-to-Bitcoin swap service to convert the amount you calculated, then have the resulting BTC arrive at a wallet you control. An XMR bridge is useful here because the channel funding transaction needs Bitcoin on-chain; XMR itself cannot fund a Bitcoin channel. For this cross-chain conversion, the XMR bridge service is one way to move value from Monero into BTC before you create the channel.

   Compare the final BTC you expect to receive with the amount required for the channel and its miner fee. The swap rate, spread, and transaction costs affect how much arrives, while Monero and Bitcoin confirmation times affect when you can proceed. For repeated funding, calculate the same total each time and avoid swapping so close to your target that a small quote change leaves the wallet short.

4. Open the channel with the right balance

   Once the BTC has arrived and is spendable, open a channel with your chosen Lightning peer and set the funding amount to match the liquidity plan. The funding transaction is an on-chain Bitcoin transaction: its fee depends on its size in virtual bytes and the selected rate in satoshis per vbyte. Your node or wallet may also require extra BTC for that fee, separate from the channel output.

   Where supported, a splice-in can add on-chain BTC to an existing channel instead of opening another one. It still needs a Bitcoin transaction and enough wallet funds for its fee. Check whether the operation changes the balance in the direction you need; adding funds to your side increases outbound capacity, while receiving capacity depends on funds on the peer’s side.

5. Wait for confirmation and check usable capacity

   Do not count the channel as ready just because the funding transaction was broadcast. Wait until your Lightning implementation marks it active; peers and implementations can require multiple Bitcoin confirmations. Lightning Labs’ documentation describes three confirmations as typical for channel activation, but the actual requirement can vary.

   Then check local and remote balances, the reserve, and any pending payments before routing traffic. Keep enough BTC for future on-chain fees if you plan to open or adjust channels regularly. The decision rule is simple: swap only the amount that covers your target channel balance plus the current transaction costs, and choose a channel balance that puts spendable liquidity on the side you need.