# Validity rollups: what does the proof prove? A validity rollup executes transactions outside Ethereum and submits a cryptographic proof that a proposed state change follows its rules. Ethereum verifies the proof. The rollup also publishes reconstruction data; proof generation, settlement and withdrawals remain distinct steps. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-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/validity-rollups/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T15:10:23.134Z AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Proof scope:** Correct execution of the rules encoded by the proof system ([Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md)) - **Data requirement:** A rollup publishes data needed to reconstruct its state ([Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md); [Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md)) - **Privacy:** Validity proofs alone do not make transactions confidential ([Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md)) ## A verifier checks a statement about execution A rollup represents its accounts and other state with a compact cryptographic commitment. After executing a batch, the operator proposes a new commitment and produces a proof linking the old state, the transactions and the resulting state under the rollup’s rules. An Ethereum verifier contract checks that proof instead of repeating every underlying computation. The security claim concerns the specified computation and the implemented proof system. Bugs in either can undermine the intended result. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ## Example: proving a balance update Imagine an account with 10 tokens makes an authorized transfer of 3 tokens. Ignoring fees for this example, the new balance is 7 and the recipient gains 3. A correct proof must be consistent with authorization, sufficient funds and both balance changes under the encoded rules. It does not establish that the recipient shipped a promised product, that the token has value or that the user understood the signature. Those are different claims. A mathematical proof of execution is powerful precisely because its scope is specific. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ## A proof is not the data needed to use the chain Users and independent operators still need enough published data to reconstruct the rollup state. A tiny state commitment cannot tell a user their balance or supply every input needed to prepare an exit. Data availability remains a separate requirement. The label ZK-rollup does not promise private payments. A proof system may have a zero-knowledge property while the rollup publishes transaction information publicly. Systems that keep reconstruction data outside Ethereum introduce different availability assumptions and are commonly described as validiums rather than rollups. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md); [Data availability](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/data-availability/index.md); [Scaling overview](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/index.md) ## Proof-based settlement still has stages An operator must include the transaction, assemble a batch, generate the proof and get it accepted on Ethereum. Ethereum inclusion and finality then matter. A withdrawal can require additional bridge steps. Avoid interpreting the absence of a fraud-proof challenge interval as a guarantee of immediate payment. Assess the actual deployment: who can submit batches, what happens during an outage, how upgrades work and whether users can exit without cooperation. A sound proof system addresses invalid state changes; it does not by itself guarantee prompt service or eliminate administrative authority. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md); [Proof of stake](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/consensus-mechanisms/pos/index.md) ## Questions ### Does ZK mean my transactions are private? No. Rollups can publish transaction information publicly while using validity proofs. Privacy depends on the application and the exact information it reveals. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ### Are withdrawals always instant? No. Batching, proof production, Ethereum inclusion and the bridge workflow can all take time. A validity proof removes a particular need for fraud-proof challenges, not all waiting. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md); [Proof of stake](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/consensus-mechanisms/pos/index.md) ### Can a validity proof establish that a token is well backed? Not on its own. It establishes a statement about the encoded computation. Real-world reserve or delivery claims require evidence outside that computation. Evidence: [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) ## Claims and scope ### validity-rollups-quick-answer A validity rollup executes transactions outside Ethereum and submits a cryptographic proof that a proposed state change follows its rules. Ethereum verifies the proof. The rollup also publishes reconstruction data; proof generation, settlement and withdrawals remain distinct steps. Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### validity-rollups-fact-proof-scope Proof scope: Correct execution of the rules encoded by the proof system Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### validity-rollups-fact-data-requirement Data requirement: A rollup publishes data needed to reconstruct its state Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ### validity-rollups-fact-privacy Privacy: Validity proofs alone do not make transactions confidential Scope: {"collection":"ethereum","dataAsOf":null,"blockHeight":null} ## Sources - [Zero-knowledge rollups](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/scaling/zk-rollups/index.md) — ethereum.org contributors. Supports validity proofs and public rollup data; no claim that every withdrawal is instant or that every ZK system is private. Locator: Data availability; validity proofs; withdrawals; EVM compatibility. Retrieved: 2026-10-02T14:35:47.579728+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. - [Proof of stake](https://raw.githubusercontent.com/ethereum/ethereum-org-website/dcc900ff125891da5b6c723b905a7113cf1bd864/public/content/developers/docs/consensus-mechanisms/pos/index.md) — ethereum.org contributors. Supports 12-second slots, 32-slot epochs, stake-weighted checkpoint voting and block verification. Locator: Validators; transaction execution; finality; fork choice. Retrieved: 2026-10-02T14:35:43.818781+00:00. ## Revision history - 2026-10-02: First publication after primary-source research and independent automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Validity rollups: what does the proof prove?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/validity-rollups/