What Is Scroll? A Guide to Its Native zkEVM

Scroll is an Ethereum layer 2 network built as a zk-rollup that aims for bytecode-level EVM equivalence, meaning it tries to replicate Ethereum's execution environment as precisely as possible at the lowest technical level, rather than approximating EVM behavior at a higher level the way some other zkEVMs do.

This distinction matters because "EVM compatible" is a term used loosely across the industry, and the degree of equivalence affects how confidently developers can deploy complex, unmodified Ethereum contracts without hitting subtle behavioral differences.

What "bytecode-level equivalence" means

Ethereum smart contracts are compiled down to EVM bytecode, a low-level instruction set that the Ethereum Virtual Machine executes directly. Different zkEVM projects choose different levels of fidelity to this bytecode:

• Some zkEVMs compile higher-level Solidity code to a custom instruction set optimized for proof generation, meaning they're compatible at the language level but not identical at the bytecode level.
• Scroll's approach specifically targets matching the actual EVM bytecode execution, aiming to make its zk-circuit prove the exact same computations the real EVM would perform, opcode by opcode.

The practical benefit is that contracts, including complex ones using unusual EVM opcodes or precompiles, are less likely to behave differently on Scroll than they would on Ethereum mainnet, reducing the testing burden for teams migrating or deploying in parallel across chains.

How Scroll's rollup mechanics work

Like other zk-rollups, covered generally in our optimistic vs. ZK rollups guide, Scroll's basic flow is:

• Transactions are ordered and executed off-chain by a sequencer.
• A prover generates a zero-knowledge proof that the batch was executed correctly according to (in Scroll's case, faithfully replicated) EVM rules.
• That proof and relevant state data are posted to and verified by a smart contract on Ethereum.
• Once verified, the batch is finalized without the roughly week-long dispute window used by optimistic rollups like Arbitrum or Optimism.

Why bytecode-level equivalence is technically hard

Faithfully proving every EVM opcode, including ones rarely used or computationally awkward to represent in a zero-knowledge circuit, is significantly more difficult from an engineering standpoint than building a custom, prover-friendly virtual machine from scratch, the approach taken by chains like Starknet with Cairo. Scroll's team has generally prioritized this equivalence goal because it reduces the risk of subtle contract behavior differences, at the cost of a harder and slower engineering path to build and optimize the proving system itself.

Decentralization status

As with most zk-rollups today, Scroll's sequencer and prover infrastructure remains largely centralized in its early stages, with decentralization plans on the roadmap rather than already implemented. This is a common industry-wide pattern discussed in our sequencer decentralization guide, and it's worth treating as a live risk factor rather than an already-solved problem for any current zk-rollup, including Scroll.

Ecosystem considerations

Scroll competes with other zkEVM rollups, including zkSync Era and Linea, for developer mindshare and liquidity. Its differentiator is primarily its equivalence philosophy rather than a distinct virtual machine design. Check current adoption and TVL figures on our chains page before assuming technical differentiation alone translates into meaningful usage.

Open-source and research collaboration

Scroll's team has been notably active in publishing research and collaborating with academic and cryptography communities on the technical challenges of building a faithful zkEVM, including contributing to broader industry discussions around EVM equivalence standards and zero-knowledge proving efficiency. This research-forward posture has helped position Scroll as a reference implementation some other projects look to when discussing what "true" EVM equivalence inside a zero-knowledge circuit actually requires.

Fees and proving costs

As with other zk-rollups, Scroll's transaction costs reflect both the computational expense of proof generation and the cost of posting proof and state data to Ethereum. Achieving bytecode-level equivalence has historically added complexity to the proving system compared to more flexible, higher-level compatibility approaches, though ongoing optimization work aims to narrow any resulting cost gap between equivalence-focused zkEVMs and their less strict counterparts over time.

Scroll vs. a language-level zkEVM

Factor	Scroll (bytecode-level equivalence)	Language-level zkEVM
Compatibility target	Exact EVM bytecode/opcode behavior	Solidity/language-level compatibility
Contract migration risk	Lower, closer behavioral match	Slightly higher for edge-case opcodes
Engineering difficulty	Higher, harder proving system to build	Comparatively more flexible to build
Prover/sequencer decentralization	Still maturing	Still maturing industry-wide

Bottom line

Scroll's focus on bytecode-level EVM equivalence sets it apart technically from zkEVMs that only aim for higher-level language compatibility, reducing the risk of subtle behavior mismatches for developers porting complex Ethereum contracts. Like the rest of the current zk-rollup landscape, its sequencer and prover infrastructure are still centralized in practice, so weigh that against the technical benefits before committing significant funds. See our Linea vs Scroll comparison for a closer look at how it stacks up against a similarly positioned competitor.