Chapter 9 - 0 of 10 quizzes passed
Consensus and Reorganizations
Consensus is how independent participants converge on one valid history without a leader.
- Explain independent validation and the heaviest-chain rule
- Distinguish soft forks, hard forks, and chain reorganizations
Same rules, separate checks
Consensus is not a meeting or a vote. Each node independently applies the same rules to transactions and blocks. Shared rules let strangers converge on the same valid ledger history. A miner proposing an invalid block is ignored, no matter how much energy it spent.
The heaviest chain
Sometimes two miners find competing valid blocks at nearly the same time. Nodes follow the valid chain with the most accumulated proof of work. One branch becomes stale as the network builds on the other. Shallow reorganizations happen; deeper ones are rare and expensive. “Confirmed” is probabilistic, not absolute, which is why wallets use confirmation thresholds.
Forks and governance
A soft fork tightens the rules and stays compatible with old nodes; a hard fork loosens or changes them and requires broad adoption. A user-activated soft fork (UASF) is a coordination attempt by node operators. Rules can change when users, miners, and businesses converge — not by decree, though change is possible. The social layer matters as much as the code.
Hard to change
Because anyone can run a node and each node chooses what rules to accept, Bitcoin consensus rules are hard to change by decree. Durable consensus comes from broad agreement among users who verify for themselves. That is a feature for predictability and a weakness for fast protocol evolution. Both are true.
What you should take away
Consensus is independent validation converging on the heaviest valid chain. Reorganizations are normal at shallow depth; forks and rule changes require coordination across users, miners, and businesses.
Retrieve, then apply
Explain a temporary reorganization, a soft fork and a hard fork without treating them as synonyms.
Check your explanation
A reorg changes the selected valid history. A soft fork tightens validity rules; a hard fork introduces rules incompatible with old validation. Adopting new software rules is different from selecting history.
Checkpoint
Sources
Reviewed 2026-10-25 · not financial advice