Layer 2 Scaling Solutions

Layer 2 scaling solutions help blockchains like Ethereum process more activity without forcing every transaction to happen directly on the base chain.

Ethereum’s main network is secure and decentralized, but blockspace is limited. When demand rises, fees increase and users can get priced out. Layer 2s address this by moving transaction activity to scaling systems that sit around Ethereum while still using it for settlement, security, data posting, or verification.

The most important Layer 2 designs today are rollups. Rollups process transactions off-chain, bundle them together, and post data or proofs back to Ethereum. This makes transactions cheaper and faster while keeping a connection to Ethereum’s trust foundation.

This guide explains how Layer 2 systems scale Ethereum and the trade-offs created by modular blockchain design.

What you’ll learn

Scaling & Layer 2s 201 is intended for readers who already understand blockchain basics, Ethereum, smart contracts, transactions, gas fees, and the basic idea of rollups.

Ethereum is moving from a single-chain model toward a modular system. Instead of one chain doing everything, specialized layers handle different jobs:

• Execution: rollups process transactions and user activity.

• Data availability: data layers store and prove rollup data.

• Consensus and settlement: Ethereum coordinates and secures the system.

By separating these jobs, Ethereum can scale beyond the limits of a single chain without abandoning its trust foundation.

Learning outcomes

By the end, you should be able to:

• explain why Ethereum needs Layer 2 scaling solutions;

• describe how rollups help Ethereum scale;

• compare optimistic rollups, ZK rollups;

• explain why data availability matters for rollup security;

• describe how EIP-4844 and blobs changed rollup data economics;

• understand shared sequencing, cross-rollup composability, and MEV-aware ordering;

• assess the trade-offs between cost, security, decentralization, and performance.

Course lesson summaries

The lesson summaries below are a short overview of the full course content. Take the full interactive Scaling & Layer 2s 201 course to explore each lesson in more depth through guided explanations, examples, and activities.

Lesson 1 - Data Availability Layers & Sampling

Explains why rollups need verifiable public data, how sampling and erasure coding let light nodes check large datasets, and how Ethereum, Celestia, Avail, and EigenDA offer different cost and security assumptions.

Lesson 2 - Proto- / Danksharding Rollups

Covers EIP-4844 blobs and their separate fee market, how cheaper data affects optimistic and ZK rollups differently, and how proto-danksharding leads toward greater blob capacity.

Lesson 3 - Shared Sequencers & Composability

Examines centralized sequencer risks, shared ordering across rollups, closer-to-atomic cross-rollup activity, and the MEV, governance, fee-distribution, and failure-coupling trade-offs.

Lesson 4 - Restaking-Backed Security Markets

Shows how validators, operators, and restakers can extend staked ETH to additional services, creating new rewards and lower launch costs alongside slashing and systemic-risk exposure.

Lesson 5 - Decentralized Sequencing & MEV-Aware Ordering

Explains how distributed sequencing can improve resilience and censorship resistance, how auctions or randomization can manage ordering value, and why designers must balance latency with fairness.

What Is the Blockchain Scalability Problem?

Early blockchains were monolithic. They tried to do everything in one place: run transactions, store data, and agree on the rules of the network.

That design is simple, but it creates limits. Every node has to keep up with the same shared system. If a blockchain increases throughput too aggressively, it may become harder for ordinary participants to verify the chain. If fewer people can verify the chain, decentralization and resilience can suffer.

This is often described as the blockchain scalability trilemma: the tension between scalability, decentralization, and security.

Ethereum’s challenge is not only to make transactions faster. The harder challenge is to scale activity while keeping the network verifiable, open, and resistant to capture. That is why Layer 2 scaling became central to Ethereum’s roadmap.

What Are Layer 2 Scaling Solutions?

Layer 2 scaling solutions are systems built around a base blockchain, or Layer 1, to increase capacity and reduce costs.

For Ethereum, Layer 1 is the Ethereum mainnet. It provides settlement, security, and a shared source of truth. Layer 2s handle more transaction activity away from the main chain, then connect back to Ethereum through data posting, proofs, bridges, or settlement.

A simple way to think about it:

Ethereum is the trust foundation. Layer 2s are the scaling systems that help more activity happen around that foundation.

Layer 2s do not all work the same way. Some focus on lower fees. Some focus on proof systems. Some focus on application-specific performance. The important question is not only whether a Layer 2 is fast, but what assumptions it makes around data, sequencing, bridges, and security.

Types of Layer 2 Scaling Solutions

Layer 2 is a broad category. The main designs include rollups, and older approaches such as Plasma or state channels. In Ethereum today, rollups are the central model.

Optimistic rollups

Optimistic rollups assume transactions are valid unless someone challenges them.

They process transactions off-chain and post results back to Ethereum. If a transaction is wrong, a fraud-proof process can be used to challenge it. This model can lower costs and increase throughput, but it depends on a challenge window and honest participants watching the system.

ZK rollups

ZK rollups use validity proofs to prove that transactions were processed correctly.

Instead of waiting for someone to challenge a bad transaction, a ZK rollup submits cryptographic proof that the state transition is valid. This can create stronger verification properties, but it also introduces proving costs and technical complexity.

Optimistic vs ZK Rollups: Key Differences

Optimistic and ZK rollups both help Ethereum scale, but they use different verification models.

• Core idea: Optimistic rollups assume transactions are valid unless challenged. ZK rollups prove transaction validity upfront.

• Proof model: Optimistic rollups use fraud proofs. ZK rollups use validity proofs.

• Cost profile: Optimistic rollups benefit strongly from cheaper data posting. ZK rollups benefit from cheaper data, but also depend on proving costs.

• Finality model: Optimistic rollups often include a challenge period. ZK rollups can verify faster once proofs are generated.

• Complexity: Optimistic rollups are often easier to implement. ZK rollups are more cryptographically complex.

• Main trade-off: Optimistic rollups depend on challenge windows and monitoring assumptions. ZK rollups introduce proving overhead and technical complexity.

Neither model is simply better. Each makes different trade-offs. Optimistic rollups can be practical and compatible with Ethereum tooling. ZK rollups provide upfront validity guarantees, but they require advanced proving infrastructure.

Benefits of Layer 2 Solutions

Layer 2 scaling solutions exist because Ethereum blockspace is limited and demand is high.

The main benefits are lower fees, faster activity, and more room for applications to grow.

Layer 2s reduce the need for every user transaction to compete directly for Ethereum Layer 1 blockspace. By batching transactions and posting compressed data or proofs back to Ethereum, rollups spread costs across many users.

They also make new kinds of applications more practical. Games, consumer apps, social products, payments, and high-frequency DeFi all become easier to build when transaction costs are lower and throughput is higher.

Scaling is not only about making today’s transactions cheaper. It is about unlocking what can be built when the network has more capacity.

Data Availability: Why Rollups Still Need Public Data

Rollups move execution away from Ethereum’s main chain, but they still need data to be publicly available.

This is the data availability problem: how do we make sure everyone can still see the data needed to verify a rollup’s state?

If rollup data is missing, users and validators may not be able to reconstruct what happened. The rollup could claim a state is valid, but others would not have the information needed to check it.

A rollup can post data directly to Ethereum. This gives strong security, but Ethereum’s data space is limited and expensive.

A rollup can also use an external data availability layer such as Celestia or Avail. These networks specialize in storing and proving data. They can offer lower costs and higher throughput, but the rollup now depends on that DA layer staying honest, live, and available.

Ethereum-aligned systems such as EigenDA create another option by connecting data availability to Ethereum’s broader security ecosystem.

The result is a growing data availability market where rollups choose between cost, throughput, security, reliability, and trust assumptions.

How Data Availability Sampling Works

Data Availability Sampling, or DAS, helps nodes check that data is available without downloading every byte.

Instead of downloading a full dataset, nodes randomly sample small pieces. If enough independent samples are available, the network gains statistical confidence that the full dataset is available.

Erasure coding adds redundant pieces so missing data can be detected and reconstructed, while cryptographic commitments let nodes verify that sampled pieces belong to the published dataset.

The basic process is:

• Encode: the data is split and given redundancy.

• Sample: light nodes randomly fetch small pieces of the block.

• Verify: if enough samples succeed, the network assumes the data is available with high confidence.

This makes it possible for smaller devices to help check much larger datasets.

Blobs, EIP-4844, and Proto-Danksharding

EIP-4844 introduced blob transactions to Ethereum.

Before EIP-4844, rollups posted much of their data through calldata. This worked, but it was expensive because rollup data competed with other Ethereum activity.

Blobs created a separate, temporary data space for rollups. A blob is a temporary container for rollup data. It keeps data available long enough for verification, but it does not store everything permanently on Ethereum.

EIP-4844 also created a separate blob fee market. Gas fees pay for computation. Blob fees pay for rollup data space. This helps separate rollup data demand from normal Ethereum execution demand.

Proto-danksharding is the first stage of Ethereum’s longer-term data-scaling roadmap. Full danksharding is intended to expand blob capacity and distributed data verification.

Shared Sequencers and Cross-Rollup Composability

A sequencer is the actor or system that orders transactions for a rollup.

Many rollups today rely on a centralized or semi-centralized sequencer. This can provide fast confirmations and a smoother user experience, but it also concentrates ordering power.

Shared sequencers are designed to coordinate transaction ordering across multiple rollups. Instead of each rollup using a separate ordering system, several rollups can use a common sequencing layer.

This matters for cross-rollup composability. If users and applications move between rollups, the order of transactions matters. Shared sequencing can help with cross-rollup trades, liquidity movement, bundled transactions, and more reliable workflows.

But shared sequencing introduces new questions. Who governs the shared sequencer? How are fees distributed? How is MEV handled? What happens if the shared sequencing layer fails?

Restaking and Security Markets

Restaking allows staked ETH to help secure additional services beyond Ethereum itself.

In a normal staking model, validators stake ETH to help secure Ethereum. Restaking extends that idea. Validators or restakers can opt into additional services and accept extra duties in exchange for extra rewards.

These services are often described as actively validated services, or AVSs. They can use restaked security instead of bootstrapping a new validator network from scratch.

This can make it easier for new infrastructure to launch, including data availability systems, sequencing services, or other middleware.

The trade-off is risk. Restaking can create more rewards, but it can also create more slashing exposure and operational complexity. Shared security can also mean shared risk.

Risk caps, operator vetting, insurance funds, and circuit breakers can limit some of that exposure, but they cannot remove the possibility that a failure spreads across connected services.

Decentralized Sequencing and MEV-Aware Ordering

Decentralized sequencing spreads transaction-ordering power across many participants instead of relying on one sequencer.

This matters because sequencing is one of the main centralization points in many rollup systems. A single sequencer can be fast, but it can also censor transactions, delay transactions, or extract value from ordering.

MEV, or maximum extractable value, is value that can be extracted by choosing or changing transaction order. MEV does not disappear just because activity moves to Layer 2.

MEV-aware ordering uses transparent auctions, randomization, rule-based ordering, or other mechanisms to manage ordering power more openly.

Decentralization also creates a latency trade-off. One sequencer can confirm transactions quickly, while a distributed group needs time to agree. Some designs combine fast local ordering with broader consensus to balance responsiveness and credible fairness.

The goal is not to pretend MEV disappears. The goal is to design systems where ordering power is visible, constrained, and less dependent on one trusted operator.

Risks and Trade-offs of Layer 2 Scaling

Layer 2 scaling improves capacity, but it does not remove trade-offs.

Important risks include:

• Sequencer centralization: one sequencer can improve speed, but it can also create censorship and ordering risks.

• Bridge risk: users often depend on bridges to move assets between Ethereum and Layer 2 networks.

• Data availability assumptions: a rollup using Ethereum data has different assumptions from one using an external DA layer.

• MEV and ordering risk: transaction ordering can affect execution quality and fairness.

• UX fragmentation: users may need to understand networks, bridges, gas tokens, and withdrawal times.

• Shared infrastructure risk: shared sequencers, DA layers, and restaking-backed services can connect failures across many systems.

The right question is not only “which Layer 2 is cheapest?” It is also “what assumptions does this Layer 2 make?”

Popular Layer 2 Networks

Several Layer 2 networks are widely used in the Ethereum ecosystem. This is not a ranking, and the best option depends on the user, application, and security needs.

Arbitrum is a major optimistic rollup ecosystem used for DeFi and general-purpose Ethereum applications.

Optimism is another major optimistic rollup ecosystem and is known for the OP Stack, which supports a broader network of chains.

zkSync is a ZK rollup ecosystem focused on validity-proof-based scaling and Ethereum-aligned application development.

Starknet is a ZK-based scaling network that uses STARK proofs and its own developer environment.

These examples show the range of Layer 2 designs. Some emphasize Ethereum compatibility. Some emphasize proof systems. Some emphasize ecosystem coordination.

How Layer 2 Fits Into the Future of Ethereum

Ethereum’s scaling roadmap is rollup-centered and increasingly modular.

The base chain is not trying to process every user transaction directly. Instead, Ethereum acts as the trust foundation while rollups and modular systems handle more execution and application activity.

In this model, rollups process transactions, data availability layers publish and prove data, blobs reduce rollup data costs, shared sequencers coordinate activity, restaking-backed services extend security, and decentralized sequencing improves resilience.

The future of Ethereum scaling is not one chain becoming infinitely large. It is a network of specialized layers that work together.

That creates new capacity, but also new questions. How much should rollups depend on Ethereum? Which data availability assumptions are acceptable? How decentralized should sequencers be? How should MEV be managed?

Those questions define the next phase of Layer 2 scaling.

Key takeaways

• Layer 2 scaling solutions help Ethereum process more activity without putting every transaction directly on Layer 1.

• Rollups are the main Layer 2 model in Ethereum’s current roadmap.

• Data availability is essential because rollup data must remain accessible for verification.

• EIP-4844 introduced blobs, which gave rollups cheaper temporary data space.

• Optimistic rollups and ZK rollups use different proof and verification models.

• Shared sequencers can improve cross-rollup coordination, but introduce governance and failure risks.

• Restaking can extend Ethereum’s security to new services, but adds slashing and systemic risk.

• Decentralized sequencing and MEV-aware ordering aim to make transaction ordering more fair and transparent.

Why a rollup still needs Ethereum

Imagine a busy application that wants to serve thousands of users without making each user pay Ethereum Layer 1 fees.

The application runs on a rollup. Users submit transactions to the rollup, and the rollup processes them quickly and cheaply. Instead of putting every transaction directly on Ethereum, the rollup bundles activity together.

But the rollup still needs Ethereum.

It needs a way to publish data, submit proofs, and settle results so users can verify what happened. If the rollup’s data disappears, users may not be able to reconstruct the state. If the sequencer controls ordering unfairly, users may face censorship or MEV extraction. If the bridge has weak assumptions, assets may be exposed to risk.

A good Layer 2 design balances cost, speed, security, data availability, sequencing, and user experience.

Before you start

This topic is intended for readers with intermediate knowledge.

Helpful background knowledge includes:

• blockchain basics;

• Ethereum and smart contracts;

• transactions and gas fees;

• Layer 1 vs Layer 2;

• the basic idea of rollups;

• why decentralization and verification matter.

Continue learning

Related topics include:

• Ethereum & Layer 1s 201;

• DeFi 201;

• Market Structure 201;

• Bitcoin 201;

• advanced modules on infrastructure, security, and application design.

Layer 2 scaling connects many parts of the digital asset ecosystem, including DeFi, wallets, exchanges, bridges, MEV, data availability, and Ethereum’s long-term roadmap.

Glossary

Actively validated service (AVS): A service that can draw on restaked security instead of building its own validator network.

Blob: A temporary data container introduced for rollups to publish data more cheaply on Ethereum.

Blob fee market: A separate market for rollup data space, distinct from normal Ethereum computation gas.

Cross-rollup composability: The ability for applications and assets on different rollups to interact reliably.

Data availability: The guarantee that transaction data is accessible so others can verify a rollup’s state.

Data Availability Sampling (DAS): A method where nodes sample small pieces of data to gain confidence that the full dataset is available.

Decentralized sequencing: A model where transaction ordering is distributed across many participants instead of controlled by one sequencer.

EIP-4844: The Ethereum upgrade that introduced blob transactions.

Layer 1: The base blockchain network, such as Ethereum mainnet.

Layer 2: A scaling system built around a Layer 1 blockchain.

MEV: Value that can be extracted by choosing or changing transaction order.

Optimistic rollup: A rollup that assumes transactions are valid unless challenged through fraud proofs.

Proto-danksharding: The first stage of Ethereum’s long-term data-scaling roadmap, centered on blob transactions.

Restaking: The use of staked ETH to help secure additional protocols or services.

Rollup: A Layer 2 system that processes transactions away from Ethereum Layer 1 and posts data or proofs back to Ethereum.

Sequencer: The actor or system that orders transactions for a rollup.

Shared sequencer: A common ordering network used by multiple rollups.

Slashing: A penalty that removes some validator stake when an operator misbehaves or fails duties.

ZK rollup: A rollup that proves transaction validity upfront using cryptographic proofs.

Start the full interactive course

This guide covers Layer 2 scaling solutions beyond the basics. The full Scaling & Layer 2s 201 course goes deeper with guided explanations, visual walkthroughs, interactive diagrams, knowledge checks, feedback, progress tracking, and completion.

Start the full interactive course to move beyond the overview and understand how Ethereum scales through rollups, data availability, blobs, shared sequencing, restaking-backed security markets, and MEV-aware ordering.