A cross-chain transfer takes two network transactions and a bridge message to move your assets. The first transaction commits your funds on the source network; a bridge then arranges for the corresponding assets to reach your destination address.
- See how bridges account for assets on both networks.
- Learn why a confirmed send may still be in progress.
- Know what to check before sending and what to do if arrival is delayed.
What does a bridge do with your assets?
A bridge coordinates a transfer between networks that keep separate records of balances. Your wallet address may look the same on both networks, but a balance on Ethereum does not automatically exist on Mantle; the bridge has to arrange a matching result on the destination network.
One common design locks your tokens in a contract on the source network and releases or creates a corresponding representation on the destination. Another burns tokens on the source and mints them on the destination. A liquidity-based route can instead pay you from funds already available on the destination, while settling the source side separately.
These designs explain why the asset name alone is not enough. A token with the same ticker on two networks may be represented by different contracts, so check that the destination asset is the one accepted by the app where you plan to use it.
Why can a confirmed send take longer to arrive?
A source transaction confirmation means the source network recorded your instruction; it does not prove that the destination network has completed its part. The bridge must observe the source transaction, establish that it is valid under its security rules, and then submit or enable the corresponding destination action.
That middle step can involve waiting for network finality, which is the point at which a transaction is treated as settled enough to act on. Some routes use an intermediary, often called a relayer, to pass the message or provide destination liquidity. Network congestion, security checks, and the route design all affect the wait, so there is no single arrival time that applies to every transfer.
For example, if you send USDC from Ethereum to Mantle, your wallet may show the Ethereum transaction as confirmed while the Mantle balance is still pending. Check the transaction on both networks and look for a completed destination transfer; do not send a second transfer just because the first one has not appeared yet.
What happens if you bridge and swap in one flow?
A bridge-and-swap route combines getting value onto the destination network with exchanging it for a different asset there. The route may execute a swap before the bridge, after it, or through a liquidity provider that pays out the requested destination asset; the exact sequence depends on the service and route.
Suppose you want an asset on Mantle but hold ETH on Ethereum. A route may use your ETH to obtain an asset that can cross, deliver value on Mantle, then swap it into the asset you requested. Each conversion can affect the amount received through exchange rates, price movement, and swap fees, in addition to the network costs for the transactions involved.
If you want to compare this kind of route, a Mantle bridge service can move and swap crypto across networks in a single flow, so you can consider the destination asset as part of the transfer rather than plan a separate swap yourself. Check which asset you will receive and on which network before you approve the source transaction.
What should you check before sending, and if it is delayed?
Before sending, confirm the source network, destination network, asset, and receiving address. Make sure you can pay the source network’s gas fee, the transaction cost paid to process an action, and leave enough destination gas if you will need to move or swap the received asset afterward.
When choosing a Mantle bridge route, compare the expected destination amount and the asset you will receive, not only the quoted speed. The route may include a bridge fee, network fees, or swap costs, and the displayed estimate can change before execution if prices or liquidity move.
If the source transaction is confirmed but the destination transfer is pending, use the transaction record and route status to identify which stage has stopped. Recovery options differ: some routes complete automatically after a delay, while others may require a claim or support from that route’s operator. Never share your recovery phrase or approve an unrelated transaction to “release” funds.
Before you act, ask yourself: do I understand what asset will arrive, on which network, and what I will need to do with it next?
Top comments (0)