Intelligence for the Layer-2 frontier
Rollups are Layer-2 scaling solutions that execute transactions off-chain, then post compressed transaction data back to Layer 1. They inherit the security of the base chain while dramatically increasing throughput and reducing fees.
The fundamental primitive of blockchain scaling
Compression Ratio
10-100x
Two paradigms compete for dominance. Optimistic rollups assume transactions are valid and use fraud proofs for disputes. Zero-knowledge rollups generate cryptographic validity proofs, offering faster finality at the cost of computational complexity.
Different trust models, same scaling goal
Peak TPS
4,000+
Rollup economics revolve around data availability. Posting compressed calldata to Ethereum costs gas, making data compression the primary battleground. Proto-danksharding (EIP-4844) introduces blob-carrying transactions, slashing L2 costs by orders of magnitude.
Blocks Processed
1.2M+
At the heart of every rollup sits a sequencer -- the entity responsible for ordering transactions, executing them, and publishing the resulting state root along with compressed transaction data to the base layer. Sequencer design represents the most critical architectural decision in rollup engineering.
Centralized sequencers offer speed and simplicity: a single server can order thousands of transactions per second with sub-second confirmation times. But they introduce a trust assumption and a single point of failure. The next frontier is shared sequencing, where multiple rollups coordinate transaction ordering through a common protocol.
Zero-knowledge proofs transform the trust model. Instead of waiting for a challenge period (optimistic) or trusting a sequencer, ZK rollups generate succinct proofs that any state transition was computed correctly. The proof is verified on-chain in constant time, regardless of how many transactions it covers.
Modern proving systems -- PLONK, STARK, Halo2 -- trade off between proof size, generation time, and verification cost. The engineering challenge is generating proofs fast enough to keep up with real-time transaction flow, a problem that has driven remarkable advances in hardware acceleration and algorithmic optimization.
A fundamental design choice: does the rollup post full transaction data to L1 (enabling anyone to reconstruct the state) or only state diffs (smaller but requiring trust in data availability)? This choice cascades through the entire security model, affecting everything from withdrawal times to censorship resistance guarantees.
The rollup-centric roadmap envisions Ethereum as a settlement and data availability layer, with execution distributed across hundreds of specialized rollups. Interoperability protocols will bridge these execution environments, creating a unified liquidity layer. The question is no longer whether rollups will scale Ethereum, but how the rollup ecosystem itself will scale.
The future is rolled up.
rollup.report