Track Mantle Withdrawals Through the Ethereum Claim

Integrators should track each Mantle withdrawal through five states, from the Mantle transaction to the Ethereum claim receipt. An L2 transaction succeeding does not mean the funds have arrived on Ethereum.

How should an integrator model a Mantle withdrawal?

Model it as a cross-chain message with separate source and destination transactions. The user starts the withdrawal on Mantle; after the withdrawal is included in Mantle’s settlement on Ethereum, the funds can be claimed there in a separate transaction.

For route choices and their trade-offs, the fuller mantle bridge guide gives the detail this tracking view only touches. Whichever route you monitor, keep the source transaction hash as the starting point and store the message identifier that connects the Mantle event to its Ethereum settlement.

Keep a record for each withdrawal, even when one wallet submits several in a batch. Useful fields include:

• Source chain, transaction hash, block number and sender.
• Asset, amount and destination address.
• Bridge message identifier and current settlement state.
• Ethereum claim transaction hash and receipt status, once available.

Do not use the wallet address and amount alone to match transfers. A wallet can have several withdrawals for the same token, and an amount may recur.

Which withdrawal states should your status page show?

Show whether the source transaction is confirmed, the message is awaiting settlement, the withdrawal is ready to claim, or the Ethereum claim has completed. These labels tell users what happened and what action, if any, remains.

Build the status from bridge and messenger events, then correlate them with the relevant transaction receipts. A confirmed Mantle transaction means the withdrawal request was recorded; it does not prove that Ethereum has released the asset. Likewise, “ready to claim” means the user can submit the next transaction, not that the claim has already succeeded.

Keep the raw hashes and event data behind the friendly labels. If an event is missing or your indexer falls behind, you can rescan the relevant blocks and rebuild the user-facing state rather than treating an unknown status as failure.

When is a Mantle withdrawal complete?

Mark it complete only after the Ethereum claim transaction succeeds and its receipt shows the expected result. Until then, the withdrawal is pending, even if the source transaction is confirmed or the bridge interface offers a claim button.

After the claim, verify the destination address and token balance or transfer event. This catches cases where a transaction completed but your application failed to associate it with the original request. Keep the withdrawal record available so users can return to it after closing the bridge page.

For reliability, reconcile your indexer against both chains and handle reorganisations by waiting for your chosen confirmation policy before treating observed events as settled. Keep Mantle gas and Ethereum claim gas distinct in the interface: a user may need MNT for the first transaction and ETH to submit the final claim.

Watch the settlement state and the Ethereum claim receipt for every open withdrawal. The key signal is the successful claim, not elapsed time or the status of the Mantle transaction alone.