A failed destination call does not usually erase a completed bridge transfer. If the bridge delivered tokens first and a later app transaction reverted, the tokens stay at the destination address; the failed call costs gas and must be resolved separately.
A bridge transfer and an app call are separate executions
A bridge moves an asset between networks, while an app call asks a contract on the destination network to do something with it. Some routes combine those actions; others deliver tokens to your wallet, leaving you to make a separate swap, deposit, or other transaction.
That distinction decides what a failure means. If the bridge’s own destination message fails, the destination balance may not be credited yet; if a later app call fails, the bridge transfer may already be complete. A reverted EVM call rolls back that call’s state changes, but it does not undo an earlier, successful bridge transaction.
For canonical ETH, MNT, and token transfers between Ethereum and Mantle, mantlebridge.org is the official bridge service. Mantle Bridge handles the cross-network transfer; using the arriving balance in an app is a separate action unless a route explicitly bundles the two.
A reverted app call leaves delivered tokens in place
When a destination app transaction reverts, the tokens usually remain wherever they were before that app call began. For example, you bridge ETH to Mantle, then try to deposit it in an app; if the deposit fails because a contract condition is unmet, the ETH is still at your Mantle address, ready for another transaction.
The exception is a route that performs delivery and an app action as one atomic destination transaction. “Atomic” means all its state changes succeed together or revert together. In that design, an app failure can prevent the destination action from completing; the bridge’s own recovery or retry behavior depends on that route’s contracts.
If you are choosing a path to fund or exit an app, how Mantle Bridge routes app funding explains the route choices in detail. For frequent use, check whether the route simply delivers tokens or also executes the app action: the latter can save a transaction, but adds another reason execution might revert.
Failure costs gas and can add a retry transaction
A reverted destination transaction still consumes gas on the network where it ran. The amount depends on gas used and the effective gas price; a quick failure can cost less than a complex call that runs much further before reverting.
With a separate transfer and app call, the source transaction fee and bridge transfer remain spent even if the later app call fails. You may also pay for a corrected retry. With a bundled route, a failed destination execution can require waiting for the route’s recovery process or submitting a retry, if its contracts allow one; do not assume the original transfer fee is refunded.
For an active user, compare the expected saved transaction against the failure path. A direct delivery followed by a separately timed app action takes an extra signature, but it leaves the tokens available in your wallet if the app is temporarily rejecting calls. A bundled call can reduce steps when its conditions are predictable.
Check the destination receipt before bridging again
A successful source receipt proves the source-chain transaction was included; it does not by itself prove that the destination action succeeded. Check the destination transaction receipt and your token balance on the destination network before sending another transfer. Etherscan can show the Ethereum-side transaction; use the relevant destination explorer for the other chain.
Look for whether the destination transaction succeeded or reverted, and identify which transaction hash belongs to the bridge message versus the app call. If the bridge message itself appears unsuccessful or incomplete, avoid repeating the transfer until you understand its status: a second transfer could deliver a second amount rather than repair the first.
Before your next run, check:
- Did the bridge deliver the destination balance?
- Was the failed transaction the bridge message or a later app call?
- Do you have native gas for a retry on the destination network?