LAYER-2.WIKI

Rollups are the most deployed Layer 2 scaling solution. They work by executing transactions off-chain while periodically committing a compressed summary of state changes to Layer 1.

Optimistic Rollups

Optimistic rollups assume transactions are valid by default and only run computation if a challenger disputes the result. This fraud-proof mechanism makes them simple and general-purpose, supporting EVM-compatible execution. Sequencers aggregate transactions into batches, compute state roots, and submit commitment transactions to Layer 1.

Zero-Knowledge Rollups

Zero-knowledge rollups generate cryptographic proofs of transaction validity before committing to Layer 1. While requiring more complex cryptography, ZK rollups eliminate withdrawal delays and provide stronger security guarantees, though they currently support limited smart contract functionality.

Sidechains are independent blockchains connected to a parent chain via a bridge mechanism. They maintain their own validator set and consensus rules while periodically committing state roots to Layer 1 for cross-chain verification.

State channels enable two or more parties to conduct transactions off-chain while periodically settling final balances on-chain. Participants exchange signed state updates that reflect transaction history, and only the final state is committed to Layer 1 upon channel closure.

Plasma is a framework for creating child blockchains (plasma chains) that periodically commit to a parent chain. Operators collect transactions and generate proofs, with exit mechanisms allowing users to withdraw funds by proving their ownership history in case of operator misbehavior.

While Plasma was historically significant as an early Layer 2 proposal, most implementations have been superseded by Rollups due to superior user experience and stronger security properties. However, Plasma concepts continue to inform designs in emerging scaling paradigms.

Sequencing and Aggregation

Layer 2 systems employ sequencers or validators that collect transactions from a mempool, order them, and execute against a shared state. The results are aggregated into a commitment that references the Layer 1 state root, ensuring provable ordering and execution.

Proof Systems

The validity assurance mechanisms differ fundamentally between optimistic and zero-knowledge approaches. Optimistic systems rely on fraud proofs—challengers can dispute incorrect state transitions within a challenge window. ZK systems generate cryptographic proofs of computation validity without revealing intermediate steps.

Cross-Layer Communication

Message passing between Layer 1 and Layer 2 is mediated through light client protocols or simplified verification logic. This asymmetry (Layer 1 → Layer 2 is simpler than Layer 2 → Layer 1) drives UX patterns around withdrawal delays and finality guarantees.

Liveness and Safety

Layer 2 security depends on the availability of validator sets or centralized sequencers. For rollups, safety is ensured by Layer 1 finality and fraud-proof or validity-proof mechanisms. Sidechains inherit security from their own consensus, creating distinct risk profiles.

Validator Incentives

Sequencers and validators are incentivized to behave correctly through transaction fees and slashing mechanisms. Economic security derives from the combined stake committed to the system and penalty structures for provable misbehavior.

Hybrid Models

Recent research explores combinations of rollup mechanisms with state channels and commit chains, attempting to optimize for different use cases within unified architectures.

Proof Composition

Zero-knowledge proof technology is advancing toward compositional systems where proofs of proofs can be aggregated, potentially enabling Layer 2 → Layer 2 communication and higher-order scaling stacks.

Multiple Layer 2 platforms have reached production status, each with distinct architectural decisions and security trade-offs. The ecosystem includes optimistic rollups (Arbitrum, Optimism), ZK rollups (StarkNet, Polygon zkEVM), and hybrid approaches.

Continued development focuses on improving developer experience, expanding smart contract capabilities in ZK systems, and enhancing cross-layer composability.