What Is Layer 2? How Blockchains Scale Without Replacing the Base Layer

A Layer 2 network can look like an independent blockchain. It has transactions, accounts, applications, blocks and its own fees. But its defining feature is not simply that it runs separately. A Layer 2 is designed to move some work away from a base blockchain while continuing to rely on that base layer for important security functions.

The basic idea is division of labor. Instead of requiring the base blockchain to execute every user action individually, a Layer 2 can process many transactions in its own environment and then use the underlying blockchain to anchor, verify or settle the result.

This is how a blockchain can gain capacity without simply replacing its base layer with a faster chain.

What is Layer 2?

Layer 2, usually shortened to L2, is a category of blockchain scaling systems built on top of a base blockchain known as Layer 1.

Ethereum is a Layer 1. Bitcoin is also a Layer 1. They maintain their own consensus systems, transaction histories and networks of nodes.

A Layer 2 moves some transaction processing away from that base layer while retaining a relationship with its security or settlement mechanism.

On Ethereum, the most important Layer 2 systems today are rollups. Rollups execute transactions separately from Ethereum Mainnet, combine information from many transactions into batches and publish information back to Ethereum.

Ethereum’s own documentation makes an important distinction: not every blockchain connected to Ethereum is an L2. A sidechain, for example, operates under its own consensus rules and does not inherit Ethereum’s security properties in the same way a rollup does.

Why does a blockchain need Layer 2?

A decentralized blockchain asks many independent computers to agree on a common state. That redundancy is useful: users do not need one company’s database to tell them which transactions are valid.

But redundancy also limits capacity.

If every transaction must compete for execution and data space on the same base layer, demand can exceed the amount of blockspace available. Users then compete for that scarce capacity through transaction fees.

One possible response would be to make the base blockchain dramatically more demanding to operate. Bigger blocks or more aggressive hardware requirements can increase capacity, but they can also make it harder for ordinary participants to run nodes and independently verify the network.

Layer 2 takes another approach: keep the base layer focused on functions where decentralization and security matter most, while moving much of the repetitive transaction workload elsewhere.

A simple way to think about Layer 1 and Layer 2

Imagine a court system and a large marketplace.

If every routine agreement in the marketplace required a judge to inspect every detail before it could happen, the court would quickly become overloaded.

Instead, most activity happens outside the court. The court provides rules, evidence standards and a final place to resolve disputes.

A rollup has a roughly similar relationship with its base layer.

Users transact in the Layer 2 environment. The L2 processes those transactions and maintains its own state. It then publishes information to Layer 1 according to rules enforced by smart contracts.

The analogy is imperfect: blockchains use protocol rules and cryptography rather than human judges. But it captures the important division of work.

How does a Layer 2 transaction actually work?

The exact process varies by system, but an Ethereum rollup generally introduces several stages between a user and final settlement on Ethereum.

1. You submit a transaction to Layer 2

When using a rollup, you normally do not send each transaction directly to Ethereum Mainnet.

Instead, you submit it to the Layer 2. An operator often called a sequencer receives transactions, orders them and produces L2 blocks.

From the user’s perspective, this can feel much like using any other blockchain: you sign a transaction with a wallet, pay a network fee and wait for confirmation.

2. Layer 2 executes the transaction

The rollup maintains its own execution environment and state.

If you transfer a token, interact with a decentralized exchange or call a smart contract, the computation occurs in the L2 environment rather than being individually executed as a normal Ethereum Mainnet transaction.

This is one of the main sources of scalability: Ethereum does not need to perform every L2 computation separately.

3. Many transactions are grouped together

The Layer 2 collects many user transactions into batches.

Instead of each user independently paying the full cost of putting an ordinary transaction onto Layer 1, the rollup can spread the cost of its Layer 1 activity across many users.

Rollups also compress transaction-related information before publishing it, further reducing the amount of expensive base-layer space required per user transaction.

4. Data is published to Layer 1

Execution alone is not enough. Other participants need enough information to check the rollup’s state and, depending on the design, reconstruct it.

Ethereum rollups therefore publish transaction-related data to Ethereum. Modern Ethereum provides specialized data space called blobs, introduced through EIP-4844, that rollups can use for this purpose.

Blob data is designed to be cheaper for rollups than storing the same information permanently as ordinary execution data. This reflects Ethereum’s rollup-centric scaling model: Layer 1 increasingly provides secure data availability for systems executing transactions above it.

5. The Layer 2 result is verified or challenged

This is where the two major rollup families differ.

Optimistic rollups and zero-knowledge rollups both move execution away from Layer 1, but they use different mechanisms for convincing Layer 1 that the resulting state is acceptable.

Optimistic rollups: valid unless challenged

An optimistic rollup operates on the assumption that submitted state transitions are valid unless someone successfully challenges them.

The operator executes transactions outside Ethereum and publishes the required information to Ethereum. The protocol then provides a period during which incorrect results can be disputed using a fault- or fraud-proof mechanism.

This is why the model is called optimistic: it does not require a cryptographic validity proof for every batch before treating the proposed result as acceptable.

If a disputed state transition is shown to be invalid, the rollup’s protocol can reject or correct the invalid result according to its rules.

The challenge mechanism also affects withdrawals. A withdrawal using the canonical path from an optimistic rollup to Layer 1 may need to wait for the protocol’s dispute process rather than becoming immediately final on Layer 1.

ZK rollups: prove the state transition

A zero-knowledge rollup, commonly called a ZK rollup, takes a different approach.

It also executes batches of transactions outside Ethereum. But instead of relying primarily on a challenge period, it generates a cryptographic validity proof demonstrating that the proposed state transition follows the rollup’s rules.

Ethereum can verify that proof without re-executing every transaction in the batch individually.

This is a powerful compression of verification: substantial computation can happen elsewhere while the base layer checks a much smaller cryptographic proof.

Both approaches are attempts to achieve the same broader goal: execute more activity without asking Layer 1 to perform every computation itself.

What does Layer 1 still do?

If transactions execute elsewhere, it is reasonable to ask what the base blockchain is actually providing.

For Ethereum rollups, three functions are particularly important.

Data availability

A rollup needs transaction-related data to be available so that participants can independently inspect and reconstruct its state.

If an operator could hide the information needed to understand the state transition, users would have to trust that operator’s private version of events.

Publishing rollup data through Ethereum makes the information available under Ethereum’s protocol rules.

Verification

The base layer hosts contracts and mechanisms used to determine whether rollup state transitions should be accepted.

For an optimistic rollup, this includes its dispute system. For a ZK rollup, Ethereum verifies validity proofs.

Settlement

Layer 1 also acts as the place where the rollup’s state ultimately becomes anchored.

This is why describing a rollup as simply a “faster blockchain” misses the key relationship. The rollup operates its own execution environment, but its security model deliberately connects back to the base layer.

Where do lower Layer 2 fees come from?

There is no rule saying an L2 transaction must always be cheap. Fees depend on the design of the rollup, demand, Layer 1 data costs and other protocol-specific factors.

But rollups have structural ways to reduce the average cost per transaction.

First, they batch many transactions together. A Layer 1 cost that supports an entire batch can therefore be distributed across many users.

Second, rollups compress information before publishing it.

Third, Ethereum provides blob space specifically suited to rollup data. Blobs have their own fee mechanism and are not stored permanently as part of Ethereum’s execution state, allowing rollups to publish the data they need without treating it like ordinary permanent contract data.

The result is not “free transactions.” It is more efficient use of scarce Layer 1 resources.

Layer 2 is not the same as a sidechain

This distinction is one of the most useful concepts for a newcomer to understand.

A sidechain can also offer faster or cheaper transactions and can be connected to another blockchain through a bridge. But it runs its own consensus mechanism and is responsible for its own security.

An Ethereum rollup is designed to derive important security properties from Ethereum itself.

So “connected to Ethereum” and “Layer 2 of Ethereum” are not synonyms.

How do assets get onto Layer 2?

Because Layer 1 and Layer 2 maintain separate state, assets usually enter a rollup through a bridge.

In a simplified deposit, an asset is placed into a bridge contract on Layer 1. A corresponding message is communicated to the Layer 2, where the user’s L2 balance is credited according to the bridge’s rules.

Withdrawals reverse that relationship.

This is also why an Ethereum address can have different balances on Ethereum Mainnet and an Ethereum-compatible L2. The address format may be the same, but the networks maintain separate state.

What are the trade-offs?

Layer 2 scaling does not remove complexity. It redistributes it.

Sequencer dependence

Many rollups use a sequencer to order transactions and produce L2 blocks. Depending on the implementation, that role may be relatively centralized.

This does not necessarily give a sequencer the ability to rewrite Ethereum, but it can create concerns around transaction ordering, censorship resistance and availability on the Layer 2.

Smart contract risk

Rollups depend on contracts deployed on the base layer. Bugs in bridge, verification or upgrade mechanisms can create risks that do not exist when holding an asset directly on Layer 1.

Upgrade controls

Some L2 systems retain mechanisms that allow contracts to be upgraded. The exact authority, delay and governance process differ between systems.

For users, this means that “inherits Layer 1 security” should not be interpreted as “has exactly the same risk profile as Layer 1.”

Bridging complexity

Moving between Layer 1 and Layer 2 introduces another transaction flow to understand. Users need to select the correct network, bridge route and token representation.

Different forms of finality

A wallet may show an L2 transaction as confirmed quickly, but several concepts can sit behind that word.

The sequencer may have included the transaction, the batch may have been published to Layer 1, and the Layer 1 state may later reach its own finality. Depending on the rollup design, these stages do not necessarily happen at the same moment.

What should you check before using a Layer 2?

• Security model: determine whether the network is actually a rollup or another type of scaling system.
• Base layer: identify which blockchain the L2 ultimately uses for settlement and security.
• Proof system: understand whether state transitions rely on challenges, validity proofs or another mechanism.
• Data availability: check where the information required to reconstruct or verify the network’s state is published.
• Sequencer: understand who currently orders transactions and what happens if that operator becomes unavailable.
• Upgrade controls: check whether contracts can be upgraded and who has authority over those changes.
• Bridge: use the network’s documented routes and understand how deposits and withdrawals work.
• Finality: distinguish a fast L2 confirmation from final settlement on the base layer.

Why Layer 2 matters beyond cheaper transactions

Lower fees are the most visible benefit, but the architectural change is more important.

A base blockchain has limited resources. If every application must compete for exactly the same execution capacity, scaling requires continuously expanding what the base layer itself can process.

Layer 2 creates another option.

The base layer can specialize in consensus, secure data availability and settlement while multiple systems above it perform much of the execution.

That makes blockchain scaling less like making one computer endlessly larger and more like separating a system into layers with different responsibilities.

It also explains why Layer 2 does not replace Layer 1. If a rollup deliberately relies on the base chain for its security model, the base layer remains part of every transaction’s broader trust structure even when the user rarely interacts with it directly.