Is Ethereum Staking Making the Network More Centralized?

Ethereum’s move to proof-of-stake changed who helps produce and finalize blocks, but “is staking centralized?” has no single yes-or-no metric. The answer depends on which layer you mean: how much ETH is routed through a staking protocol, who operates the validators, who can change a service’s rules, or how independent the wider network’s software and infrastructure are. These forms of concentration can overlap, but they are not interchangeable.

What does “centralization” mean in staking?

A staking pool lets people stake without each person running a validator. A liquid staking protocol may issue a token such as stETH to represent a claim on pooled ETH and its rewards. That token does not itself validate blocks. The protocol allocates stake to node operators, who run validator software and hold validator signing keys. A separate governance layer may set protocol parameters, admit operators, or approve upgrades.

So a protocol’s share of staked ETH measures the size of the service, not the number of people or independent operators behind it. Conversely, a long validator list does not prove that the keys are operated independently: one organization can run many validators. To understand concentration, look at the pool, operator, governance, custody, client, and infrastructure layers separately. Ethereum.org’s pooled-staking overview also distinguishes a liquid-staking token from directly operating a validator.

What current data shows—and what it cannot show

Ethereum.org currently describes liquid-staking protocols as accounting for around one-third of all staked ETH. That broad category is useful context, but it is not a measure of how many independent people run validators or how much control any one operator has. For provider-level trends, hildobby’s live Ethereum staking dashboard on Dune tracks reported staking entities. Its values change, and entity labels depend on how deposits and providers are classified. A chart can show concentration in a product category; it cannot by itself prove that every operator assigned to that category acts together.

Validator counts have a similar limitation. One organization can operate many validator keys, while a protocol can spread stake among operators with separate infrastructure. A count of validators is therefore not the same thing as a count of independent decision-makers. Older snapshots should not be presented as current distribution data.

Why the one-third threshold matters—and what it means

Ethereum’s proof-of-stake documentation says that disrupting chain liveness can require control of at least roughly one-third of total staked ETH under relevant attack or failure conditions. That threshold concerns stake weight in consensus, not one-third of all ETH in circulation and not a simple count of validators. It also does not mean that every protocol with a large market share can unilaterally stop finality: the operators and governance behind that stake would have to matter in the way the threat model assumes.

The same documentation distinguishes other thresholds: around 51% of staked ETH can affect the contents of future blocks, while rewriting finalized history would require more than two-thirds and trigger a different response. These are protocol-level security scenarios, with slashing and community recovery mechanisms—not a direct conversion from a dashboard’s brand share to control. The Ethereum proof-of-stake FAQ explains the liveness, block-control, and finality thresholds.

Lido: protocol share is not the same as one operator

Lido is a useful case study because it is a large staking protocol and its governance and operator structure are publicly documented. Lido’s current documentation describes a curated operator module as well as Community Staking Modules with permissionless entry. A protocol can therefore aggregate deposits while delegating validator work across multiple operators. That distribution reduces the chance that a single node operator is the only point of failure, but it does not erase the protocol’s smart-contract, governance, or operator-selection risks.

Distributed Validator Technology can split validator signing responsibilities across multiple machines or operators, helping reduce single-operator failure risk. It does not automatically decentralize the governance that selects operators or controls a staking service. Lido’s staking-module documentation is the source for its current module structure; Ethereum.org separately cautions that some pools concentrate stake among chosen operators.

What the Pectra upgrade changed

The 2025 Pectra upgrade activated EIP-7251. It raised the optional maximum effective balance for a validator to 2,048 ETH while keeping 32 ETH as the minimum activation balance. This lets operators consolidate validator keys and lets eligible validators compound rewards. Fewer validator records after consolidation would not, on its own, mean that stake became more concentrated: the relevant question is whether the same actors control a larger share of total stake.

Pectra also included EIP-7002, which lets a withdrawal-address holder trigger a validator exit. That can reduce reliance on a node operator cooperating with an exit request in supported setups. These changes improve operational flexibility; they do not remove pool, governance, custody, or infrastructure concentration. The Ethereum Foundation’s Pectra announcement and EIP-7251 specification describe the changes.

A small community discussion

A September 23, 2026 r/ethereum discussion included one participant who viewed Lido’s Community Staking Module as a way for independent operators to contribute, alongside replies asking about additional risks and whether staking remained worthwhile. That is a narrow sample from one daily thread, not a survey or a measure of Ethereum-wide opinion. It illustrates that users weigh permissionless operator access against operational, contract, and financial risks.

Last updated: October 27, 2026

How to assess the risk

  • Ask what is concentrated: ETH deposits, protocol governance, validator signing keys, node operators, software clients, or hosting infrastructure.
  • Check whether a provider’s stake is distributed across independent operators and whether its entry and exit rules are transparent.
  • Separate a protocol’s market share from the share of stake that could actually coordinate under a specific threat model.
  • Look for mitigations such as distributed validator setups and client diversity, while checking what governance or custody risks remain.

Ethereum.org’s client-diversity guide explains why independent software implementations matter when a bug affects one client. Ethereum staking has real concentration risks, especially when users rely on a small set of services or operators. But a single provider-share number does not prove that Ethereum is controlled by one actor. A useful assessment separates the economic service users choose from the operators who run validators and the stake weight that could coordinate at the consensus layer.

Related Articles

Related Glossary Terms

See Also

Sources