Soft Fork and Hard Fork: How Bitcoin Rules Change

Soft Fork and Hard Fork: How Bitcoin Rules Change

A soft fork is a change to Bitcoin’s consensus rules in which only blocks and transactions that were valid before are made invalid. A hard fork is a change to those rules after which blocks created under the new rules can be invalid under the old rules. Consensus rules are the rules that full nodes use to check each block and the transactions inside it.

What Are Consensus Rules, and Who Applies Them?

Consensus rules are the block validation rules that full nodes follow to stay in consensus with other nodes.

A node is a computer that connects to the Bitcoin network. A full node keeps its own copy of the blockchain, and that copy holds only blocks the node has validated itself, so a full node checks each block instead of taking another node’s word for it.

Full nodes that apply the same rules agree on which blocks are valid. A change to the consensus rules is called a consensus change or a protocol upgrade. A soft fork and a hard fork are two ways such a change can relate to the old rules.

What Is a Soft Fork, and Why Do Older Nodes Still Accept Its Blocks?

A soft fork is a change to the consensus rules in which only blocks and transactions that were valid before are made invalid. In plain terms, a soft fork tightens the rules: every block that follows the new rules also follows the old rules, but some blocks that the old rules allowed are no longer allowed. A soft fork is also written “softfork.”

A soft fork is called backward compatible because a node that has not upgraded recognizes the new blocks as valid. That node keeps accepting the same blocks as upgraded nodes, and it stays on the same chain as long as most of the network’s hashrate enforces the new rule.

Hashrate is the combined speed at which all miners compute on the network. If most of it did not enforce the new rule, blocks that break the rule would be valid to older nodes but ignored by upgraded nodes, so the two groups could end up on different chains.

Backward compatible does not mean that an older node checks the new rule. SegWit, for example, is a soft fork specified in BIP 141. A BIP, or Bitcoin Improvement Proposal, is a numbered design document for Bitcoin.

Nodes that have not upgraded to SegWit do not validate its witness data. Witness data is a separate part of a transaction. Only upgraded nodes enforce the new rule.

What Is a Hard Fork, and Why Can It Split the Chain?

A hard fork is a change to the consensus rules after which blocks created under the new rules can be invalid under the old rules. A hard fork makes blocks or transactions valid that were invalid before, so the rules loosen. A hard fork is also written “hardfork.”

When nodes do not upgrade, a permanent divergence in the blockchain can follow. Existing developer documentation says this divergence commonly occurs when nodes that have not upgraded cannot validate blocks created by upgraded nodes that follow newer consensus rules.

A node that has not upgraded keeps the old rules, and blocks made under the new rules can be invalid under them, so the node can be unable to validate those blocks.

A chain split is the outcome when the divergence leaves two chains, one for the nodes that have not upgraded and one for the nodes that have.

A Bitcoin hard fork would be a change of this kind to Bitcoin’s own rules, such as a change to the structure of a block or to the difficulty rules.

Soft Fork vs Hard Fork: How Do They Compare?

A soft fork and a hard fork differ most in how a node that has not upgraded treats blocks made under the new rules.

QuestionSoft forkHard fork
What changes in the rules?Only blocks and transactions that were valid before are made invalid, so the rules become stricter.Blocks created under the new rules can be invalid under the old rules, so the rules can loosen.
Which nodes must upgrade?No node has to upgrade to keep accepting the same blocks, but only upgraded nodes enforce the new rule, and the nodes that have not upgraded stay on the same chain only while most hashrate enforces it.Every node that wants to follow the chain made under the new rules has to upgrade.
What happens to a node that does not upgrade?The node keeps accepting the same blocks as upgraded nodes, and it stays on the same chain as long as most hashrate enforces the new rule.The node can be unable to validate blocks made under the new rules, so the blockchain can diverge permanently into one chain for each group of nodes.
Which Bitcoin upgrades are examples?SegWit (BIP 141) and Taproot (BIP 341) were both deployed as soft forks.None described in this entry.

How Does a Bitcoin Soft Fork Activate?

A Bitcoin soft fork activates when its new rules start to apply to blocks. BIP 9 describes a way to deploy a soft fork with version bits. Each block carries a block version, which is a number that the block’s creator sets.

Version bits use single bits of that number to flag a specific change. Miners create blocks. A miner who is ready to enforce a change sets that change’s bit in the blocks it finds, which is called miner signaling.

BIP 9 counts signals in periods of 2,016 blocks. On the main Bitcoin network, a change locks in after a period in which at least 1,916 of the 2,016 blocks (95%) signal for it, and it becomes active one further period later. The figure of 1,916 is BIP 9’s main-network value and the one SegWit used. It is not a rule for every soft fork.

SegWit is the upgrade that added witness data. It was deployed as a soft fork under BIP 141 with version bit 1.

SegWit activated at block 481,824. A block height is the number of blocks that come before a block in the chain, so the genesis block has a height of zero. That block carries a timestamp of August 24, 2017 at about 01:57 UTC. The miner who finds a block sets its timestamp, so the minute is approximate.

Taproot is a later upgrade that added new spending rules. It was deployed as a soft fork under BIP 341 with version bit 2. Its threshold was lower than BIP 9’s default: 1,815 of 2,016 blocks (90%).

Taproot also had a minimum activation height of 709,632. A minimum activation height is the earliest block height at which a deployment can activate. Taproot activated in November 2021 at that height.

What Is Not a Fork, and What Else Does the Word Mean?

The word fork has more than one meaning. Here, a fork means a change to the consensus rules, either a soft fork or a hard fork. The word is also used for a chain split, which is the outcome when a hard fork leaves two chains.

A temporary fork is a different thing. It typically occurs when two or more miners find blocks at nearly the same time, so that two blocks have the same height. Nodes are designed to follow the chain with the most accumulated work, and a block left outside it is a stale block, most likely because another block at the same height had its chain extended first.

On code-hosting platforms such as GitHub, a fork is a repository that starts as a copy of another repository. A repository is a project’s stored code. This meaning has nothing to do with Bitcoin’s consensus rules.

The halving schedule is part of Bitcoin’s existing consensus rules. A node that applies Bitcoin’s rules rejects a block that claims more than the block subsidy plus transaction fees, and the subsidy halves every 210,000 blocks. A halving therefore takes effect under the existing rules and is not a rule change.

The words soft and hard do not rank the two kinds of change. Hard says nothing about importance or quality, and neither word says which change is better or says anything about markets.

November 18, 2026

GoMining News

You might be interested in: