BC.GAME promotional banner
Subscribe

What Is a Soft Fork? How Soft Forks Work and How They Differ From Hard Forks
10–16 minutes

Last Updated:

November 16, 2026

Crypto fork symbol connecting branching blockchain networks.

What Is a Soft Fork? How Soft Forks Work and How They Differ From Hard Forks

Crypto fork symbol connecting branching blockchain networks.

A soft fork is a backward-compatible change to a blockchain’s consensus rules that only tightens them: some blocks or transactions that were valid before become invalid, and nothing that was invalid becomes valid. Blocks produced under the new rules are therefore still valid to nodes running old software, and the chain does not split as long as most of the hash power enforces the new rules.

A hard fork loosens or changes the rules instead, so nodes that do not upgrade reject the new blocks and the network can split in two. The best-known soft forks are Bitcoin’s Segregated Witness (SegWit), activated in August 2017, and Taproot, activated in November 2021.

How a soft fork works

Every full node in a cryptocurrency network checks each block against the same consensus rules and rejects any block that breaks one. A soft fork adds a restriction to that set. Old nodes do not know about it, but any block that meets the stricter rules also meets the old ones, so they accept it and stay on the same chain. The Bitcoin developer guide gives the condition: if upgraded nodes control a majority of the hash rate, they build a longer chain that old nodes also accept.

Old nodes keep checking the rules they know but cannot check the new ones. Bitcoin developers have used this by giving new meaning to formats that old software already treated as valid. Under BIP 16, old nodes saw pay-to-script-hash (P2SH) spends as non-standard and checked only that the script matched its hash. The SegWit specification says non-upgraded nodes do not see or validate witness data and treat every witness program as anyone-can-spend. BIP 341 did the same for Taproot outputs. Upgraded nodes require a valid signature or script for these outputs, and miners enforcing the soft fork leave out any spend that breaks the rules.

SegWit also made unintended transaction malleability impossible, which BIP 141 calls important for off-chain protocols such as the Lightning Network. Unused opcodes were repurposed in a similar way. BIP 65 turned NOP2 into OP_CHECKLOCKTIMEVERIFY, an absolute time lock, and BIP 112 turned NOP3 into OP_CHECKSEQUENCEVERIFY. Old nodes treat these opcodes as doing nothing. Checking such rules directly needs an up-to-date full node, one of the reasons people run their own Bitcoin node.

Activation methods

Activation is the point at which nodes start enforcing the new rules. Nodes enforcing different rules can end up on different chains, and Bitcoin Optech describes activation mechanisms as designed to reduce that risk.

Flag days and IsSuperMajority

Early soft forks switched on at a height or time written into the software, a style BIP 148 calls flag day activation. Optech dates the earliest known soft fork to block 31,000 on 22 December 2009. For P2SH, miners first signalled support in their coinbase transactions, and Bitcoin 0.6.0 enforced the rules for blocks timestamped from 1 April 2012.

BIP 34 moved signalling into the block version number with a function called IsSuperMajority (ISM). Once 750 of the last 1,000 blocks had version 2 or higher, nodes rejected invalid version 2 blocks. At 950 of 1,000, they rejected all version 1 blocks. BIP 66 and BIP 65 reused these thresholds in 2015. ISM had no expiry and could not run upgrades in parallel.

BIP 9 version bits

BIP 9, assigned in October 2015, gives each soft fork its own bit in the block version field and counts signals per 2,016-block retarget period. The mainnet threshold is 1,916 of 2,016 blocks (95%). A deployment moves through these states:

  1. DEFINED until its start time passes, then STARTED.
  2. LOCKED_IN once 1,916 blocks in one period signal its bit.
  3. ACTIVE one period later, when nodes begin enforcing the rules.
  4. FAILED if the timeout passes before lock-in.

The CSV package (BIP 68, BIP 112 and BIP 113) was the first to use it. Bitcoin Core 0.12.1 signalled it on bit 0 from 1 May 2016, and it activated at block 419,328 on 4 July 2016.

User-activated soft forks: BIP 148 and BIP 91

SegWit signalled on bit 1 from 15 November 2016, but miner support stayed well below 95%. BIP 148, assigned in March 2017, proposed a user-activated soft fork (UASF). From 1 August 2017, its nodes would reject any block that did not signal for SegWit, whatever miners did.

BIP 91 set a lower bar: once 269 of 336 blocks (80%) signalled bit 4, nodes would reject blocks not signalling for SegWit. It locked in on 20 July 2017, after which Bitcoin Magazine described SegWit’s own lock-in as a matter of time. SegWit locked in on 9 August 2017 and activated at block 481,824 on 24 August 2017. Optech notes that the weight of each proposal in that outcome is still debated.

BIP 8 and Speedy Trial

BIP 8 measures its start and timeout in block heights. With its lockinontimeout parameter set, blocks must signal in the last period before the timeout, which guarantees lock-in. Its recommended threshold is 1,815 of 2,016 blocks (90%). Litecoin’s LIP-0003 chose BIP 8 for MWEB with a 75% threshold.

Taproot used Speedy Trial, a short signalling period followed by a delay. Bitcoin Core 0.21.1 watched bit 2 from 24 April to 11 August 2021, with a 90% threshold and a minimum activation height of 709,632. Miners locked Taproot in during June 2021, per Optech Newsletter #153, and it activated at that height on 14 November 2021.

Notable soft forks

Heights for BIPs 34, 65 and 66 are those hard-coded by BIP 90. Heights for CSV and SegWit come from the Bitcoin Core change that did the same for them. A date given with a block height is that block’s UTC timestamp.

NameBIP(s)ChainActivatedWhat it changed
P2SH16Bitcoin1 April 2012 (timestamp rule)Outputs that pay to the hash of a script
Height in coinbase34Bitcoin25 March 2013, block 227,931Blocks must state their height in the coinbase
Strict DER signatures66Bitcoin4 July 2015, block 363,725Signatures must use strict DER encoding
CLTV65Bitcoin14 December 2015, block 388,381Absolute time-lock opcode
CSV68, 112, 113Bitcoin4 July 2016, block 419,328Relative time locks and median time past
SegWit141, 143Bitcoin24 August 2017, block 481,824Separate witness data and a 4,000,000-unit block weight limit
Taproot340, 341, 342Bitcoin14 November 2021, block 709,632Schnorr signatures, SegWit version 1 outputs and tapscript
MWEBLIP-0003LitecoinMay 2022, block 2,265,984Opt-in MimbleWimble transactions in extension blocks
BIP-110110BitcoinDid not activate; Closed 9 August 2026Temporary limits on data fields

MWEB locked in at block 2,257,920, according to an update posted on Litecoin Talk, and ForkLog confirmed its activation on 20 May 2022.

BIP-110, the “Reduced Data Temporary Softfork”, was assigned on 3 December 2025. It would have limited data fields for about one year, for example by making output scripts over 34 bytes invalid except OP_RETURN outputs of up to 83 bytes. Its modified BIP 9 deployment had a 55% threshold (1,109 of 2,016 blocks) and mandatory signalling from block 961,632 to 963,647. Michael Saylor argued against it in July 2026. UseTheBitcoin reported on 9 August 2026 that only 2.53% of miners signalled. The BIP’s changelog marks it Closed that day, “following a chain split with stalled mining”.

Risks and criticisms

Weaker validation for old nodes

A node that has not upgraded no longer checks every rule the network enforces, so it would accept a block that breaks only the new rules. The developer guide warns that such nodes may spread incorrect information. The Bitcoin Wiki names SPV wallets and outdated full nodes as the most exposed to false confirmations.

The July 2015 BIP 66 fork

Block 363,725, mined on 4 July 2015, completed BIP 66’s 950-of-1,000 supermajority, which made version 2 blocks invalid. At block 363,731 a miner that had not upgraded produced one anyway. Other miners built on it without validating it, creating a chain of six invalid blocks. A bitcoin.org alert said roughly half the hash rate was mining this way, a practice called SPV mining. Old nodes and many light wallets showed the 96 transactions in the first invalid block with six confirmations, although none had been confirmed in a valid block. A three-block invalid fork followed on 5 July.

Bitcoin.org told users of Bitcoin Core 0.9.4 or earlier and of SPV wallets to wait for 30 more confirmations than usual. Optech records that all regular transactions were later confirmed in valid blocks, and that no ordinary user lost money.

Chain splits

A soft fork keeps one chain only while most hash power enforces it. If only a minority enforces it, the enforcing nodes reject the majority’s blocks and follow a slower chain of their own. User-activated soft forks accept this risk by design. Ahead of 1 August 2017, bitcoin.org warned of a possible split, and BIP-110 ended in one in August 2026.

Some developers argue that soft forks change the rules without the agreement of every node operator, since old nodes accept the new blocks without being asked. In a September 2015 bitcoin-dev thread on deploying BIP 65, Tier Nolan wrote that miners can carry out a soft fork even when most users oppose it. Mike Hearn argued in the same thread for hard forks, saying they stop old nodes from computing an incorrect ledger while reporting they are in sync. The Bitcoin Wiki counters that miners have an incentive to upgrade, since blocks that ignore the new rules can be reorganized out.

Hard forks

A hard fork loosens or changes the rules so that some invalid blocks become valid. Old nodes reject those blocks, and the developer guide notes that miners on different software can end up on permanently divergent chains. If part of the network refuses the change, two chains continue with a shared history. The site’s history of Bitcoin forks covers Bitcoin’s in detail.

Ethereum’s DAO fork took effect at block 1,920,000 on 20 July 2016 and moved about 12 million ETH into a recovery contract, according to the Ethereum Foundation blog. The unchanged chain continued as Ethereum Classic. Bitcoin Cash split from Bitcoin on 1 August 2017. Its UAHF specification set activation for 12:20 UTC that day, required a first block larger than 1,000,000 bytes and added SIGHASH_FORKID replay protection.

Other networks schedule hard forks as upgrades that clients adopt in unison. Ethereum.org lists, among others, London (5 August 2021), the Merge (15 September 2022), Dencun (13 March 2024), Pectra (7 May 2025) and Fusaka (3 December 2025).

Soft fork vs hard fork

AspectSoft forkHard fork
CompatibilityBackward compatible; old nodes accept new blocksNot backward compatible; old nodes reject new blocks
Rule changeTightens rulesLoosens or changes rules
Node upgrade neededOnly to check new rules or use new featuresYes, to follow the upgraded chain
Chain split riskLow with majority hash power; higher if contested or user-activatedPermanent split if part of the network keeps the old rules
New coinNoOnly if both chains survive
Typical activationMiner signalling (ISM, BIP 9, Speedy Trial) or a UASF dateA set block height or time
ExamplesP2SH, SegWit, Taproot, Litecoin MWEBEthereum DAO fork, Bitcoin Cash, Ethereum upgrades

What a soft fork means for holders and users

A soft fork does not create a new coin, and most holders need to do nothing. Wallets and nodes that have not upgraded keep working on the same chain. You need an upgrade only to use new features, such as SegWit or Taproot addresses, or to have your node check the new rules. The site’s guide to SegWit wallets lists wallets that support the format.

Exchanges sometimes pause deposits or withdrawals around a contested activation. Before 1 August 2017, bitcoin.org warned that many services might stop accepting bitcoin at 00:00 UTC that day or earlier. Check your exchange’s announcements before moving coins near an activation date.

The same notice warned that offers to “split” coins may be scams and that software claiming to split them can steal them. A soft fork has no new coin to claim, so any site or “wallet update” asking for your recovery phrase to deliver one is fraudulent.

Frequently asked questions

Is a soft fork backward compatible?

Yes. A soft fork only tightens the consensus rules, so every block valid under the new rules is also valid under the old ones. Nodes running older software keep accepting new blocks and stay on the same chain. They cannot check the new rules themselves until they upgrade.

Do soft forks create new coins?

No. A soft fork changes the rules of the existing chain and leaves balances untouched, so there is nothing to claim. A second coin appears only when a chain splits and both sides survive, as with the Bitcoin Cash hard fork of 1 August 2017. Offers of free “soft fork coins” are scams.

What is a user-activated soft fork?

A user-activated soft fork (UASF) is one that full nodes start enforcing at a set date or height, whether or not miners signal support. The best-known example is BIP 148, whose nodes would reject blocks that did not signal for SegWit from 1 August 2017. A UASF can split the chain if most hash power ignores it.

Was SegWit a soft fork?

Yes. Segregated Witness (BIPs 141 and 143) moved signature data into a separate witness that old nodes do not see. Non-upgraded nodes treat SegWit outputs as anyone-can-spend scripts, so they accept the new blocks. SegWit locked in on 9 August 2017 and activated at block 481,824 on 24 August 2017.

What happens to nodes that don’t upgrade?

They stay on the same chain and keep checking the rules they know, but they cannot check the new ones. Such a node would accept a block that breaks only the new rules, which upgraded nodes reject. During the July 2015 BIP 66 fork, old nodes showed confirmations from blocks that were invalid.

Can a soft fork cause a chain split?

Yes, when the miners enforcing the new rules are a minority. Enforcing nodes then reject the majority’s blocks and follow a slower chain of their own. Bitcoin saw short invalid forks in July 2015, and in August 2026 nodes enforcing BIP-110 followed a chain that produced two blocks in about eight hours.

Sources

  1. BIP 8: Version bits with lock-in by height, GitHub bitcoin/bips, 1 February 2017
  2. BIP 9: Version bits with timeout and delay, GitHub bitcoin/bips, 4 October 2015
  3. BIP 16: Pay to Script Hash, GitHub bitcoin/bips, 3 January 2012
  4. BIP 34: Block v2, Height in Coinbase, GitHub bitcoin/bips, 6 July 2012
  5. BIP 65: OP_CHECKLOCKTIMEVERIFY, GitHub bitcoin/bips, 1 October 2014
  6. BIP 66: Strict DER signatures, GitHub bitcoin/bips, 10 January 2015
  7. BIP 68: Relative lock-time using consensus-enforced sequence numbers, GitHub bitcoin/bips, 28 May 2015
  8. BIP 90: Buried Deployments, GitHub bitcoin/bips, 8 November 2016
  9. BIP 91: Reduced threshold Segwit MASF, GitHub bitcoin/bips, 22 May 2017
  10. BIP 110: Reduced Data Temporary Softfork, GitHub bitcoin/bips, 3 December 2025
  11. BIP 112: CHECKSEQUENCEVERIFY, GitHub bitcoin/bips
  12. BIP 113: Median time-past as endpoint for lock-time calculations, GitHub bitcoin/bips
  13. BIP 141: Segregated Witness (Consensus layer), GitHub bitcoin/bips, 21 December 2015
  14. BIP 148: Mandatory activation of segwit deployment, GitHub bitcoin/bips, 12 March 2017
  15. BIP 341: Taproot: SegWit version 1 spending rules, GitHub bitcoin/bips, 19 January 2020
  16. Bitcoin Core version 0.12.1 released, bitcoin.org, 15 April 2016
  17. Bitcoin Core version 0.13.1 released, bitcoin.org, 27 October 2016
  18. Bitcoin Core 0.21.1, bitcoincore.org, 1 May 2021
  19. Bury bip9 deployments (#16060), GitHub bitcoin/bitcoin, 2019
  20. Some Miners Generating Invalid Blocks, bitcoin.org, 4 July 2015
  21. Potential network disruption, bitcoin.org, 12 July 2017
  22. Soft fork activation, Bitcoin Optech
  23. Bitcoin Optech Newsletter #153, Bitcoin Optech, 16 June 2021
  24. Block Chain Guide, Bitcoin Developer Documentation
  25. Softfork, Bitcoin Wiki
  26. Tier Nolan, reply on deploying BIP 65, bitcoin-dev mailing list, 28 September 2015
  27. Mike Hearn, reply on deploying BIP 65, bitcoin-dev mailing list, 29 September 2015
  28. The Long Road To SegWit, Bitcoin Magazine, 23 August 2017
  29. LIP-0003: MimbleWimble via Extension Blocks, GitHub litecoin-project/lips, 20 October 2019
  30. MWEB Progress Update Thread 2, Litecoin Talk, 6 May 2022
  31. Litecoin activates MimbleWimble upgrade on mainnet, ForkLog, 19 May 2022
  32. Hard Fork Completed, Ethereum Foundation Blog, 20 July 2016
  33. Timeline of all Ethereum forks, ethereum.org
  34. UAHF Technical Specification, Bitcoin Cash Node, 24 July 2017
  35. Block 227,931, Blockchain.com
  36. Block 388,381, Blockchain.com
  37. Block 419,328, Blockchain.com
  38. Block 481,824, Blockchain.com
  39. Block 709,632, Blockchain.com

More crypto guides: Guides hub · What is cryptocurrency · What is a seed phrase · 7 crypto scams to avoid

Join our growing community

David Lance Constantino

Author

David Lance Constantino is UseTheBitcoin's Editorial Lead and reviews articles before they are published. He has written about crypto for five years, joined UseTheBitcoin in 2025 and has more than 450 articles to his name, mostly on new blockchain projects, token launches, airdrops and market news.