Staking Provider Concentration

How it happens

Most holders stake through an intermediary: an exchange, a liquid staking protocol, or a professional operator, and those intermediaries run many validators on common infrastructure with common configuration. That commonality makes errors correlated rather than independent, since a duplicate-signing misconfiguration or a cloud region outage affects an operator's entire fleet at once. At the network level, concentration interacts with protocol thresholds, because a single operator or protocol controlling more than one third of stake can affect finality and more than two thirds can finalize a chain outright. The same concentration appears in block building, where a small number of relays and builders assemble most blocks and therefore decide what gets included.

What you can actually observe

Look at stake share by operator, by liquid staking protocol, and by client software, and at the share of blocks produced through the largest relays and builders. Check the cloud provider and geographic distribution disclosed by large operators, and whether a liquid staking protocol's node operator set is permissioned or open. Slashing history and mass missed-attestation events are recorded on-chain.

Precedent

An early professional operator on Ethereum's beacon chain had a batch of its validators slashed simultaneously after a redundant setup caused duplicate signing, showing that one configuration decision applies across an operator's whole fleet.

What makes it more or less material

Consider the largest operator's share against protocol thresholds, whether operators run diverse clients and regions, whether the node set is permissioned, whether withdrawal keys are held by the user or the provider, and the slashing record.