What is Satoshi Nakamoto's coefficient? Why is it important?

Satoshi Nakamoto's coefficient

Satoshi's coefficient refers to the minimum number of independent entities that need to collude to undermine the blockchain consensus. In proof-of-work, this means a pool with enough consolidation power to rewrite the chain; in proof-of-stake, it means a verifier operator with enough consolidation pledge to prevent the chain from running. A higher coefficient means that more parties need to agree before any damage occurs; a lower coefficient means fewer parties need to agree.

This is why this number is more valuable than the number in any financing presentation. Ethereum has approximately 1,278,000 validators, but its on-chain data shows that Satoshi Nakamoto has a coefficient of 1. The gap between this figure and the effective figure is exactly what this indicator will reveal.

Where did this number come from?

In July 2017, Balaji Srinivasan and Leland Lee published the article "Quantitative Decentralization". Their criticism is straightforward: decentralization is the main selling point of Bitcoin and Ethereum, but few people quantify it.

They borrowed the framework of economics. The Lorentz curve describes the uneven distribution of wealth among people, and the Gini coefficient compresses the curve to a number between 0 and 1. Srinivasan and Lee applied the same idea to blockchain and added a step: Break the system into basic subsystems, calculate the minimum number of entities needed to control each subsystem, and then take the lowest result among all subsystems.

This minimum result is the minimum Nakamoto Satoshi coefficient. The subsystems they list include: mining or pledge, client software, developers, node operators, exchanges and token ownership. In practice, almost all data panels report only the consensus layer because this layer can be cleanly quantified and is the first layer to fail.

The name is both a tribute to Satoshi Nakamoto and a point to the characteristics that Bitcoin was originally designed to have.

How to calculate?

The method is simple, but data collection is difficult.

First, identify entities and their controlling shares, grouped by actual operators rather than by individual nodes or verifier keys. Second, rank from the largest share to the smallest share. The shares are then accumulated until the critical threshold is exceeded. Finally, statistics how many entities are needed, and this number is the coefficient.

The threshold depends on consensus design:

The proof-of-work uses 51% computing power, which is the critical point at which most attacks or chain reconstructions become possible. Proof of stake typically uses a pledge of 33%, which is enough to prevent finality in a BFT-style system. Some trackers use 50% instead.

Take Bitcoin real-time mining pool data as an example. For the seven days ending July 17, 2026, data shows that Foundry USA accounted for 27.6% of computing power, F2Pool accounted for 17.8%, AntPool accounted for 17.3%, ViaBTC accounted for 9.5%, and SpiderPool accounted for 5.7%. Foundry plus F2Pool totals 45.4%, which does not reach the threshold. In addition, AntPool reached 62.7%, exceeding the threshold. Three mining ponds, with a coefficient of 3.

The data also shows this number. Bitcoin runs in 145 mining pools, three of which determine the outcome.

What is the current status of major blockchains?

Snapshot taken from the decentralized dashboard, taken on July 17, 2026 at 12:52 UTC:

Polkadot: 166

TON: 72

Avalanche: 25

Sui: 19

Solana: 18

Cardano: 15

Aptos: 14

ICP: 14

TRON: 13

Algorand: 12

Tezos: 12

MultiversX: 11

NEAR: 9

Sei: 8

BNB Chain: 7

Hedera: 7

Polygon: 4

Bitcoin: 3 (there is no single official central account)

Stellar: 3

Ethereum: 1

Compare these numbers with the number of validators and the rankings will be reshuffled. Polkadot derived a coefficient of 166 from 600 validators;TRON had only 27 validators, with a coefficient of 13, meaning that nearly half of the super representatives needed to act in sync;MultiversX ran 3,250 validators, with a coefficient of 11; and Cardano ran 2,088 validators, with a coefficient of 15.

The number of verifiers in Ethereum exceeds the sum of all other chains in the list, but by a factor of 1, because the data puts pooled and liquidity pledge providers under the names of the operators that actually hold the keys. The number of validators does not equal the distribution of control.

The rollup illustrates the same problem in a clearer way. Arbitrum, Base, Optimism, Starknet, and Etherlink each have only one validator, with a coefficient of 1. Their sorters are centralized, which is a well-known fact in the industry, but few data panels bother to quantify.

Why is it important?

Attack Resistance

It quantifies the actual difficulty of launching a 51% attack, censoring a campaign, or stopping a chain.

Trust minimization

Blockchain sells without having to trust third parties. A factor of 1 or 2 means that you actually still trust third parties, no matter how marketing promotes it.

Risk assessment

Concentration of control increases the probability of collusion, regulatory capture, and single point of failure.

Design Objectives

The project uses it to evaluate itself and demonstrate the rationality of pledge caps, delegation limits, and anti-concentration rules.

It can't tell you anything

This indicator has practical limitations and it would be wrong to regard it as a safety score.

Entity recognition is imperfect. Two validators running under different names for the same company would count as two, and dozens of validators located in the same cloud area would count as dozens, but neither would fit into reality in a crisis.

Numbers change. Transfer of pledge amount, merger of mining pools, and upgrade of agreements. Screenshots taken six months ago are almost meaningless today.

And it only examines one dimension. Client diversity, developer concentration, governance capture, and geographical distribution are not within the scope of calculations. A chain may have a high coefficient, but it may still be defeated by a client vulnerability or a regulatory agency.

The rate of ground change can be seen in the data. TON's coefficient fell 13.25% in one day to 72, and its number of validators fell 13.27% over the same period. The scale behind a score is invisible just from the score itself. Both Bitcoin and Fogo have a coefficient of 3, but Bitcoin has 145 mining pools and a computing power of 1.11K EH/s, while Fogo has only 7 validators. The scores are the same, but nothing else has in common.