In short: Ethereum layer 2s (L2s) are separate networks, mostly rollups such as Arbitrum, Base and OP Mainnet, that execute transactions away from Ethereum and post the data back to it for security. Ethereum provides settlement and data availability, while the L2s capture most user activity and fee revenue, which is why the relationship between them is debated.

At a glance
What L2s get from EthereumSettlement, security and data availability
What Ethereum getsData (blob) fees, and ETH used as gas on most major rollups
Who runs L2sMostly a single sequencer operated by the launching team
Main tensionActivity and fees moving to L2s while mainnet fees fall
Key upgradeDencun (March 2024) added blobs and cut L2 data costs
Free trackersL2BEAT, growthepie

Ethereum’s rollup-centric roadmap has enabled unprecedented scale, but with it comes a new question: Are users trusting Ethereum, or are they trusting a company running an L2?

This article explores the centralization risks across Ethereum’s major Layer 2 rollups: who controls upgrades, who operates sequencers, and what escape hatches users actually have. We’ll use the L2BEAT “Stages” framework to understand which L2s are maturing toward trustless operation, and which still rely heavily on centralized control.

The Framework: Stage 0 to Stage 2

L2BEAT’s Stages framework is a three-level maturity model for rollups:

  • Stage 0: Fully custodial or centralized (no fraud/ZK proofs live).
  • Stage 1: Proofs are live, but upgrade keys, sequencer control, or escape hatches remain centralized.
  • Stage 2: Fully trustless and permissionless. No training wheels.

Today, no major rollup is at Stage 2. Most leading L2s, including Arbitrum, Optimism, Base, and zkSync Era, are still at Stage 1 or below.

Sequencers: Single Points of Failure

Most L2s today are operated by single, privileged sequencers:

This architecture enables fast UX but introduces censorship and liveness risks. When sequencers go down, users can’t submit transactions until fallback mechanisms kick in.

Upgradeability & Governance: Who Holds the Keys?

Behind the scenes, most rollups are controlled by upgradeable contracts governed by multisigs or councils:

These upgrade paths are critical for security patches but raise governance centralization concerns. The keys are often held by core teams or foundations.

Escape Hatches: Can Users Exit?

Even if sequencers fail or censor, many rollups include forced transaction mechanisms:

  • Optimism allows users to force-include L2 txs after a delay (up to ~12h).
  • Arbitrum uses a Delayed Inbox, letting users submit forceInclusion calls after ~24h.

These provide some censorship resistance, but with multi-hour latency and requiring L1 interaction. If upgrade keys are also centralized, these paths can be altered or halted.

Case Studies: When Centralization Breaks Things

These events show how L2s may inherit Ethereum’s settlement security, but not its liveness or censorship resistance.

The Fix: Shared and Decentralized Sequencers

Teams are actively building more decentralized sequencing layers:

These systems are early, but promise trust-minimized sequencing and inter-rollup coordination.

Moving Forward

The hope is that more rollups will progress toward Stage 2 on L2BEAT, reducing trust assumptions.

Until then, Ethereum’s scalability comes with trade-offs. And it’s worth asking every time you transact on an L2: who are you really trusting?

Disclaimer

The information provided in this article is for informational and educational purposes only and should not be construed as financial, investment, or trading advice. Onchain News does not provide recommendations to buy, sell, or hold any asset, and nothing here should be taken as a guarantee of future performance. Always conduct your own research and consult a qualified financial professional before making any investment decisions. Cryptocurrency markets are volatile and you are responsible for your own risk.

Common questions

Do Layer 2s take revenue away from Ethereum? They move execution fees to the rollup while still paying the base layer for data. The result is lower mainnet revenue per unit of user activity, which is the substance of the argument.

Is that a problem? It depends whether you think the base layer should capture value or provide settlement. Ethereum’s roadmap chose the second deliberately, so the outcome is a design decision rather than an accident.

How would you measure who runs the show? Compare total fees paid to the base layer against fees captured by rollups, and check how much rollup activity would survive if mainnet data costs rose sharply. That is a dependency test rather than a revenue test.

Podcast also available on PocketCasts, SoundCloud, Spotify, Google Podcasts, Apple Podcasts, and RSS.

Leave a Reply

Onchain News

Onchain News is your source for the latest developments across Bitcoin, Ethereum, Solana, and the broader crypto ecosystem.