Where do Ethereum rollups execute and settle?

Why move some work away from Ethereum Mainnet?

Ethereum Mainnet has limited shared capacity. When demand is high, users compete for that capacity and fees rise. A Layer 2 is a separate system that extends Ethereum while using Ethereum's security guarantees; its purpose is to increase speed and throughput without casually giving up the security and decentralization of the base layer.

Rollups are one kind of Ethereum Layer 2. Their basic idea is to handle many transactions away from Mainnet, then combine the result into a smaller set of Layer 1 submissions.

Is proof of stake a Layer 2 solution?

Ethereum's move to proof of stake changed how Ethereum Mainnet reaches consensus and is secured by validators. It did not move transaction execution into a separate Layer 2, and it was not itself a rollup or a network-capacity expansion.

Rollups address a different constraint. They execute transactions separately, then submit batch data to Ethereum and settle through Layer 1 rules. That makes them an Ethereum Layer 2 scaling path—not a new consensus mechanism for Mainnet.

What happens in a rollup?

Rollups separate execution from some of the work Ethereum Mainnet performs. Users send transactions to the rollup environment, where they are processed and grouped into batches. The rollup then submits the transaction data needed for a batch to Ethereum, along with the commitments or proofs required by its design. That division lets one Layer 1 submission represent activity from many Layer 2 transactions.

Ethereum's official documentation describes two broad proof approaches. An optimistic rollup treats transactions as valid unless a fault proof challenges them; a zero-knowledge rollup submits a validity proof. The exact mechanism is important because it affects how and when the Layer 1 contract accepts a batch.

Why do data and settlement on Layer 1 still matter?

Batching does not mean Ethereum is irrelevant after a transaction is executed. For a rollup to be independently checked, the data behind a claimed state change must be available to verifiers. Ethereum can serve as the place where that data, the batch, and the settlement rules meet.

For example, Ethereum's documentation explains that rollup batches compress many offchain transactions into a Layer 1 transaction. It also explains that data availability is necessary for others to verify a proposed summary rather than simply trust an operator's claim.

How are a rollup, a sidechain, and a bridge different?

These names answer different questions. A rollup describes an Ethereum scaling design and its relationship with Layer 1. A sidechain is an independent chain with its own security model. A bridge is a connection that carries assets, messages, or data between networks; it does not by itself determine the security model of the destination.

What new trade-offs should you look for?

Rollups can lower a user's share of Layer 1 costs by batching, but they add a new system to understand. Different Layer 2s have different trade-offs and security models, so the right beginner question is not only “Is it cheap?” but also “Where is this executed, where is it settled, and what does it depend on?”

Conclusion

A rollup separates where transactions execute from where they settle. Users transact in the rollup environment, the rollup groups that activity into batches, and it submits the transaction data plus whatever commitment or proof its design requires to Ethereum, where a Layer 1 contract provides the settlement point. One Layer 1 submission can then represent activity from many Layer 2 transactions, which is where the cost saving comes from.

Two distinctions do most of the work in this topic. The first is that Ethereum's move to proof of stake changed how Mainnet reaches consensus — it did not move execution to a separate layer, and it was not a capacity expansion. The second is that rollup, sidechain, and bridge answer different questions: a rollup describes a scaling design and its relationship to Layer 1, a sidechain is an independent chain with its own security model, and a bridge is a connection between networks that does not by itself determine the security of the destination.

Data availability is why Ethereum still matters after execution has happened elsewhere. For anyone to check a claimed state change independently rather than trust an operator's assertion, the data behind it must be available, and Ethereum can be the place where the data, the batch, and the settlement rules meet. The reader's question when meeting a cheap network is therefore not whether it is inexpensive but where it executes, where it settles, and what that arrangement depends on. A low fee does not identify a network's security relationship to Ethereum.

Lightning and rollups both respond to pressure on a base layer, but they do so for different networks and workloads. Lightning focuses on Bitcoin payment channels; rollups focus on Ethereum transaction execution and settlement. The next lesson compares another response to scaling: an independent Layer 1 with its own validators, rules, and native asset.

Frequently asked questions