Level 9 · Advanced technical layer

How Bitcoin changes: BIPs, soft forks and consensus

From proposal and implementation through review and activation to the rules nodes actually enforce.

Article: 96
Reading time: 17 minutes
Reviewed: 10 September 2026

In a nutshell

A BIP is a public proposal or document, not an order to the network. Change takes effect through implementation, review, deployment and adoption. A soft fork tightens validity compatibly for old nodes; a hard fork makes rules that are not backward compatible.

A BIP records; it does not rule

BIP 3 describes technical, informational and process proposals. A number or status reflects the document process, not a community-wide vote. Editors assess format and readiness, not authority to change Bitcoin.

Code passes a separate filter

Bitcoin Core changes receive public review and tests. A maintainer can merge code into that project but cannot install it on other people's nodes. Operators, other implementations, wallets, businesses and miners choose compatible software.

Soft fork and hard fork

A soft fork narrows valid blocks, so an old node may accept a new block under looser old rules without checking the new restriction. A hard fork expands or incompatibly changes validity; disagreement can leave two persistent chains and assets.

Activation coordinates risk

BIP 9 used version bits, signalling windows, thresholds and a delay before enforcement. Signalling measures one kind of readiness, not a universal political vote. Outcomes depend on enforced code, economic acceptance and willingness to tolerate a split.

Level 9 · Advanced technical layer

Terms to know

BIP: A public Bitcoin Improvement Proposal, standard or process document.
Soft fork: A backward-compatible tightening of validity from old nodes' perspective.
Hard fork: A rule change whose newly valid data may be invalid to old nodes.

Common misconception

Bitcoin Core developers or miners can vote in a rule and force everyone to use it.

A more accurate explanation

Developers propose code and miners can signal or produce blocks, but each node enforces software its operator chose; incompatibility can cause a split.

A more accurate explanation

Is governance without a formal authority chaos?

Coordination is slower and less tidy than a company decision, but makes unilateral changes harder. Power and politics still exist; they are distributed across technical and economic roles.

Key takeaways

01A BIP is a proposal and record, not an order.
02Merging code does not update other nodes.
03Soft forks tighten rules; hard forks can split compatibility.
04Activation coordinates adoption but does not replace it.

A child-friendly recap

In very simple terms

A BIP is a public proposal, not an order. A rule takes effect only when people run software that enforces it; Bitcoin has no single boss or update button.

Reviewed: 10 September 2026