{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "optimistic-rollups",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/optimistic-rollups/",
  "collection": "ethereum",
  "title": "Optimistic rollups: state claims, challenges and withdrawal waits",
  "description": "Understand optimistic rollups through an incorrect-balance example, including fault proofs, data availability, challengers and withdrawal timing.",
  "aliases": [
    "fault proofs",
    "fraud proofs",
    "rollup challenge period"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T18:16:35.976Z",
    "dataAsOf": null
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "optimistic-rollups-quick-answer",
    "sourceIds": [
      "optimistic",
      "data-availability"
    ]
  },
  "keyFacts": [
    {
      "label": "Initial treatment",
      "value": "State claims are accepted provisionally under the protocol",
      "sourceIds": [
        "optimistic"
      ],
      "id": "initial-treatment",
      "claimId": "optimistic-rollups-fact-initial-treatment"
    },
    {
      "label": "Challenge",
      "value": "A dispute can expose an incorrect transition",
      "sourceIds": [
        "optimistic"
      ],
      "id": "challenge",
      "claimId": "optimistic-rollups-fact-challenge"
    },
    {
      "label": "Data",
      "value": "Challengers need access to the inputs needed to check execution",
      "sourceIds": [
        "data-availability",
        "optimistic"
      ],
      "id": "data",
      "claimId": "optimistic-rollups-fact-data"
    }
  ],
  "prerequisites": [
    "ethereum-layer-2"
  ],
  "sections": [
    {
      "id": "provisional-claim",
      "heading": "Optimistic describes how a state claim is handled",
      "sourceIds": [
        "optimistic",
        "scaling"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "dispute-example",
      "heading": "Example: challenge a balance that execution does not justify",
      "sourceIds": [
        "optimistic"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "withdrawal-timing",
      "heading": "A sequencer receipt is earlier than a completed canonical exit",
      "sourceIds": [
        "optimistic"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "implementation-limits",
      "heading": "A challenge mechanism needs data and a path that works",
      "sourceIds": [
        "optimistic",
        "data-availability"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does optimistic mean users must trust every batch?",
      "answer": "No. The design provides a way to dispute incorrect state. Its protection depends on the deployed challenge mechanism and access to the required data.",
      "sourceIds": [
        "optimistic"
      ]
    },
    {
      "question": "Is every optimistic-rollup withdrawal exactly seven days?",
      "answer": "No. Timings are protocol-specific and can include multiple stages. A quoted duration should identify the particular deployment and withdrawal route.",
      "sourceIds": [
        "optimistic"
      ]
    },
    {
      "question": "Is a fast bridge the same as a faster canonical challenge?",
      "answer": "No. A liquidity provider can pay ahead of settlement, adding its own route and assumptions while the underlying rollup process still exists.",
      "sourceIds": [
        "optimistic"
      ]
    }
  ],
  "claims": [
    {
      "id": "optimistic-rollups-quick-answer",
      "articleSlug": "optimistic-rollups",
      "statement": "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.",
      "sourceIds": [
        "source-e415b897a2b02da7",
        "source-73ba119e5fae20da"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-e415b897a2b02da7",
          "locator": "Fraud proving; censorship resistance; exiting the rollup"
        },
        {
          "sourceId": "source-73ba119e5fae20da",
          "locator": "Data availability problem; rollups; availability versus retrievability"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:16:35.976Z",
        "reviewer": "Codex independent automated reviewer /root/verify_ethereum_100",
        "notes": [
          "Freshly reopened pinned optimistic-rollups source, especially transaction aggregation, state commitments and exiting/liquidity-provider sections. Sequencer observation, publication, dispute process and withdrawal are distinct stages.",
          "The draft correctly avoids treating generic documentation’s approximate seven-day wording as a universal deployment-specific withdrawal duration. A liquidity provider pays ahead of canonical settlement without shortening its protocol rules."
        ]
      }
    },
    {
      "id": "optimistic-rollups-fact-initial-treatment",
      "articleSlug": "optimistic-rollups",
      "statement": "Initial treatment: State claims are accepted provisionally under the protocol",
      "sourceIds": [
        "source-e415b897a2b02da7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-e415b897a2b02da7",
          "locator": "Fraud proving; censorship resistance; exiting the rollup"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:16:35.976Z",
        "reviewer": "Codex independent automated reviewer /root/verify_ethereum_100",
        "notes": [
          "Freshly reopened pinned optimistic-rollups source, especially transaction aggregation, state commitments and exiting/liquidity-provider sections. Sequencer observation, publication, dispute process and withdrawal are distinct stages.",
          "The draft correctly avoids treating generic documentation’s approximate seven-day wording as a universal deployment-specific withdrawal duration. A liquidity provider pays ahead of canonical settlement without shortening its protocol rules."
        ]
      }
    },
    {
      "id": "optimistic-rollups-fact-challenge",
      "articleSlug": "optimistic-rollups",
      "statement": "Challenge: A dispute can expose an incorrect transition",
      "sourceIds": [
        "source-e415b897a2b02da7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-e415b897a2b02da7",
          "locator": "Fraud proving; censorship resistance; exiting the rollup"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:16:35.976Z",
        "reviewer": "Codex independent automated reviewer /root/verify_ethereum_100",
        "notes": [
          "Freshly reopened pinned optimistic-rollups source, especially transaction aggregation, state commitments and exiting/liquidity-provider sections. Sequencer observation, publication, dispute process and withdrawal are distinct stages.",
          "The draft correctly avoids treating generic documentation’s approximate seven-day wording as a universal deployment-specific withdrawal duration. A liquidity provider pays ahead of canonical settlement without shortening its protocol rules."
        ]
      }
    },
    {
      "id": "optimistic-rollups-fact-data",
      "articleSlug": "optimistic-rollups",
      "statement": "Data: Challengers need access to the inputs needed to check execution",
      "sourceIds": [
        "source-73ba119e5fae20da",
        "source-e415b897a2b02da7"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-73ba119e5fae20da",
          "locator": "Data availability problem; rollups; availability versus retrievability"
        },
        {
          "sourceId": "source-e415b897a2b02da7",
          "locator": "Fraud proving; censorship resistance; exiting the rollup"
        }
      ],
      "scope": {
        "collection": "ethereum",
        "dataAsOf": null,
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T18:16:35.976Z",
        "reviewer": "Codex independent automated reviewer /root/verify_ethereum_100",
        "notes": [
          "Freshly reopened pinned optimistic-rollups source, especially transaction aggregation, state commitments and exiting/liquidity-provider sections. Sequencer observation, publication, dispute process and withdrawal are distinct stages.",
          "The draft correctly avoids treating generic documentation’s approximate seven-day wording as a universal deployment-specific withdrawal duration. A liquidity provider pays ahead of canonical settlement without shortening its protocol rules."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "optimistic",
      "label": "Optimistic rollups",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/optimistic-rollups/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/scaling/optimistic-rollups/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:47.579696+00:00",
      "locator": "Fraud proving; censorship resistance; exiting the rollup",
      "sha256": "cb9e43862d4716e7fac18423a53aa8efde7597ef9ed4c19d65acb7ceca2f21cd",
      "note": "Supports challenge periods, dispute verification, sequencer ordering and withdrawal distinctions; concrete timings depend on the implementation.",
      "recordId": "source-e415b897a2b02da7",
      "contentSha256": "cb9e43862d4716e7fac18423a53aa8efde7597ef9ed4c19d65acb7ceca2f21cd"
    },
    {
      "id": "data-availability",
      "label": "Data availability",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/data-availability/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:47.112785+00:00",
      "locator": "Data availability problem; rollups; availability versus retrievability",
      "sha256": "8ef54fe5d3ff94dec32a7de22795770098bed269e308d5a2ad1dd6e542d909e9",
      "note": "Supports why a hash is not sufficient to reconstruct data and why availability differs from permanent historical storage.",
      "recordId": "source-73ba119e5fae20da",
      "contentSha256": "8ef54fe5d3ff94dec32a7de22795770098bed269e308d5a2ad1dd6e542d909e9"
    },
    {
      "id": "scaling",
      "label": "Scaling overview",
      "publisher": "ethereum.org contributors",
      "url": "https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md",
      "canonicalUrl": "https://ethereum.org/en/developers/docs/scaling/",
      "version": "dcc900ff125891da5b6c723b905a7113cf1bd864",
      "checkedAt": "2026-10-02T14:35:47.354550+00:00",
      "locator": "Layer 2 scaling; rollups; sidechains; validium",
      "sha256": "184af71e45f53390c4f782d936954caf42715feb82048072d79eb05495569a21",
      "note": "Supports rollup execution/settlement roles and distinct security assumptions of sidechains and offchain data systems.",
      "recordId": "source-27bb64638570155e",
      "contentSha256": "184af71e45f53390c4f782d936954caf42715feb82048072d79eb05495569a21"
    }
  ],
  "related": {
    "articles": [
      "validity-rollups",
      "rollup-sequencers",
      "ethereum-blobs-data-availability"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and independent automated verification."
    },
    {
      "date": "2026-10-02",
      "kind": "substantive-edit",
      "summary": "Expanded explanation: A sequencer receipt is earlier than a completed canonical exit. Worked examples are illustrative; source checks and independent verification are recorded separately."
    }
  ],
  "citation": "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/"
}