Scroll White Paper: From Halo2 to OpenVM

Authors Scroll (the paper does not name individual authors)
Year 2024
Version 1.0, dated June 24, 2024
Project Scroll
License Not stated in the paper

Disclaimer: This page summarizes a technical paper and later protocol changes for educational purposes. It is not investment, legal, or financial advice. The linked source documents are authoritative where their scope applies; network software and governance plans can change.

Original paper Original paper
Directories Ethereum Whitepapers & Research

Scroll began as an Ethereum Layer 2 built around a zero-knowledge Ethereum Virtual Machine (zkEVM). Its June 2024 white paper describes how Scroll executed EVM transactions, batched them, published data to Ethereum, and used validity proofs to check state transitions. That document is a historical design snapshot. Scroll later replaced its original Halo2-based prover with OpenVM, and in September 2026 upgraded that prover to OpenVM v2.0 with the SWIRL proof system. The paper should therefore be read alongside current upgrade documentation rather than as a description of every component running today. [1][2][3]

What the 2024 white paper covers

The official document is Scroll White Paper, version 1.0, dated June 24, 2024. It explains the original zkEVM architecture and the transaction lifecycle that connected Scroll’s Layer 2 execution to Ethereum. The PDF does not identify individual authors or state a license, so this page does not attribute it to particular people or label it MIT. [1]

The paper’s central idea is straightforward: execute transactions outside Ethereum’s base layer, publish the information needed to reconstruct the rollup’s state, and submit a cryptographic validity proof so Ethereum can verify that the state transition followed the protocol. In the paper’s architecture, Ethereum is the settlement layer. Scroll’s sequencer orders and executes transactions, while a separate proving layer generates proofs of execution. [1]

How the original architecture worked

The 2024 paper divides the system into three cooperating layers:

  1. Settlement: Ethereum hosts Scroll’s bridge and rollup contracts. It provides the data availability and ordering used by the canonical Scroll chain, verifies validity proofs, and carries messages and assets between the two networks.
  2. Sequencing: Scroll’s execution node processes transactions and produces Layer 2 blocks. The rollup node groups those blocks, submits transaction data to Ethereum, and coordinates proof submission.
  3. Proving: A coordinator assigns proving work to a pool of provers. Their validity proofs attest that the Layer 2 execution followed the rules represented by the proof system.

This separation helps explain what a rollup does and where its responsibilities sit. Scroll executes user transactions on Layer 2, but Ethereum remains the settlement environment described by the paper. The details of the prover and state commitment have since changed, as discussed below. [1][2]

Confirmed, committed, and finalized

The paper and Scroll’s transaction documentation describe three useful transaction states:

  • Confirmed: the sequencer has executed the transaction and included it in a Layer 2 block. This is an early inclusion status.
  • Committed: the transaction’s batch data has been posted to Ethereum and the commit transaction has finalized there. The posted data allows the Layer 2 state to be reconstructed.
  • Finalized: a validity proof for the batch has been verified on Ethereum and the finalization transaction has finalized. Scroll treats the batch as part of the canonical chain.

These labels describe different stages; they should not be collapsed into a single idea of “confirmation.” The time between them depends on batching and proving. Check current transaction documentation for operational details and status definitions. [1][4]

What a validity proof does—and does not do

A zkEVM proof checks that the transaction execution and resulting state transition satisfy the system’s rules. In plain terms, the proof is evidence that the computation was performed correctly. Scroll also commits rollup data to Ethereum so independent parties can reconstruct the state. [1][4]

The “zero-knowledge” label does not mean ordinary Scroll transactions are private. Validity proofs can be used in privacy-preserving applications, but Scroll’s rollup design publishes transaction data to Ethereum for data availability. Users should not assume that sending a transaction to the public rollup hides its details.

From Halo2 to OpenVM

The 2024 paper describes Scroll’s early zkEVM work with Ethereum Privacy and Scaling Explorations (PSE) and the Halo2 proving system. That is important historical context, but it is no longer an accurate description of Scroll’s current prover. In the April 2025 Euclid upgrade, Scroll deprecated its Halo2 circuits in favor of a prover built on OpenVM. The upgrade also replaced Scroll’s zkTrie state commitment with Ethereum’s Merkle-Patricia Trie (MPT) structure. [2][3]

Scroll’s current technical overview describes a proof pipeline that aggregates chunk proofs into batch proofs and then a bundle proof for verification on Ethereum. On September 22, 2026, Scroll moved its prover stack from OpenVM 1.6 to OpenVM 2.0, which uses the SWIRL proof system and a new on-chain verifier. Scroll’s governance forum reported that the upgrade completed successfully. The announcement said the change affected the proving stack, not the external protocol, EVM, fee model, RPC, or user-facing interfaces. [2][5]

So, references to Halo2 belong to the paper’s original design period. A current explanation should distinguish that history from the OpenVM and SWIRL prover now documented by Scroll.

Scroll’s proposed direction in 2026

Scroll’s September 2026 team update says it is considering a shift from a general-purpose public network toward a private, application-specific network connected to its AI product plans. The post explicitly says the operating model and transition path still need work and that the update was not a formal proposal or vote. A September DAO update also describes the transition as under discussion and lists only tentative dates for possible token deployments, a governance vote, and a later network transition. Those plans should not be described as completed changes to Scroll’s live network. [6][7]

For users and developers, the open questions include how existing public-network applications and users would migrate, what decisions would remain with the DAO, and how the proposed network and token roles would work. These points require further governance review. Until a proposal is approved and implemented, treat them as plans under discussion rather than current protocol behavior. [6][7]

Reality check: proving, upgrades, and trust assumptions

A validity proof is only one part of rollup security. Users also rely on correct data publication, functioning sequencer and prover operations, secure contracts, and a safe upgrade process. Scroll’s Euclid documentation describes safety mechanisms such as enforced transaction inclusion through Ethereum and permissionless batch submission if the sequencer stops progressing. Those mechanisms address specific liveness and censorship risks; they do not make every operational or governance assumption disappear. [3][4]

In May 2025, Scroll’s Security Council reported an emergency verifier upgrade after a vulnerability was found in a dependency used by the OpenVM prover. The council said the issue was patched and pending blocks were re-proven. Its report also noted that, at that time, the sequencer and provers were not permissionless, which limited the vulnerability’s exploitability. This incident is a reason to understand the prover and verifier upgrade process, not evidence that the same bug remains present. [8]

Finally, technical compatibility does not make Scroll identical to Ethereum. It is a Layer 2 system with its own sequencing, batching, proof generation, contracts, and upgrade path. Evaluate those features separately from Ethereum’s base-layer guarantees.

Social Media Sentiment

A small sample of replies to Scroll’s September 2026 governance discussion is mixed: one delegate expressed support for applying Scroll’s ZK work to its new product direction while asking for a clear migration path for existing users and applications; another asked which decisions the DAO would actually control. This is a limited forum discussion, not a representative survey of Scroll users or token holders, so it should be read as evidence of active questions rather than broad consensus. [6][7]

Last updated: 2026-10

Related Terms

See Also

Sources

  1. Scroll, Scroll White Paper, v1.0, June 24, 2024 — the original paper on Scroll’s Layer 2 architecture and early zkEVM.
  2. Scroll Documentation, “Intro to zkEVM” — current overview of Scroll’s proving-system evolution and proof aggregation.
  3. Scroll Documentation, “Euclid Upgrade” — OpenVM and MPT changes, upgrade timeline, and safety features.
  4. Scroll Documentation, “Transactions” — transaction submission, lifecycle, batching, and finalization.
  5. Scroll Governance Forum, “Announcement: OpenVM v2.0.0 Upgrade on Scroll” — SWIRL migration and September 2026 execution update.
  6. Scroll Governance Forum, “What We’ve Been Working On at Scroll” — the team’s September 2026 strategic update and early community responses.
  7. Scroll Governance Forum, “Scroll DAO Monthly Update — September, 2026” — proposed transition status, tentative timeline, and governance questions.
  8. Scroll Governance Forum, “Security Council Report: Scroll Mainnet Emergency Upgrade on 2025-05-26” — the 2025 OpenVM dependency issue, remediation, and stated trust assumptions.