A Manta Pacific withdrawal marked “Waiting for state root” is usually waiting for its L2 transaction to be included in a state commitment published to Ethereum; if that withdrawal transaction is confirmed, submitting it again will not advance it. A reader who has already waited longer than the expected proving interval needs to identify the stalled stage before deciding whether to wait or act.
- A confirmed L2 withdrawal can remain unprovable until its state root is available on Ethereum.
- The challenge period starts after proving, not when the withdrawal is first submitted.
- Use the transaction hash and onchain records to distinguish a protocol delay from a wallet or display issue.
What does “waiting for state root” mean?
It means the withdrawal has been executed on Manta Pacific, but the commitment needed to prove that execution on Ethereum is not yet available to the bridge flow. The L2 transaction and the L1 state commitment are separate events: a successful receipt on Manta Pacific confirms the first, not the second.
In the rollup sequence, the withdrawal is included in L2 state, its batch data is made available, and a state root is submitted to Ethereum. The proof then ties the withdrawal message to that committed state. Until the relevant root is posted and accepted, there is nothing valid to prove, so reconnecting a wallet or changing browsers cannot remove this dependency.
How can you locate the stalled stage?
Start with the withdrawal transaction hash on the Manta Pacific explorer. Check that the transaction is successful, and record its block number, timestamp, asset, amount, and destination address; a pending or reverted receipt means the withdrawal did not reach the state-root stage.
If the L2 receipt succeeded, check whether the corresponding output or state commitment has been posted to Ethereum and whether the withdrawal has become eligible for proving. A missing commitment points to the output-publication stage. A published commitment with no proof points to proving eligibility or the bridge’s status indexer; a submitted proof moves the transaction into the challenge and finalization stages.
For the separate funding question, read what gas a Manta bridge withdrawal needs; this article focuses on diagnosing the pending state. Keep the L2 withdrawal hash as the reference throughout, since a separate transaction hash appears when you prove or finalize on Ethereum.
What should you do while the root is missing?
Do not repeat the withdrawal just because its status has not changed. If the original L2 transaction succeeded, a second withdrawal creates a second message and may lock another amount; it does not repair or replace the first one. The common mistake is treating “not yet provable” as “not submitted.”
Compare the L2 block time with the latest state commitments visible on Ethereum. If newer commitments are appearing but yours is not yet covered, the issue may be ordinary sequencing or indexing delay. If commitments stop advancing, or the same withdrawal remains outside a posted commitment well beyond the route’s stated estimate, preserve the transaction evidence and wait for the relevant publication mechanism to resume rather than sending a duplicate.
If the L2 transaction reverted, inspect the receipt and event logs for the failure reason before trying again. A retry is appropriate only after confirming that no successful withdrawal message was created; first check whether the token balance returned to the sender on Manta Pacific.
What changes after the root is available?
Once the withdrawal is provable, the next action is an Ethereum transaction that submits the withdrawal proof. This transaction consumes Ethereum gas, and its receipt should be checked independently from the original Manta Pacific transaction. A proof can fail if it uses the wrong output, the wrong withdrawal data, or a stale commitment; in that case, use the current eligible commitment and the original withdrawal message.
After a valid proof, the withdrawal enters the challenge period before it can be finalized and released on Ethereum. Manta has described a three-day period for the standard optimistic withdrawal path, while fast-finality mechanisms may shorten confirmation when they apply. These are distinct states: a long “Waiting for state root” delay happens before proving, so neither the challenge clock nor an advertised faster finality window fixes a root that has not appeared.
When the challenge period has elapsed, submit or complete the finalization transaction if required by the route, then verify the resulting Ethereum receipt and destination balance. The asset is not available on Ethereum merely because the L2 withdrawal succeeded or the proof transaction was accepted.
Practical tip: keep a small record of each hash, chain, and receipt status; it turns a vague “stuck” report into a precise answer about which stage needs to move.