Skip to main content

What Is Scroll? Native zkEVM L2 Explained

How Scroll's bytecode-level EVM equivalence works, who built it, the SCR token, and how it compares to Linea, Polygon zkEVM, and zkSync Era.

Written by Eco


Scroll is an Ethereum layer 2 that uses zero-knowledge proofs to inherit security from mainnet while running unmodified Solidity bytecode. Mainnet went live on October 17, 2023, after roughly two years of public testnets. The project's defining technical claim is bytecode-level EVM equivalence, meaning contracts compiled for Ethereum mainnet deploy and execute on Scroll without recompilation or modification.

That puts Scroll in a narrow group of zkEVMs that prioritize equivalence over throughput shortcuts. This guide walks through what Scroll actually is, who built it, how it stacks up against Linea, Polygon zkEVM, and zkSync Era, and which risks are still open as the chain enters 2026.

What Is Scroll in One Sentence?

Scroll is a zero-knowledge rollup on Ethereum that executes the full EVM at the bytecode level, generates validity proofs for each batch of transactions, and posts both the data and the proof back to mainnet for verification. The result is L2 throughput with cryptographic, rather than economic, security inheritance.

Who Built Scroll?

Scroll was co-founded in 2021 by Sandy Peng, Ye Zhang, and Haichen Shen. Ye Zhang and Haichen Shen come from a zero-knowledge research background, with prior work tied to the Ethereum Foundation's privacy and scaling explorations and academic ZK circles at institutions including Tsinghua University. Sandy Peng leads on strategy and operations.

Backers across the project's funding rounds include Polychain Capital, Sequoia China, IOSG Ventures, Bain Capital Crypto, and Variant. Scroll has also collaborated closely with Ethereum Foundation's Privacy and Scaling Explorations group, which helped open-source much of the early zkEVM circuit work that Scroll's prover builds on.

How Does Scroll Achieve EVM Equivalence?

Most zkEVMs trade off between equivalence and proving cost. zkSync Era, for example, runs a custom virtual machine (the EraVM) and recompiles Solidity into a custom bytecode, which is faster to prove but means developer tooling can diverge. Scroll takes the opposite approach. Its zkEVM proves the execution of native EVM opcodes directly, so the same bytecode that runs on Ethereum runs on Scroll.

The tradeoff is proving cost. Native EVM opcodes were not designed for ZK circuits, so proving them is expensive in both compute and time. Scroll's prover is GPU-accelerated and uses a multi-proof architecture that breaks execution into smaller chunks. According to docs.scroll.io, the system aggregates per-transaction proofs into batch proofs before posting to L1, which amortizes the verification cost on Ethereum.

Vitalik Buterin's widely cited zkEVM taxonomy places Scroll as a Type 2 zkEVM, meaning it matches Ethereum at the EVM level with only minor internal differences (state tree layout, for example) that are invisible to application developers. Type 1 would mean full consensus-level equivalence including the state tree, which no production zkEVM has hit. Type 3 and Type 4, the cheaper-to-prove categories, accept more visible divergence from mainnet behavior. Scroll's position at Type 2 is the equivalence-prioritized end of the spectrum that is actually shipping in production.

How Do Withdrawals from Scroll Work?

Because Scroll is a ZK rollup, withdrawals to Ethereum mainnet do not require the seven-day challenge window that optimistic rollups like Arbitrum and Optimism use. Once a batch is proven and the proof is verified on L1, the corresponding state root is final, and withdrawals against that root can settle. In practice, the user-perceived withdrawal time on Scroll is bounded by batch posting cadence and proof generation latency rather than by a fraud-proof window, which puts typical withdrawals on the order of hours rather than a week.

This is one of the clearer practical wins of the ZK approach. For users moving large balances back to mainnet, or for treasuries that cannot tolerate a week of locked capital, the validity-proof path materially changes the operational picture.

What Is the SCR Token?

SCR launched on October 22, 2024, alongside an airdrop to early users, testnet participants, and ecosystem contributors. Distribution included allocations for community, ecosystem development, the core team, and investors, with vesting schedules consistent with most L2 token launches.

SCR is currently used for governance over the Scroll DAO and ecosystem grants. It is not, as of early 2026, used to pay gas on Scroll, which still uses ETH. Whether SCR ever takes on a fee or staking role depends on future governance votes and progressive decentralization of the sequencer and prover.

What Is in the Scroll Ecosystem?

Scroll's ecosystem skews toward established DeFi blue chips deploying onto a new chain, rather than chain-native experiments:

  • Aave: The lending market deployed a Scroll instance, supporting ETH, USDC, and a handful of LSTs.

  • Pendle: Yield trading went live on Scroll, focused on LST and stablecoin yield markets.

  • Compound: Brought core money markets to Scroll as part of its multichain expansion.

  • Native bridge: scroll.io operates the canonical bridge for moving ETH and ERC-20 tokens between mainnet and Scroll.

  • Ambient, SyncSwap, iZUMi: DEX liquidity providers that picked up early volume.

The Scroll Sessions program ran in 2024 to bootstrap ecosystem TVL ahead of the SCR airdrop, similar in shape to incentive programs run by Arbitrum and Optimism in prior cycles.

How Big Is Scroll Today?

According to DeFiLlama's Scroll page at defillama.com/chain/Scroll, TVL has tracked the broader zkEVM cohort, with peaks tied to the Sessions program and post-airdrop normalization in late 2024. For live numbers on TVL, daily active addresses, and bridge volume, pull directly from DeFiLlama and from scroll.io's own status page rather than quoting stale figures.

Daily transaction counts and gas usage have settled into a pattern consistent with mid-tier L2s. Activity skews toward DeFi power users rather than retail or NFT-driven spikes, which reflects the ecosystem composition above.

Scroll vs Linea vs Polygon zkEVM vs zkSync Era

Four zkEVMs reach mainnet maturity, and the differences come down to equivalence level, tooling, and backer footprint:

  • Scroll: Bytecode-level EVM equivalence. Native opcodes proven directly. Independent team with deep EF-research ties.

  • Linea: Also a zkEVM with high equivalence, built and operated by ConsenSys, the company behind MetaMask and Infura. Linea's distribution advantage is tight MetaMask integration. See the Linea breakdown for details.

  • Polygon zkEVM: Type 3 zkEVM (per Vitalik's classification), high but not full equivalence. Part of the broader Polygon 2.0 stack and now positioned alongside Polygon CDK chains.

  • zkSync Era: Custom EraVM rather than native EVM. Cheaper to prove, but requires the zksolc recompiler and has had occasional tooling divergence from mainnet.

For a developer choosing among them, the practical questions are which chain has the users and liquidity for the specific use case, and whether full bytecode equivalence (Scroll, Linea) or proving efficiency (zkSync Era) matters more for the application.

Is Scroll Decentralized?

Not fully, by the team's own roadmap. As of early 2026, the sequencer that orders transactions on Scroll is operated by the Scroll team, and the prover network, while open in design, is still in the early stages of permissionless participation. The docs at docs.scroll.io publish a progressive decentralization roadmap covering sequencer rotation, prover marketplace, and governance handoff to the Scroll DAO.

This is consistent with where most zkEVMs sit. Validity proofs mean users do not need to trust the sequencer for correctness of state transitions, but a centralized sequencer can still censor or reorder transactions in the short term, and a prover outage can stall withdrawals.

What Are the Risks?

Three risk buckets worth naming:

  • Centralized sequencer. One operator can censor or delay inclusion. Validity proofs protect state correctness, not transaction-level liveness or ordering fairness.

  • Proof generation cost and latency. Native EVM proving is expensive. If proof costs rise or prover capacity is constrained, L1 finality can lag, which affects bridge withdrawal times.

  • Ecosystem concentration. Scroll's DeFi TVL is concentrated in a small number of blue-chip deployments. A pause or migration by Aave or Pendle would materially reshape the chain's footprint.

Why Does Bytecode Equivalence Matter?

For a developer, the practical answer is tooling. Hardhat, Foundry, Tenderly, Etherscan, and the long tail of Solidity libraries all assume native EVM bytecode. A chain that proves that bytecode directly inherits that tooling with no special compiler step. A chain that runs a custom VM can match developer experience eventually, but the path requires forking or wrapping each piece of tooling, which takes time.

For a user, the answer is closer to invisible. The same wallet, same RPC patterns, and same block explorer behavior carry over from mainnet, which lowers the cognitive cost of moving between L1 and L2.

Who Should Use Scroll?

Scroll makes the most sense for developers who want a zkEVM with minimal porting work and for users who prefer ZK-based security inheritance over the seven-day optimistic withdrawal window on Arbitrum or Optimism. DeFi power users with capital on Aave, Compound, or Pendle will find familiar markets on Scroll. Users prioritizing the deepest liquidity or lowest fees today should compare against Base, Arbitrum, and zkSync Era before committing.

How Does Scroll Compare to Eco's Approach?

Eco focuses on stablecoin movement across chains rather than building or operating a single chain. If your goal is moving USDC or USDT between L2s including Scroll, the relevant tools are intent-based routing systems and Circle's CCTP for native USDC transfers. Scroll sits as one supported destination among many in that model. If your goal is choosing a zkEVM to deploy a Solidity codebase onto with the least friction, Scroll's bytecode equivalence is its core argument.

Methodology and Sources

Architecture, EVM-equivalence claims, and decentralization roadmap pulled from docs.scroll.io and scroll.io as of May 2026. Founding team and backer information cross-referenced against public funding announcements and the Scroll team's own About pages. SCR token launch date and distribution confirmed against the October 2024 token announcement. TVL and ecosystem composition sourced from DeFiLlama's Scroll chain page (defillama.com/chain/Scroll). zkEVM type classification follows Vitalik Buterin's public taxonomy of zkEVM equivalence tiers.

Related Reading

Did this answer your question?