Layer 2 (L2) solutions are protocols built on top of a Layer 1 blockchain that handle transaction execution off the main chain while ultimately relying on the L1 for security and settlement. They exist because the most secure and decentralized L1 blockchains—particularly Ethereum—have inherently limited throughput, creating a bottleneck that manifests as high fees and slow confirmation times during peak demand.
Why Layer 2 Solutions Exist
The need for L2 scaling stems directly from the blockchain trilemma. Ethereum, the primary platform for decentralized applications, processes approximately 15–30 transactions per second on its base layer. During periods of high demand—NFT mints, DeFi yield farming events, market volatility—gas fees can spike to $50–$200 per transaction, pricing out most users.
Ethereum's roadmap addresses this through a rollup-centric scaling strategy: rather than increasing L1 throughput (which would require higher node hardware requirements and reduce decentralization), the approach is to move execution to L2s while keeping the L1 as a secure settlement and data availability layer.
This is not a concession. It is a deliberate architectural choice: the L1 provides the strongest possible security guarantees, and L2s leverage those guarantees to offer fast, cheap transactions without sacrificing the decentralization of the base layer.
The L1-L2 Relationship
The critical concept in L2 design is security inheritance. A true L2 derives its security from the L1—meaning that even if the L2 operators are malicious or go offline, users can recover their funds through the L1. This is what distinguishes an L2 from a sidechain, which has its own independent security model.
The relationship works as follows:
- Users deposit assets into a smart contract on the L1.
- The L2 processes transactions off-chain, maintaining its own state.
- The L2 periodically posts proofs or transaction data back to the L1.
- The L1 smart contract verifies that the L2 state transitions are valid.
- Users can withdraw from the L2 back to the L1 at any time, even if the L2 ceases to operate.
Types of Layer 2 Solutions
Rollups
Rollups are the dominant L2 scaling approach. They execute transactions off-chain, then "roll up" batches of transactions and post compressed data to the L1. This achieves significant throughput gains while maintaining L1-level security guarantees.
There are two types of rollups, distinguished by how they prove correctness to the L1:
- Optimistic Rollups: Assume transactions are valid by default. A challenge period (typically 7 days) allows anyone to submit a fraud proof if an invalid state transition is detected. Examples: Arbitrum, Optimism, Base.
- ZK-Rollups (Zero-Knowledge Rollups): Generate cryptographic validity proofs for every batch of transactions. The L1 verifies the proof mathematically, providing immediate certainty. Examples: zkSync Era, StarkNet, Polygon zkEVM, Scroll, Linea.
Both types post transaction data (or a compressed representation) to the L1, ensuring that anyone can reconstruct the L2 state from L1 data alone. This data availability guarantee is what enables users to force-exit from the L2 even if all L2 operators disappear.
State Channels
State channels allow two or more parties to conduct unlimited off-chain transactions, settling only the final state on the L1. They are ideal for scenarios involving repeated interactions between the same participants.
- Participants lock funds in a multisig contract on the L1.
- They exchange signed transactions off-chain, updating balances between themselves.
- When finished, they submit the final state to the L1 for settlement.
- Dispute resolution mechanisms handle cases where a party tries to submit an outdated state.
The Lightning Network (Bitcoin) and Raiden Network (Ethereum) are the most prominent examples. State channels offer near-instant finality and zero fees for off-chain transactions but are limited to fixed participant sets and are not suitable for general-purpose smart contract execution.
Sidechains
Sidechains are independent blockchains that run in parallel to the L1 and connect via a bridge. Unlike true L2s, sidechains have their own consensus mechanisms and validator sets. They do not inherit L1 security.
- Polygon PoS: A Proof of Stake sidechain with its own validator set. Periodically checkpoints to Ethereum but does not derive security from it.
- Ronin: An Ethereum-linked sidechain built for Axie Infinity. Uses a small validator set optimized for gaming throughput.
- Liquid Network: A Bitcoin sidechain operated by a federation of exchanges and financial institutions, designed for faster BTC transfers and asset issuance.
Sidechains offer high throughput and flexibility but introduce additional trust assumptions. The security of the sidechain is only as strong as its own validator set, not the underlying L1.
Plasma
Plasma chains are child chains that submit periodic commitments (Merkle roots) to the L1. Users can exit to the L1 using Merkle proofs. Plasma was an early scaling proposal for Ethereum but has largely been superseded by rollups due to data availability limitations.
The key problem with Plasma is that it does not post full transaction data to the L1. This means that if the Plasma operator withholds data, users may not be able to construct the proofs needed to exit. Rollups solve this by posting data (or data commitments) on-chain.
Settlement and Data Availability
Two concepts are central to understanding L2 security:
- Settlement: The L1 acts as the final arbiter of disputes. If an L2 operator submits an invalid state, the L1 smart contract can reject it (ZK-rollups) or accept a fraud proof challenge (optimistic rollups).
- Data availability: Transaction data must be accessible so that anyone can independently verify the L2 state. Rollups post this data to the L1 (either as calldata or blobs). Without data availability, users cannot prove their balances and force withdrawals.
Ethereum's EIP-4844 (Proto-Danksharding), deployed in March 2024, introduced blob transactions—a dedicated, cheaper data space on the L1 designed specifically for rollup data. This reduced rollup transaction costs by 10–100x and is a precursor to full Danksharding, which will further expand data availability capacity.
The Current L2 Landscape
As of 2026, the Ethereum L2 ecosystem has matured significantly:
| L2 Solution | Type | TVL Rank | Key Feature |
|---|---|---|---|
| Arbitrum One | Optimistic Rollup | #1 | Nitro engine, Stylus (multi-language support) |
| Base | Optimistic Rollup | #2 | Coinbase-incubated, OP Stack |
| Optimism | Optimistic Rollup | #3 | Superchain vision, OP Stack framework |
| zkSync Era | ZK-Rollup | #4 | Native account abstraction, zkEVM |
| StarkNet | ZK-Rollup (STARK) | #5 | Cairo language, STARK proofs |
| Polygon zkEVM | ZK-Rollup | #6 | EVM-equivalent ZK proofs |
Key Takeaways
- Layer 2 solutions move transaction execution off the main chain while relying on L1 for security and settlement.
- Rollups (optimistic and ZK) are the dominant L2 paradigm, posting transaction data to the L1 to ensure data availability and user fund safety.
- State channels offer instant finality for fixed participant interactions but lack general-purpose programmability.
- Sidechains provide independent scaling but do not inherit L1 security—a critical distinction from true L2s.
- Ethereum's rollup-centric roadmap, enhanced by EIP-4844 blob transactions, has made L2 transactions 10–100x cheaper.
- The primary challenge ahead is L2 interoperability and liquidity fragmentation across the growing number of rollup chains.