Blockchain Forks

A chain fork happens when nodes temporarily see multiple valid branches extending the same parent. This can occur without any protocol change when two blocks are produced close together. A rule fork happens when software versions disagree about validity rules. Mixing these meanings causes confusion because one is usually resolved automatically while the other can split a community and network.

The key questions are: did history diverge under the same rules, or did the rules themselves diverge?

Miner A finds block X while Miner B finds block Y from the same parent. Some nodes hear about X first and others hear about Y first. Both branches can be valid. When a later block adds more accumulated work to one branch, Bitcoin nodes converge on that branch and transactions only present on the losing branch return to the mempool if still valid.

The discarded valid block is commonly called stale. The event is a normal consequence of propagation delay, not a protocol failure.

A soft fork tightens validity rules so upgraded nodes reject some blocks that older nodes would have accepted; it can remain backward-compatible under specific deployment conditions because old nodes still accept upgraded blocks. A hard fork changes rules so blocks valid under the new rules may be rejected by old nodes, making persistent chain separation possible if both rule sets retain support.

Compatibility is about validation logic, not branding. Two groups can share a code history yet become separate networks because they accept different blocks.

A rule change becomes meaningful only when miners or validators, nodes, exchanges, wallets, application developers, and users decide which software and chain to support. Technical compatibility determines what can coexist, while social and economic coordination determines which branch receives infrastructure and value.

A blockchain protocol cannot force every participant to install the same version.

The word fork is overloaded, so the first task is to identify which kind of divergence is occurring. A temporary chain fork can arise when two valid blocks are produced near the same time and different parts of the network see them in different orders. The consensus fork-choice rule later causes nodes to converge on one branch, while the other becomes stale or noncanonical.

A protocol-rule fork is different. Software changes can alter which blocks or transactions a node considers valid. In a backward-compatible tightening of rules, upgraded nodes may accept a subset of what older nodes accept. In an incompatible rule change, upgraded and non-upgraded nodes can permanently disagree and maintain separate histories if both communities continue operating.

Forks therefore expose the distinction between consensus rules and social coordination. Software determines what a node will accept, but people and organizations decide which software to run, which assets or markets to recognize, and whether to follow a changed rule set. Even a technically clean upgrade can create coordination risk if deployment is fragmented.

When studying a fork, ask whether the disagreement is temporary or rule-based, whether both branches remain economically active, and whether replay protection, address formats, or application assumptions change across the split.

1. Distinguish a temporary chain fork from a protocol-rule fork.

2. Why can two honest producers create competing valid blocks without anyone attacking the network?

3. What role does fork choice play after a temporary branch appears?

4. How can a software upgrade create a persistent split?

5. Why are social and economic coordination relevant even though validity rules are encoded in software?

6. Correct this statement: “Every blockchain fork creates a new cryptocurrency.”