Scroll’s zkEVM batch compression and proof recursion explained

The Prover Hierarchy

Scroll’s OpenVM architecture effectively lowers proving costs. This system, which arrived via the Euclid upgrade, uses a general-purpose RISC-V zkVM developed by Axiom. This architecture enables the proving of standard Rust code, which simplifies auditing and supports code reuse. The upgrade allowed Scroll to become a Stage 2 rollup. This technology replaces the early development methods used between 2021 and 2024, where custom EVM circuits proved individual opcodes. The current prover uses a hierarchical proof aggregation system. First, chunk proofs verify individual chunks of blocks. Second, batch proofs aggregate multiple chunk proofs. Finally, bundle proofs provide the aggregation layer by converting proofs into a SNARK for on-chain verification. The system also utilizes Ceno research to explore parallel proving.

wstETH and Governance

Lido’s decision does not endanger user funds. In June 2026, the Lido DAO revoked canonical recognition for wstETH bridge endpoints on Scroll. This action followed a Lido DAO Snapshot vote to focus resources on networks with high wstETH adoption. In June 2026, the Lido DAO decided to revoke canonical status for wstETH bridge endpoints on networks like Scroll to concentrate resources on chains where the asset shows more meaningful adoption. The affected networks include zkSync Era, Mode, Mantle, Swell, Zircuit, Soneium, Polygon PoS, and Lisk. This revocation constitutes a governance decision rather than a technical failure. You should know that this revocation does not disable any bridge or invalidate any tokens. Users can still hold, transfer, or bridge wstETH back to Ethereum using the same infrastructure as before. Why did the DAO decide to sunset active monitoring for these specific networks? The exchange rate for 1 WSTETH stands at 1.248889 ETH as of October 8, 2026.

zkEVM Architecture and Scaling

Scroll’s Type 2 compatibility simplifies development. The network executes transactions off-chain and then posts a compressed batch of data and a validity proof to Ethereum. The verification of a single proof for a massive batch of transactions costs much less than re-executing every transaction on the mainnet. This architecture allows developers to use existing Ethereum tools like Foundry, Hardhat, MetaMask, and Remix. The transaction life cycle follows three stages. First, the execution node processes transactions to create L2 blocks. Next, the rollup node proposes batches, and the relayer sends a commit transaction to the Rollup Contract for data availability. Finally, the coordinator receives a proof from the prover, and the relayer sends a finalize transaction to the Rollup Contract to verify the validity proof. The Execution Node contains the Sync service, the Mempool, the Executor, and the transaction queue. The Rollup Node utilizes the Relayer and the Proposer. The Rollup Node relies on a specialized workflow. The Relayer collects transaction data in each package and sends a commit transaction to the Rollup Contract to ensure data availability on Ethereum. The Chunk/Batch Proposer creates chunks or batches from transactions and sends them to the database for subsequent submission to the Prover for proof generation. The Coordinator queries the database for new chunks and sends tasks to a random Prover. This coordination ensures the Rollup Node can pass proofs to the Rollup Contract for finalizing transactions in Ethereum.