Layer 2 Scaling and Trade-offs
A deeper look at why base blockchains hit limits, how Layer 2 networks address them, and what trade-offs they introduce.
Jump to section
What to remember
- Layer 1 blockchains have real, deliberate throughput limits that create demand for scaling solutions.
- A Layer 2 processes activity away from the base chain and settles data or proofs back to it.
- Rollups, sidechains, and state channels make different security and trust trade-offs — they are not interchangeable.
- Always check a specific Layer 2's withdrawal process, bridge design, and security assumptions before relying on it.
Why base blockchains hit limits
A base blockchain (a Layer 1) typically has every participating node process every transaction to maintain its security and decentralization guarantees. That design is deliberate, but it caps how much activity the network can process, and demand for limited block space can push gas fees higher during busy periods.
What a Layer 2 actually does
A Layer 2 processes transactions away from the base chain — often batching many of them together — and later posts data or cryptographic proofs back to the Layer 1 for settlement. The goal is to inherit as much of the base chain's security as the specific design allows, while handling far more activity than the base chain could process directly.
Common Layer 2 designs
- Optimistic rollups, which assume transactions are valid by default and allow a window for anyone to submit fraud proofs challenging incorrect ones
- Validity (zero-knowledge) rollups, which submit a cryptographic proof that a batch of transactions was processed correctly, checked by the base chain before finalizing
- Sidechains, which run their own independent consensus and periodically interact with a base chain through a bridge, rather than inheriting its security directly
- State channels, which let participants transact directly with each other off-chain and settle only the final result on-chain
Optimistic and validity rollups both derive security from the base layer, via different mechanisms -- a sidechain does not, relying on its own validator set instead.
Trade-offs to evaluate
Different designs make different trade-offs: how much security is actually inherited from the base chain, how long it takes to withdraw funds back to the base chain, how much trust is placed in a bridge or a small set of operators, and how decentralized the system that orders transactions really is. "Layer 2" is a category, not a guarantee of any specific property.
| Design | Security inheritance from the base chain | Depends on |
|---|---|---|
| Optimistic rollup | Inherited, via a fraud-proof challenge window | Someone actually submitting a fraud proof within the window |
| Validity (ZK) rollup | Inherited, via a cryptographic correctness proof | The base chain verifying the submitted proof |
| Sidechain | Not directly inherited -- its own independent consensus | That sidechain's own validator set and bridge design |
| State channel | Only the final settled result touches the base chain | Participants' own off-chain interaction being resolved correctly |
How the four Layer 2 designs above compare on security inheritance and what each one depends on.
"Cheaper and faster" doesn't mean "equally secure"
A Layer 2's fees and speed depend on its own design choices, and so does its security. Some designs inherit strong guarantees from their base chain; others depend heavily on trusting a bridge or a small operator set. Evaluate each Layer 2 on its own specific design rather than assuming all of them share the base chain's security automatically.
What to remember
- Layer 1 blockchains have real, deliberate throughput limits that create demand for scaling solutions.
- A Layer 2 processes activity away from the base chain and settles data or proofs back to it.
- Rollups, sidechains, and state channels make different security and trust trade-offs — they are not interchangeable.
- Always check a specific Layer 2's withdrawal process, bridge design, and security assumptions before relying on it.
Related research and concepts
Base and the Growth of Coinbase-Backed Layer-2 Activity
Read the research article
Arbitrum vs. Optimism
Read the comparison
Starknet vs. ZKsync
Read the comparison
Sharding
Read the Sharding glossary definition
Sidechain
Read the Sidechain glossary definition
Rollup
Read the Rollup glossary definition
Zero-Knowledge Proof
Read the Zero-Knowledge Proof glossary definition
Cross-Chain Bridge
Read the Cross-Chain Bridge glossary definition
Interoperability
Read the Interoperability glossary definition
Polkadot
Read the Polkadot research page
Polygon
Read the Polygon research page
zk-SNARK
Read the zk-SNARK glossary definition
zk-STARK
Read the zk-STARK glossary definition
Arbitrum
Read the Arbitrum research page
The Layer 2 Scaling Landscape
Read the research article
Layer 2
Read the Layer 2 glossary definition
Layer 1
Read the Layer 1 glossary definition
Gas Fee
Read the Gas Fee glossary definition
Optimistic Rollup
Read the Optimistic Rollup glossary definition
Zero-Knowledge Proofs Explained: SNARKs vs. STARKs
Read the article
Ethereum's Glamsterdam Upgrade: What ePBS and Block-Level Access Lists Actually Change
Read the article
What Happens When a Layer 2 Shuts Down: Blast and Abstract's Exit Deadlines
Read the article