A standard withdrawal from Manta Pacific to Ethereum Mainnet can take about three days after its withdrawal proof is submitted, because the rollup holds it through a challenge period before the funds can be released. That delay is part of the security process, not necessarily a sign that your transfer failed.
Why does withdrawing take longer than depositing?
Depositing and withdrawing use different checks. A deposit starts on Ethereum Mainnet, and the bridge makes the corresponding assets available on Manta Pacific after the source transaction is processed. A withdrawal starts on Manta Pacific, but Ethereum must first accept evidence that the rollup recorded it correctly.
Manta Bridge gives you a route between Ethereum Mainnet and Manta Pacific, so you can move assets to the network where you intend to use them. For a withdrawal, expect more steps than signing one transaction: you initiate it on Manta Pacific, wait for the rollup’s checks, and may need to return to finish the release on Ethereum. Manta Network’s Fast Finality announcement describes a three-day challenge period for withdrawals through its native bridge.
That challenge period gives participants time to dispute an invalid rollup record. Ethereum.org explains “finality” as the point when a block is treated as permanent; a new transaction appearing in your wallet or an explorer does not, by itself, mean the withdrawal has completed on Ethereum.
What happens during the wait?
A typical rollup withdrawal has three stages: initiation, proof, and finalization. First, your wallet submits a transaction on Manta Pacific to start the withdrawal. After the rollup posts the relevant data to Ethereum, a proof can be submitted to the Ethereum contract; the challenge period runs after that proof is accepted.
When the challenge period ends, the withdrawal may still need a finalization transaction before the assets arrive in your Ethereum wallet. This is an easy step to miss: “ready to finalize” is different from “paid.” The OP Stack specification describes this proof, challenge, and finalization sequence; exact interface labels and timing can vary by bridge implementation.
For example, if you withdraw ETH on Monday, it may show as initiated well before it is ready to claim on Ethereum. Keep the transaction record and check the bridge’s status after the stated challenge period. If the screen says the withdrawal is ready, follow its finalization prompt and review the wallet’s network and fee details before signing.
How can you check the status and finish?
Use the transaction hash—the unique ID shown after you sign—to check the withdrawal at each stage. Work through these actions in order:
- Confirm the initiation. In your wallet, open the Manta Pacific transaction and check that it succeeded. If it failed or was rejected, the withdrawal did not start; read the wallet’s error before trying again.
- Open the bridge’s withdrawal status. Look for whether the withdrawal is waiting for a proof, inside the challenge period, or ready to finalize. These are separate stages, so compare the status with the transaction hash rather than relying on a balance alone.
- Wait for the displayed challenge period. The three-day period is a useful expectation for the standard route described by Manta Network, but the interface’s current estimate should guide your transfer. A fast-finality route, if explicitly offered for your withdrawal, may have different timing and terms.
- Finalize when prompted. Connect the same wallet, switch to Ethereum Mainnet if requested, and submit the finalization transaction. Check the recipient address and fee in the wallet prompt; a withdrawal can require an Ethereum transaction fee at this stage.
- Verify the arrival on Ethereum. Check the recipient wallet on Ethereum Mainnet. The funds are available there only after the final transaction succeeds.
When is a delay a problem?
A wait within the stated challenge period is usually expected. If the status has not moved after the displayed period, first check whether the proof was submitted and whether the interface is asking you to finalize; a long-running withdrawal can be waiting for that user action.
If the source transaction failed, the status shows an error, or the bridge has no recognized record for the hash, do not submit another withdrawal blindly. Compare the transaction hash and wallet address with the bridge’s status details, then use the bridge’s support instructions if they still do not match. Never share your seed phrase or approve a wallet request that asks for it.
Plan on the standard challenge-period timeline unless the selected route clearly states a different finalization method and estimate.