# Optimistic rollups: state claims, challenges and withdrawal waits Optimistic rollups execute transactions off Ethereum and allow proposed state results to be challenged. A dispute mechanism determines whether a contested transition followed the rules. Their security depends on usable data, an effective challenge path and timely participation; a fast sequencer receipt is not the end of the challenge or withdrawal process. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md) Canonical: https://degreesofsatoshi.com/encyclopedia/optimistic-rollups/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T18:16:35.976Z AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Initial treatment:** State claims are accepted provisionally under the protocol ([Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md)) - **Challenge:** A dispute can expose an incorrect transition ([Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md)) - **Data:** Challengers need access to the inputs needed to check execution ([Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md); [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md)) ## Optimistic describes how a state claim is handled The rollup operator executes transactions and proposes a resulting state. Instead of proving every batch’s computation up front, the system provides a period and procedure in which an incorrect assertion can be disputed. Optimistic does not mean no checking is possible. It means the settlement design relies on an enforceable challenge process, with the deployed rules determining who can challenge and how. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Scaling overview](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md) ## Example: challenge a balance that execution does not justify Imagine a batch whose valid transactions should leave an account with seven units, but whose proposed state assigns nine. A challenger re-executes the available inputs and identifies the disagreement. Some dispute protocols narrow the disagreement through successive steps until the settlement contract can decide a small execution claim. The exact procedure varies; this example illustrates why a reproducible state transition matters. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md) ## A sequencer receipt is earlier than a completed canonical exit Separate acceptance by a sequencer, rollup inclusion, publication or commitment to the settlement chain, the applicable dispute process and completion of a withdrawal. These establish different facts at different stages. A liquidity service can offer an earlier payout by taking additional risk or using its own inventory. That service does not erase the canonical route’s settlement rules. Quote a withdrawal period only for a named deployment and version, with its assumptions. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md) ## A challenge mechanism needs data and a path that works If transaction inputs are unavailable, an observer may be unable to reconstruct execution and challenge effectively. Data publication and access therefore belong in the security explanation alongside the proof mechanism. Permissioning, upgrade authority and outage behavior also matter. Do not assume every project has the same challenge duration, a permissionless challenger set or identical forced-inclusion and exit protections. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md); [Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md) ## Questions ### Does optimistic mean users must trust every batch? No. The design provides a way to dispute incorrect state. Its protection depends on the deployed challenge mechanism and access to the required data. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md) ### Is every optimistic-rollup withdrawal exactly seven days? No. Timings are protocol-specific and can include multiple stages. A quoted duration should identify the particular deployment and withdrawal route. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md) ### Is a fast bridge the same as a faster canonical challenge? No. A liquidity provider can pay ahead of settlement, adding its own route and assumptions while the underlying rollup process still exists. Evidence: [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md) ## Claims and scope ### optimistic-rollups-quick-answer Optimistic rollups execute transactions off Ethereum and allow proposed state results to be challenged. A dispute mechanism determines whether a contested transition followed the rules. Their security depends on usable data, an effective challenge path and timely participation; a fast sequencer receipt is not the end of the challenge or withdrawal process. Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### optimistic-rollups-fact-initial-treatment Initial treatment: State claims are accepted provisionally under the protocol Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### optimistic-rollups-fact-challenge Challenge: A dispute can expose an incorrect transition Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### optimistic-rollups-fact-data Data: Challengers need access to the inputs needed to check execution Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ## Sources - [Optimistic rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md) — ethereum.org contributors. Supports challenge periods, dispute verification, sequencer ordering and withdrawal distinctions; concrete timings depend on the implementation. Locator: Fraud proving; censorship resistance; exiting the rollup. Retrieved: 2026-10-02T14:35:47.579696+00:00. - [Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md) — ethereum.org contributors. Supports why a hash is not sufficient to reconstruct data and why availability differs from permanent historical storage. Locator: Data availability problem; rollups; availability versus retrievability. Retrieved: 2026-10-02T14:35:47.112785+00:00. - [Scaling overview](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md) — ethereum.org contributors. Supports rollup execution/settlement roles and distinct security assumptions of sidechains and offchain data systems. Locator: Layer 2 scaling; rollups; sidechains; validium. Retrieved: 2026-10-02T14:35:47.354550+00:00. ## Revision history - 2026-10-02: First publication after primary-source research and independent automated verification. - 2026-10-02: Expanded explanation: A sequencer receipt is earlier than a completed canonical exit. Worked examples are illustrative; source checks and independent verification are recorded separately. ## Cite this entry Degrees of Satoshi editorial project. “Optimistic rollups: state claims, challenges and withdrawal waits.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/optimistic-rollups/