Longest Chain Rule
Bitcoin nodes follow the chain with the most accumulated proof-of-work, ensuring consensus in a decentralized network.
The longest chain rule is Bitcoin's consensus mechanism for resolving conflicts when multiple valid chains exist: every node follows whichever chain has the most accumulated proof-of-work.
The name is slightly misleading. It's not the chain with the most blocks (longest); it's the chain with the most cumulative work. In practice these are usually the same, but during difficulty transitions or attempted attacks they can diverge.
What the rule does:
- When two miners find blocks at the same height at nearly the same moment, the network temporarily splits.
- Each node follows whichever block it saw first, building on top of it.
- As soon as the next block is found on one side, that side has more cumulative work.
- Nodes that were on the other side reorg to the now-heavier chain.
- The losing block becomes a stale block; its transactions return to the mempool.
Why this rule is the foundation of Bitcoin's security:
- Attacking the chain requires more work than the honest network is producing. An attacker trying to rewrite history has to mine a longer fork, secretly, faster than the rest of the world mines the real one. With Bitcoin's ~700 EH/s of hash rate, this requires owning more than half of the global mining industry. Economically infeasible.
- The deeper a transaction sits, the more work would be required to overturn it. This is what the 6-confirmation convention buys: it would take an attacker controlling >50% of hash rate, working in secret, to overturn a 6-confirm transaction. The probability falls exponentially with depth.
- Honest miners are incentivized to build on the longest chain. A miner who finds a block off the main chain doesn't get paid; the block becomes stale.
The longest chain rule is sometimes called "Nakamoto consensus" - the version of consensus Satoshi described in the whitepaper. It's the deceptively simple rule that turns proof-of-work into a globally agreed-upon ledger.
Key takeaways
- Nodes resolve conflicts by picking the chain with the most work
- Deters attackers from rewriting the ledger without immense hash power
- Ensures consistent ledger state across the decentralized network