How Does Scroll Work?

L2|Risk B-|8 mechanisms|5 interactions

An Ethereum Layer 2 that uses zero-knowledge proofs to process transactions faster and cheaper while inheriting Ethereum's security. It holds $750M in locked assets and raised $80M. Its C+ grade comes from a centralized sequencer that can censor transactions, a new unproven proof system, and no refund mechanism if your withdrawal gets stuck.

TVL

$8,000

Sector

L2

Risk Grade

B-

Value Grade

D+

Core Mechanisms

Rollup/ZK Rollup/zkEVM

Bytecode-level EVM-compatible zkEVM using SNARK proofs for transaction validity

Type-2 zkEVM aiming for full EVM bytecode compatibility. Well-documented architecture but ZK circuits are complex attack surface.

Rollup/Sequencer/Centralized Sequencer

Single privileged sequencer with priority for batch submission and transaction ordering

Standard centralized sequencer model. Can extract MEV and censor transactions. Force-inclusion is available but sequencer has priority ordering.

Rollup/Proving/OpenVM Migration

Novel

Euclid upgrade migrates proving system to OpenVM RISC-V zkVM by Axiom

Novel proving architecture using general-purpose RISC-V zkVM. Simplifies auditing via standard Rust code but introduces new, less battle-tested proving pipeline.

Bridge/Canonical/L1-L2 Message Bridge

Canonical bridge with L1 message queue and ZK-verified finalization

Messages pass through L1 queue verified by ZK proofs. No refund mechanism if messages are censored before proof submission.

Governance/Multisig/Tiered Timelock

Novel

ScrollOwner contract with four distinct timelocks governed by Security Council and team multisigs

Tiered governance with different delay guarantees per action type. Security Council and team have different authority scopes.

Rollup/Data Availability/On-chain DA

Transaction data posted to Ethereum L1 as calldata for full data availability

Standard on-chain DA model inheriting Ethereum security. Higher cost than alt-DA solutions but stronger security guarantees.

Rollup/Batch/Finalization Pipeline

Three-stage pipeline: commit transaction batches, generate ZK proofs, finalize on L1

Team can revert unfinalized batches and add/remove sequencers and provers while in permissioned mode.

Token Supply/Vesting/Airdrop

SCR token with 19% circulating supply and major unlock scheduled for October 2026

Only 190M of 1B total supply circulating. Next major unlock could create significant sell pressure.

How the Pieces Interact

Centralized sequencerL1 message bridgeHigh

Sequencer can skip messages in the L1 queue and confirm specific messages directly, enabling selective censorship. Combined with no refund mechanism, user assets can become permanently stuck in gateway contracts.

OpenVM proving migrationZK finalization pipelineHigh

Migration to novel OpenVM RISC-V proving system changes the entire proof generation pipeline. Bugs in the new prover could delay finalization or, in worst case, allow invalid state transitions to be proven.

Tiered timelock governanceBatch revert capabilityHigh

Team multisig retains ability to revert unfinalized batches and modify sequencer/prover sets. Combined with tiered timelock, critical upgrades could bypass longer delay guarantees through lower-tier authorization.

SCR token unlock scheduleTVL-dependent ecosystem growthMedium

Major token unlock in October 2026 could trigger sell pressure that reduces ecosystem confidence and TVL, creating a negative feedback loop on protocol adoption.

On-chain DA costsSequencer revenue modelMedium

High L1 data availability costs squeeze sequencer margins, potentially incentivizing transaction censorship or batching delays to optimize profitability.

What Could Go Wrong

  1. Centralized sequencer can censor transactions and extract MEV with no permissionless fallback
  2. ZK proof system migration to OpenVM introduces unproven proving pipeline with limited audit history
  3. Assets can get stuck in L1 gateway if sequencer censors messages with no refund mechanism

Sequencer Censorship Asset Freeze

Moderate

Trigger: Centralized sequencer begins selectively censoring L1 message queue entries for 24+ hours, preventing withdrawal completions for specific users or contract interactions

  1. 1.Sequencer skips specific messages in L1 queue and confirms others directly Affected users' withdrawal transactions are indefinitely delayed
  2. 2.Force-inclusion mechanism proves insufficient as sequencer has priority ordering Assets in L1 gateway contracts become effectively frozen for censored users
  3. 3.No refund mechanism exists for stuck gateway assets Users face indefinite capital lockup with no recourse
  4. 4.Community discovers censorship; confidence in Scroll collapses TVL flight begins as users who can exit rush to withdraw
  5. 5.Remaining users face degraded sequencer service under load L2 ecosystem activity drops precipitously as DeFi protocols on Scroll lose liquidity

Risk Profile at a Glance

Mechanism Novelty3/15
Interaction Severity10/20
Oracle Surface0/10
Documentation Gaps3/10
Track Record3/15
Scale Exposure3/10
Regulatory Risk3/10
Vitality Risk9/10
B-

Overall: B- (34/100)

Lower score = safer

More on Scroll

Related L2 Explainers