# Why is my rollup withdrawal still waiting? 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. Evidence: [OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow); [Base transaction finality](https://docs.base.org/specifications/transactions/transaction-finality); [Inside Arbitrum Nitro](https://docs.arbitrum.io/how-arbitrum-works/inside-arbitrum-nitro) Canonical: https://degreesofsatoshi.com/encyclopedia/rollup-withdrawal-troubleshooting/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:27:58.939Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Source step:** Starting a withdrawal records an action on the source chain. ([OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow)) - **L1 steps:** The OP Stack example requires separate proving and finalization transactions. ([OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow)) - **Version matters:** Base’s current finalization paths differ from a generic fixed waiting rule. ([Base transaction finality](https://docs.base.org/specifications/transactions/transaction-finality)) ## 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. Evidence: [OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow); [Inside Arbitrum Nitro](https://docs.arbitrum.io/how-arbitrum-works/inside-arbitrum-nitro) ## 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. Evidence: [OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow) ## 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. Evidence: [OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow); [Base transaction finality](https://docs.base.org/specifications/transactions/transaction-finality) ## Questions ### 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. Evidence: [OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow) ### 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. Evidence: [OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow); [Base transaction finality](https://docs.base.org/specifications/transactions/transaction-finality) ## Claims and scope ### rollup-withdrawal-troubleshooting-quick-answer 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: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### rollup-withdrawal-troubleshooting-fact-source-step Source step: Starting a withdrawal records an action on the source chain. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### rollup-withdrawal-troubleshooting-fact-l1-steps L1 steps: The OP Stack example requires separate proving and finalization transactions. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ### rollup-withdrawal-troubleshooting-fact-version-matters Version matters: Base’s current finalization paths differ from a generic fixed waiting rule. Scope: {"collection":"ethereum","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [OP Stack withdrawal flow](https://docs.optimism.io/stack/transactions/withdrawal-flow) — Optimism. L2-to-L1 withdrawals require distinct onchain stages and protocol waits. Locator: Initiate; prove; finalize; fault proofs. Retrieved: 2026-10-02T18:55:27.608Z. - [Base transaction finality](https://docs.base.org/specifications/transactions/transaction-finality) — Base. Distinguish Base preconfirmation, block inclusion, Ethereum data finality and withdrawal completion. Locator: Finality stages. Retrieved: 2026-10-02T18:55:27.802Z. - [Inside Arbitrum Nitro](https://docs.arbitrum.io/how-arbitrum-works/inside-arbitrum-nitro) — Offchain Labs. Nitro rollup execution and Ethereum batch publication versus AnyTrust committee assumptions. Locator: Transaction journey; rollup; AnyTrust. Retrieved: 2026-10-02T18:55:27.094Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry 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/