Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia Ethereum · Entry 284

Why is my rollup withdrawal still waiting?

AI-assisted research · separate automated verificationCorrections

Theme
Ethereum
Sources
3 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for Why is my rollup withdrawal still waiting?
FactDetailSource
Source stepStarting a withdrawal records an action on the source chain.[1]
L1 stepsThe OP Stack example requires separate proving and finalization transactions.[1]
Version mattersBase’s current finalization paths differ from a generic fixed waiting rule.[2]
01

Find the bridge and message you actually used

Record the source and destination networks, asset, recipient and source transaction. Then use that bridge’s message or withdrawal identifier to locate the next stage. A generic transaction hash search on the wrong chain can look empty while the source transaction succeeded.

A fast liquidity service and a protocol’s native withdrawal can follow different routes. Check which service accepted the request before applying its timing expectations.

02

Proving late can start a later waiting clock

In the documented OP Stack flow, a withdrawal first needs an eligible state proposal. Its proof then has its own maturity condition, alongside conditions on the dispute game. Proving against a game that already resolved does not automatically allow immediate finalization.

If your source transaction is old but you proved it only recently, the source age alone does not show that every waiting requirement has passed.

03

Check the final execution and recipient

When eligible, a withdrawal may still need a destination-chain transaction and its fee. Inspect the finalization result and actual asset outcome. Do not repeatedly initiate new source withdrawals to fix an unfinished later step.

Treat a failed or invalid supporting claim through the bridge’s documented recovery path; some flows require proving again. A different bridge cannot silently complete the first bridge’s message.

Direct answers

Questions people ask

Has a withdrawal failed if my L2 transaction succeeded but L1 is empty?

Not necessarily. The source transaction can be complete while publication, proof, waiting or destination execution remains unfinished. Identify the current stage.

Do all rollup withdrawals take exactly seven days?

No. Timing depends on the protocol, current version, proof path and when required transactions occur. Check the actual deployment’s withdrawal rules.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

A rollup withdrawal can be waiting for data publication, a state proposal or proof, a protocol delay, or a final transaction on the destination chain. Identify the network and bridge, then follow the withdrawal message across its stages. A successful source-chain transaction does not by itself prove that the destination account has been paid. Exact steps and waiting rules differ by protocol and version.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Source step: Starting a withdrawal records an action on the source chain.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
L1 steps: The OP Stack example requires separate proving and finalization transactions.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Version matters: Base’s current finalization paths differ from a generic fixed waiting rule.

Scope: Ethereum · data through 2026-10-02. Verification: verified · 2026-10-02T19:27:58.939Z.

Link to this claim
Revision history
  1. — First publication after primary-source research and separate automated verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. OP Stack withdrawal flowOptimism

    L2-to-L1 withdrawals require distinct onchain stages and protocol waits.

    Locator: Initiate; prove; finalize; fault proofs · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:27.608ZOpen source
  2. Base transaction finalityBase

    Distinguish Base preconfirmation, block inclusion, Ethereum data finality and withdrawal completion.

    Locator: Finality stages · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:27.802ZOpen source
  3. Inside Arbitrum NitroOffchain Labs

    Nitro rollup execution and Ethereum batch publication versus AnyTrust committee assumptions.

    Locator: Transaction journey; rollup; AnyTrust · Version / scope: Documentation snapshot retrieved 2 October 2026; response hash recorded separately · Retrieved: 2026-10-02T18:55:27.094ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “Why is my rollup withdrawal still waiting?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/rollup-withdrawal-troubleshooting/