Crypto and decentralization get treated as synonyms in most conversations. Bitcoin maximalists call it the great decentralization movement. Critics say it's a myth. Neither is completely right — and the confusion matters, because how decentralized a system is changes what it can and can't do, what risks it carries, and who actually controls it.
The honest answer: it varies enormously. Some crypto systems are deeply decentralized. Others are controlled by a small number of entities in ways that would make most people uncomfortable if they understood the structure.
Decentralization isn't binary. It exists across multiple dimensions simultaneously — consensus, development, wealth distribution, geographic concentration, infrastructure dependencies — and a system can score high on one while failing badly on another.
Start with consensus. Bitcoin's proof-of-work network has miners distributed across many countries, with no single entity consistently controlling more than 50% of hashrate. Ethereum's proof-of-stake has over 900,000 validators, but roughly one-third of all staked ETH runs through Lido, a single liquid staking protocol. That's a concentration risk even if validators are geographically spread. The mechanism works — but the actor distribution doesn't match the "decentralized" label people attach to it casually.
Then there's development control. Bitcoin's protocol changes require rough consensus across developers, miners, node operators, and users who frequently disagree — which is why it changes slowly. That slowness is the decentralization working as designed. Solana's development is driven primarily by Solana Labs and the Solana Foundation. That's not inherently bad, but it's a different architecture of control. Changes can happen faster. The tradeoff is obvious if you look for it.
Wealth distribution matters too. Most crypto assets have token distributions concentrated among early insiders, venture funds, and founding teams. When a handful of wallets hold most of the supply, governance votes and economic incentives follow those wallets. Bitcoin is old enough that distribution has dispersed somewhat — but it still skews heavily toward early adopters and large miners.
The one people overlook most: infrastructure concentration. Many "decentralized" applications run on Ethereum but depend on Infura or Alchemy for RPC access — centralized API providers that applications use to read and write blockchain data. When Infura has an outage, large parts of the ecosystem feel it immediately. Most wallets, even self-custody ones, pull data from these providers. The protocol is decentralized; the plumbing often isn't.
Finally, geographic concentration. Bitcoin mining shifted heavily to the US, Kazakhstan, and Russia after China's 2021 ban. Better distribution than before — but still clustered in ways that create regulatory exposure.
Coordination requires structure. The more decentralized a network is, the slower and more expensive it becomes to change — that's not a bug for systems like Bitcoin, which prioritize immutability over governance speed. But for blockchains competing with each other or with traditional financial systems, decentralization is often the first thing traded away for performance.
This is the blockchain trilemma operating in practice: decentralization, security, and scalability don't all maximize simultaneously. Networks make explicit or implicit choices about which to optimize. Most don't advertise what they deprioritized.
Regulatory pressure is a soft constraint that becomes a hard one quickly. When governments identify actors they can target — companies, foundations, development teams — they can exert pressure that bypasses the "decentralized" label entirely. The Tornado Cash sanctions applied to a protocol, not a company. They showed how permissioned infrastructure can selectively choke tools that are technically decentralized at the protocol layer.
Two trends worth tracking.
First, decentralization is quietly getting worse in some dimensions as the ecosystem matures. Institutional capital concentrates into fewer validators, protocols, and infrastructure providers. This isn't a conspiracy — it's the natural result of economies of scale and professionalization.
Second, there's genuine technical work aimed at reducing infrastructure concentration. Ethereum's DVT (distributed validator technology) projects — Obol and SSV Network — aim to fragment validator keys across multiple operators, reducing single-point failure risk. The Portal Network is working toward stateless clients so users don't need centralized RPC providers. These are early-stage, but they're addressing real structural problems rather than just improving optics.
DVT adoption reaching a meaningful share of Ethereum validators. Liquid staking concentration falling below 25% for any single provider. Continued geographic diversification in Bitcoin mining. Growth in self-hosted RPC nodes and light client usage, reducing dependence on Infura and Alchemy.
Lido or another liquid staking protocol crossing 33% of staked ETH — making finality disruption theoretically accessible from a smaller set of correlated actors. A government successfully coercing a major development foundation into protocol-level changes. Censorship by infrastructure providers becoming persistent and effective rather than temporary.
Now: Liquid staking concentration is a present-tense structural issue. Lido's share has hovered around 30–32% without material decline despite sustained community pressure. Infrastructure dependence is today's risk, not a future one.
Next: DVT and decentralized RPC solutions are in early deployment — worth monitoring, not yet at the scale that would change the risk picture.
Later: Whether governance mechanisms can actually enforce decentralization limits before concentration creates capture is a long-horizon question. The mechanisms exist in theory. Whether they hold under real economic pressure is still open.
This post maps how decentralization actually works across dimensions — consensus, development, wealth, infrastructure, geography. It doesn't assess which blockchains are sufficiently decentralized for any particular use case. That depends entirely on what you're protecting against and what risks you're willing to carry.
"Is it decentralized?" is almost always the wrong question. "Decentralized enough for what?" is the one worth asking.




