What decentralization is, and how you measure it
Decentralization is not a slogan but a measurable distribution: how many independent nodes run the network, and how many different pieces of software those nodes use. We explain why running your own node means not having to trust anyone, why one dominant client is a risk, and why decentralization is a degree rather than an on-off switch.
In brief
Decentralization means a network's operation does not depend on a single company, server or piece of software.
It helps to think of it as a distribution rather than a slogan: how many independent computers run the network, and how many different programs those computers use.
What a node does
Every computer connected to the network is a node. A node's job is not to watch but to check. Ethereum's documentation puts it this way:
"Your node verifies all the transactions and blocks against consensus rules by itself. This means you don't have to rely on any other nodes in the network or fully trust them."
The load-bearing part is the end of that sentence: you do not have to trust anyone else. That is what decentralization buys in practice.
Client diversity
Node count alone is not enough. If every node runs the same software, a single bug in that software hits the whole network at once.
That is why having several clients written by different teams is a deliberate safety measure rather than a weakness. The stated goal is for no client to dominate the network.
A degree, not a switch
Decentralization is not on or off but a line running from little to a lot. One network can be more distributed than another while both use the same word.
Four questions are enough to judge it yourself:
- How many independent nodes run the network?
- Who runs them, and how many separate organisations?
- How many different client programs are in use?
- Does one of them run far ahead of the rest?
Commonly confused
Node count is not distribution. A thousand nodes sitting on one company's servers make a large number and a small spread.
A validator is not a node. A validator takes part in producing blocks; a node checks the rules. A network can have many validators and few independent nodes.
Decentralization is not a feature-list item. A project may describe itself that way; the four questions above either support that or they do not.
Risks
Biggest uncertainty Decentralization is a degree, not a binary; how distributed a given network actually is can only be said by measuring its node and client spread.
Three traps people fall into while learning this:
- Taking the word for a measurement. Projects describing themselves as decentralized is common and proves nothing on its own. Until the four questions above are asked, it is a claim.
- Reading a single number. Node count can look high while the spread is narrow. The number needs "who runs them" beside it.
- Treating today's reading as permanent. Client distribution shifts over time; a chart from six months ago does not describe today.
Sources
This article rests on the sources below. Whether each has a permanent copy is stated next to it.
- #1
Düğüm tanımının, kendi düğümünü çalıştırmanın neden güven meselesi olduğunun ve istemci çeşitliliğinin kaynağı.
ethereum.org· our own copy· archive copy· no screenshot· cited 3 times in the text
Evidence chain: 1 sources
Tweets get deleted, sites go down. Below is whether a durable copy exists for each source.
Sources (1)
- #1
Düğüm tanımının, kendi düğümünü çalıştırmanın neden güven meselesi olduğunun ve istemci çeşitliliğinin kaynağı.
“Your node verifies all the transactions and blocks against consensus rules by itself. This means you don't have to rely on any other nodes in the network or fully trust them.”
ethereum.org/en/developers/docs/nodes-and-clients/our own copyopen in a new tab - no screenshot captured
- archived copy
- captured on Sep 7, 2026, 10:39 PM
content hash
432cc69fee…7f0d3e