How to Finish a Manta Bridge Withdrawal

As of September 11, 2026, finishing a Manta Pacific-to-Ethereum withdrawal means returning after the Manta-side transaction and signing every Ethereum-side action the bridge marks ready. A successful initiation does not place the asset in the Ethereum wallet. Keep the transaction hash, reconnect the address that started the transfer, and use the withdrawal history in Manta Bridge to determine whether the next action is prove, wait or finalize.

Why is a confirmed withdrawal not finished?

The first confirmation only records an L2-to-L1 withdrawal message on Manta Pacific. In the canonical OP Stack-style path, that message must be included in a state commitment that Ethereum can verify. A proof transaction then identifies the withdrawal and demonstrates its inclusion; after the applicable finality or challenge conditions are satisfied, a final Ethereum transaction relays the message and releases ETH or the represented ERC-20.

That is materially different from a deposit, where Ethereum escrows the asset and the L2 credits its counterpart without the user returning for an exit claim. Manta announced a fast-finality system in January 2025 to shorten the older multi-day wait. The announcement, public code and audit work show the intended mechanism, but they do not make every withdrawal instantly claimable. The live status attached to the specific transaction is the deployed result that matters.

Finish it from transaction history

Open the history view with the initiating address connected, select the withdrawal and read its current state before signing anything. Then work through the stages in order:

• Initiated or waiting to prove: do nothing yet. Save the L2 transaction hash and let the relevant output or finality data reach Ethereum.
• Ready to prove: switch the wallet to Ethereum mainnet, inspect the destination and transaction, then submit the proof and retain its hash.
• Challenge or finality period: wait. Repeating the withdrawal will create another exit, not accelerate the existing one.
• Ready to finalize: stay on Ethereum, submit the completion transaction and verify that it succeeds before treating the balance as recovered.

Budget ETH on both networks. Manta Pacific gas pays for initiation; Ethereum gas pays for proof and finalization when those are separate transactions. The bridge amount is not a gas reserve, so withdrawing an entire native balance can leave the wallet unable to start the exit.

What if the action button is missing?

A missing button usually means the connected account, selected network or withdrawal state does not match the required step. Confirm that the wallet address matches the history entry, Manta Pacific uses chain ID 169, and the Ethereum action is being attempted on mainnet. Also distinguish a rejected wallet request from a mined failure: the former changes nothing, while the latter consumes gas and leaves an on-chain receipt worth checking.

Do not hand a seed phrase or private key to anyone offering to “release” the transfer. The recipient and amount were encoded when the withdrawal began; support cannot safely rewrite them. If the history view fails, preserve the initiation hash and retry from a clean browser session or another compatible wallet interface before attempting a duplicate withdrawal.

The custody trade-off remains

The canonical route avoids a liquidity provider: contracts and cross-chain messages determine release, and the receiving address remains fixed by the signed request. Its price is delay, multiple signatures and exposure to Manta’s sequencer, state-publication and upgrade assumptions. A liquidity bridge can deliver faster by advancing inventory, but adds provider liquidity, contract and pricing risk, plus a fee or spread.

The practical verdict is simple: an unfinished canonical withdrawal is usually a pending claim, not lost funds. Completion depends on reading the on-chain stage and funding the Ethereum transaction that stage requires—not on surrendering custody or starting over.