1.22 Consensus

Consensus is the mechanism by which independent network participants converge on an accepted state according to predefined rules. Consensus does not mean every participant agrees politically; it means valid participants follow a rule set that produces a common history.

Learning objectives

• Validity rules
• Forks
• Finality
• Chain selection
• Economic incentives
• Governance

Why this matters

"Decentralised" is often used as a single yes/no label. This lesson replaces that with a specific, testable question: who actually needs to agree for a rule change to take effect, and what happens when they don't?

Core teaching

Consensus is the process and rule set by which distributed, mutually distrusting participants converge on which transaction history to accept as valid. It requires a shared, precise definition of what counts as a valid block and transaction — without that shared definition, participants could not even meaningfully disagree, let alone agree.

A concrete historical test of this happened in 2017: a proposed rule change known as SegWit2x had backing from a significant share of mining power and several large companies, but was ultimately not adopted network-wide, because enough node operators and users did not run the software implementing it. This demonstrates directly that raw hashing power alone does not unilaterally determine which rules the broader network follows — social and technical consensus among the people actually running node software plays a decisive role too.

Worked example

In 2017, a proposed change to Bitcoin's rules (commonly referred to as SegWit2x) was ultimately not adopted by the network despite backing from a significant share of mining power and some large companies, because a large enough portion of node operators and users did not run the software implementing it. This is a real historical illustration that raw hashing power alone does not unilaterally determine which rules the wider network follows — social and technical consensus among node operators and users plays a decisive role too.

This matters for evaluating any blockchain's claimed decentralisation: ask specifically who would need to agree for a contentious rule change to actually take effect across the network, not just who has the most computational power.

Deeper analysis

Consensus is the process by which independent participants converge on which state or history is accepted under a set of rules. Bitcoin uses rule-based validation together with proof-of-work to resolve competing valid chains. Nodes reject invalid blocks even if a powerful miner produced them. This makes consensus more than a popularity contest: the participants are checking whether proposed changes satisfy the rules they recognise.

Consensus and governance are related but different. A developer can publish a software change, but users and node operators decide whether to run it. Businesses can choose which chain they recognise. Miners can choose where to direct hash power. A contentious rule change can therefore become a coordination problem involving technical compatibility, economics and social agreement. Studying forks is useful because it shows where protocol rules end and collective choice begins.

Common misconceptions

• Consensus rules and governance are related but not identical.
• A hard fork can change the rules if network participants adopt new software.
• Different consensus models make different trade-offs.

Application lab

Research one real historical Bitcoin protocol disagreement (a "fork" event) from a reputable source. Identify which groups favoured which outcome, and what ultimately determined which chain or rule set the majority of users and node operators followed.

Practical exercise

Write two sentences explaining why "51% of mining power supports this change" is not automatically the same as "the network has reached consensus on this change".

Knowledge check

Question: What did the 2017 SegWit2x episode demonstrate about how much control mining power alone has over Bitcoin's rules?

Model answer: Despite backing from significant mining power and large companies, SegWit2x was not adopted network-wide because a large enough share of node operators and users did not run the software — showing that mining power alone does not unilaterally determine the rules the network follows.

Case study prompt

Research the SegWit2x episode (or another Bitcoin protocol disagreement) from a reputable source. Identify which groups favoured which outcome, and what specifically determined which rule set the majority of the network actually followed.

Key takeaways

• Consensus requires a shared, precise definition of validity before agreement is even possible
• Mining power alone does not unilaterally decide protocol rules
• Node operators and users running specific software are a decisive part of consensus
• "Decentralised" is better analysed as a specific, checkable question than a single label

Further exploration

Lesson 1.23 examines the specific mechanism, proof of work, that Bitcoin uses to make dishonest participation in this consensus process economically costly.