Are Layer 2 Networks Actually Decentralized?

Calling a Layer 2 (L2) “secured by Ethereum” can be accurate, but it leaves out important details. Ethereum may verify a rollup’s state updates and hold data needed to reconstruct them, while transaction ordering, emergency powers, upgrades, or data availability are still controlled elsewhere. The words “L2” and “Ethereum-secured” do not by themselves tell you how decentralized a system is.

A useful review separates four questions: what Ethereum verifies, where the data needed to recover state is stored, who orders and includes transactions, and who can change or pause the contracts. Those answers vary by project and can change over time.


Four parts of an L2’s trust model

1. State validation and settlement. An Ethereum Layer 2 rollup posts information to Ethereum and uses a proof system to support its state updates. Optimistic rollups let challengers dispute an invalid update during a challenge period; zero-knowledge rollups use validity proofs that Ethereum verifies. These systems can reduce reliance on an operator for state correctness, but they do not automatically decentralize sequencing, governance, or every contract that holds assets.

2. Data availability. A rollup needs the transaction data or state data required to verify and reconstruct its state. Rollups publish that data to Ethereum, using calldata or blobs; other systems marketed as L2s may use an external data-availability network or committee. If the data is unavailable, users may be unable to independently recover the state even when a proof system is present. Data availability also does not mean that historical data remains retrievable forever.

3. Transaction ordering and inclusion. A sequencer usually offers a fast path for ordering transactions. A single sequencer can delay, reorder, or censor transactions and can go offline. Some systems provide a separate forced-inclusion or fallback mechanism through Ethereum, but its operation, delay, cost, and scope are project-specific. Do not assume that every L2 has the same escape route or that it provides instant censorship resistance.

4. Upgrade and pause authority. A multisig, Security Council, DAO, or company may be able to upgrade contracts, pause withdrawals, change proof systems, or appoint operators. Check who controls each permission, the approval threshold, whether actions are delayed, and whether users have a practical exit window before an unwanted change. The name “Security Council” does not imply a standard membership or power structure.


What L2Beat’s stages tell you

L2Beat’s Stages Framework is a way to compare a rollup’s progress toward decentralization and reduced reliance on privileged actors. L2Beat explicitly cautions that a stage is not an overall security rating: a system can have fewer centralized controls and still contain software or proof-system bugs.

Under L2Beat’s published Stage 2 criteria, the fraud-proof system must be permissionless, users must have at least 30 days to exit before unwanted upgrades (with a narrow exception for onchain-detected bugs), and any Security Council must be limited to responding to adjudicable onchain bugs. These are framework criteria, not a guarantee that every user can withdraw in every circumstance. L2Beat’s framework and project assessments can change, so check the current project page rather than relying on an old stage label or a static list.


How to compare two L2s

Before bridging or keeping assets on a network, look up its current contract and risk documentation. Ask:

  • Does the project use Ethereum for settlement and data availability, or does it rely on a separate data layer?
  • What proof or challenge system verifies state updates, and who is allowed to use it?
  • Who operates the sequencer, and what mechanism can a user use if a transaction is censored?
  • Who can upgrade or pause the bridge and core contracts, and what delay or exit period applies?
  • Which assets and contracts are covered by those protections? A bridge, app, or token can introduce additional risks.

The point is not that a centralized sequencer automatically has custody of user funds, or that a rollup is safe merely because it posts data to Ethereum. Each security claim depends on the specific proof system, data model, contract permissions, and exit path. “Secured by Ethereum” is a starting description; it is not a substitute for checking those components.


Social Media Sentiment

A small sample of public discussions shows different priorities, not a consensus among L2 users. In an August 2023 r/ethfinance thread about sequencer decentralization, participants focused on censorship, transaction ordering, and multisig concentration. In a December 2025 L2Beat forum discussion about stage criteria, a counterproposal argued that forced transactions, sequencing decentralization, and upgrade authority should be evaluated as distinct dimensions. Both discussions are in English, and this small sample cannot represent the wider community.

Last updated: 2026-10


Related Articles

Related Glossary Terms

Sources