Why a Mantle Bridge Withdrawal Can Stay Pending

A Mantle withdrawal can be confirmed on Mantle while its Ethereum release is still waiting for settlement or a claim. The L2 transaction records the exit and sends a withdrawal message; it does not, by itself, credit the receiving address on Ethereum. Mantle’s OP-Succinct upgrade changed the settlement mechanism: batches use ZK validity proofs verified on Ethereum, replacing the former optimistic challenge period. Proof production, Ethereum processing and the final withdrawal step can still take time.

That distinction matters when a bridge screen says “complete” or “pending”: those labels can refer to different stages. The L2 receipt confirms that Mantle processed the request. The Ethereum transaction is the evidence that the exit was released. For the contract path and the difference between starting and completing an exit, see the Mantle Bridge reference. Keep both transaction hashes; they identify separate steps in one transfer.

Why is a Mantle withdrawal delayed after L2 confirmation?

Because Ethereum must verify Mantle’s state and withdrawal message before releasing the asset. Mantle executes the withdrawal on L2, where the bridge records the message and burns or accounts for the corresponding bridged balance. A batch containing that state change must then be proved and accepted by the Ethereum-side contracts. Only after the exit is eligible can the Ethereum-side release occur.

This is different from the old optimistic-rollup flow. An optimistic system allows a challenge window during which a proposed state can be disputed. OP-Succinct instead uses a validity proof: a proof attests that the batch followed the execution rules, and Ethereum verifies it. Removing the old challenge wait does not make every withdrawal instant. Proof generation and submission have their own queues, and Ethereum still needs to include and process transactions.

So a delay is not, by itself, evidence that funds are lost or that the withdrawal failed. It may mean the request has been recorded on Mantle but its settlement data is not yet ready, or that settlement is complete and the Ethereum-side action remains. The relevant question is which on-chain stage the request has reached, not simply how long the bridge page has been open.

How do I find which withdrawal step is waiting?

Start with the Mantle transaction hash and check its receipt on the Mantle explorer. A pending transaction has not yet been included; a reverted transaction did not complete the withdrawal call. A successful receipt means the L2 request was processed, but it does not prove the Ethereum release has happened. Then use the bridge’s history or withdrawal status to see whether the message is awaiting settlement or is ready for the next step.

• No successful L2 receipt: Check the wallet’s transaction status and whether the transaction reverted. Do not treat a wallet prompt or submission as an on-chain withdrawal.
• Successful L2 receipt, settlement pending: The request is recorded, but the proof and Ethereum verification path has not reached the state needed for release. Keep checking that same withdrawal.
• Ready to claim or finalize: Switch to Ethereum and inspect the receiving address and token. If the bridge requires a separate transaction, submit it from the wallet that can pay Ethereum gas.
• Ethereum transaction succeeded: Check the destination address on Ethereum and confirm the token contract. The receipt on the destination chain is the confirmation that the release executed.

Explorer events and the bridge interface describe different parts of the lifecycle. A bridge can show a request as pending even though its Mantle transaction succeeded; conversely, a successful L2 transaction can remain incomplete as a cross-chain transfer until Ethereum processes the exit. Compare the sender, recipient, asset and amount across both sides. A matching token symbol alone is not enough if the destination asset has a different contract.

What should I do if the withdrawal is ready but funds have not arrived?

If the status says the exit is ready, check whether the Ethereum claim or finalization transaction has been sent. If it has not, the withdrawal may be waiting for your action. That step is a separate Ethereum transaction, so the wallet needs ETH to pay its gas, even when the asset being withdrawn is ETH. Refresh the status before signing, then verify the chain, recipient and transaction details in the wallet.

If the claim was sent, check its Ethereum receipt. A pending receipt means Ethereum has not yet included it. A reverted receipt means the release did not execute; read the revert details and refresh the bridge status before trying again. If the interface no longer shows the action clearly, reconnect the same wallet and open the original withdrawal in history. Starting a second withdrawal will not complete the first one.

On Mantle, MNT pays for the withdrawal initiation; ETH on Ethereum pays for a separate claim when one is required. Keep enough of each token for its chain’s transaction. A status that remains unchanged after the relevant settlement step, or a claim that repeatedly reverts, is a reason to compare the explorer records with the bridge’s displayed request and contact the bridge’s support channel with both hashes. Do not share a seed phrase or sign an unfamiliar transaction to “unstick” a withdrawal.

The practical rule is to follow the exit from its Mantle receipt through proof settlement to the Ethereum receipt. The OP-Succinct proof system removes the former dispute-period wait, but settlement and any required claim remain distinct steps. Mark the transfer received only after confirming the destination balance on Ethereum.