A Layer 1 (L1) is a base blockchain — the foundational network that settles transactions, enforces the rules, and maintains the canonical record of truth. A Layer 2 (L2) is a separate system built on top of an L1 that handles transactions off the main chain, then reports the results back. The distinction matters because it sits at the heart of one of the hardest engineering problems in crypto: how do you make a blockchain fast enough for the world without sacrificing the properties that make it trustworthy?
The scalability problem
Blockchains deliberately trade speed for security. Every full node on the network must verify every transaction, which means the network can only process as many transactions as the slowest reasonable participant can handle. For a global, censorship-resistant network, that is a considered choice — not an oversight.
The result is a real constraint. Ethereum, for example, processes roughly 15 to 30 transactions per second on its base layer. Visa processes thousands per second. During periods of high demand, users compete for limited block space by bidding up gas fees. At peak congestion, a simple token transfer can cost more than most people would ever want to spend on it.
This is not a bug that a software patch can simply fix. It stems from what researchers call the blockchain trilemma: the observation that a decentralized network seems unable to simultaneously maximize security, decentralization, and scalability. Improving one tends to come at the expense of another.
The trilemma in plain terms: Make blocks bigger and you process more transactions — but only powerful machines can run full nodes, so the network becomes more centralized. Speed up block times and throughput rises — but shorter windows for propagation can compromise security. Layer 2 systems are an attempt to escape this tradeoff rather than simply slide along it.
What Layer 1 actually does
The L1 is the source of truth. It defines:
- The consensus rules — which transactions are valid, who can add new blocks, how disputes are resolved (see proof of work and proof of stake).
- The canonical ledger — the agreed-upon record of every balance and smart contract state.
- Settlement finality — once a transaction is deep enough in the chain, it is essentially irreversible.
Well-known L1s include Bitcoin, Ethereum, Solana, and Avalanche. Each makes different tradeoffs. Solana, for instance, achieves much higher throughput on its base layer by requiring validators to run high-end hardware — a choice that improves speed but raises questions about how decentralized the validator set can realistically become.
What Layer 2 actually does
An L2 moves transaction execution off the L1 while still anchoring its security there. The broad idea: users interact with the L2, which batches many transactions together and periodically posts a compressed summary back to the L1. The L1 does not re-execute each individual transaction — it only verifies the summary.
This lets the L2 be dramatically faster and cheaper than the L1 because it is not competing for scarce L1 block space on every single action. It inherits the L1’s security because the final record is settled there.
How L2s connect back to L1
The mechanism for connecting an L2 back to its L1 is what separates different L2 designs. The two dominant approaches for Ethereum are covered in detail in the rollups guide, but the short version is:
- Optimistic rollups assume transactions are valid by default and only run a full verification if someone raises a challenge within a dispute window (typically about a week).
- ZK rollups generate a cryptographic proof that the batch of transactions was executed correctly. The L1 verifies the proof — a much smaller and faster operation than re-running every transaction.
Both approaches post transaction data to the L1, which is what gives users the ability to exit to the L1 independently if the L2 operator ever goes offline or behaves badly.
Sidechains are not the same thing
It is worth separating L2s from sidechains, which are independent blockchains that run alongside an L1 and connect via a bridge. A sidechain has its own consensus mechanism and its own security model — it does not derive security from the L1 in the same structural way a rollup does. Polygon PoS is technically a sidechain (with a separate validator set), while Arbitrum and Optimism are rollups. The distinction is not pedantic: if a sidechain’s validators collude or are compromised, users can lose funds even if the L1 is perfectly healthy. See sidechains and bridges for more on how these connections work and where the risks lie.
Comparing the tradeoffs
| Property | Layer 1 | Layer 2 (Rollup) |
|---|---|---|
| Security model | Self-contained consensus | Inherits L1 security |
| Transaction throughput | Lower (constrained by consensus) | Much higher |
| Cost per transaction | Higher at peak demand | Significantly lower |
| Finality | On-chain, relatively slow | Fast on L2, final on L1 |
| Trust assumptions | Minimal (verify yourself) | L1 + rollup contract code |
| Complexity for users | Simpler mental model | Bridging and withdrawals add steps |
The user experience gap
Using an L2 introduces friction that the base layer does not have. You need to bridge assets from the L1 to the L2, which involves sending tokens to a smart contract and waiting for them to appear on the other side. Withdrawing back to L1 from an optimistic rollup involves a waiting period. If you use multiple L2s, you end up with fragmented balances across different networks.
The crypto industry treats this as a solvable engineering problem, and progress is real — wallets are getting better at abstracting away which chain you are on, and standards for moving assets between L2s are improving. But as of now, the multi-layer world is still genuinely more complicated to navigate than staying on a single chain.
Why this architecture matters
The L1/L2 split reflects a deliberate philosophy: keep the base layer simple, secure, and maximally decentralized, then let a competitive ecosystem of L2s handle throughput. Ethereum’s long-term roadmap is explicitly “rollup-centric” — the base layer is not trying to become a high-speed transaction processor. Its job is to be the settlement and data availability layer that L2s rely on.
This is different from blockchains that try to solve scalability at L1 — through larger blocks, faster consensus, or specialized hardware requirements. Neither approach is obviously wrong. One trades some decentralization at the base layer for simplicity; the other keeps the base layer lean and accepts the complexity of a layered ecosystem.
Understanding this architectural split is essential context for evaluating any L2 project or any claim that a particular blockchain has “solved” scalability. The question is always: solved it how, and what did you give up?
Key takeaways
- Layer 1 is the base blockchain — it settles transactions, enforces consensus rules, and holds the canonical ledger.
- The scalability trilemma means L1s face hard tradeoffs between security, decentralization, and throughput.
- Layer 2 systems execute transactions off-chain and post compressed summaries back to the L1, inheriting its security while achieving much higher throughput and lower costs.
- Rollups (optimistic and ZK) are the leading L2 design for Ethereum; sidechains are a related but distinct concept with a separate security model.
- Using an L2 introduces bridging complexity and withdrawal delays that do not exist on the base layer.
- Ethereum’s roadmap is explicitly rollup-centric, treating L2s as the primary scaling path rather than expanding the base layer itself.
Next up: Rollups: Optimistic vs ZK