PipeFlare

What Is a Bitcoin Soft Fork?

A Bitcoin soft fork adds stricter consensus rules while old nodes can accept new blocks. Learn how activation works and why a chain split remains possible.

By Jonathan West · Updated November 17, 2026

A Bitcoin soft fork adds stricter consensus rules that old nodes can still accept, with activation requiring nodes to coordinate when they begin enforcing the rules

Activation determines which rules full nodes enforce, and differences between nodes can cause a chain split

Category

Protocol upgrade

Difficulty

Intermediate

Where you'll see it

Bitcoin Improvement Proposal headers and the Bitcoin Optech activation history

First introduced

The earliest known Bitcoin soft fork shipped in Bitcoin 0.1.6, released November 2009

About bitcoin soft forks

A Bitcoin soft fork tightens the rules for valid blocks and transactions, while older nodes can still accept blocks that follow the stricter rules. Activation coordinates when upgraded nodes start enforcing the change, using a mechanism such as miner signaling or a specified block height. Nodes that enforce different rules can disagree about which chain is valid.

What a Bitcoin Soft Fork Is

A Bitcoin soft fork makes some previously valid blocks or transactions invalid under new consensus rules. The Bitcoin developer glossary defines it this way: old nodes still recognize blocks that satisfy the stricter rules as valid. Consensus rules are the checks nodes use to decide whether a block or transaction belongs on the chain.

Upgraded full nodes apply the new checks. Non-upgraded nodes continue applying their older checks, so a block that satisfies both sets can pass through both groups. This compatibility concerns acceptance of blocks. It does not mean older software enforces the new restriction.

Bitcoin Improvement Proposal (BIP) 341 gives a concrete example. Its Taproot rules apply to a new Segregated Witness (SegWit) version 1 output type, while non-upgraded nodes treat those witness programs as anyone-can-spend scripts. An upgraded node checks the Taproot spending rules that the older node does not know how to check.

Soft Fork vs Hard Fork

A soft fork makes some previously valid blocks or transactions invalid under new rules, while a hard fork can create blocks that non-upgraded nodes cannot validate. The developer glossary describes a hard fork as a permanent divergence that commonly occurs when old nodes cannot validate blocks made under newer rules. Bitcoin Optech's activation history describes the different risk for a soft fork: nodes applying different restrictions may accept and reject the same block, causing a chain split.

Here, fork means a Bitcoin protocol-rule change. The glossary also uses fork for a separate software codebase or a temporary Git codebase split. Those development terms do not describe whether Bitcoin nodes accept the same blocks.

Soft fork vs hard fork
AspectSoft forkHard fork
Change directionMakes some previously valid blocks or transactions invalidCan produce blocks that non-upgraded nodes cannot validate
What non-upgraded nodes doRecognize blocks following the stricter rules as validCannot validate blocks that depend on the newer rules
Main riskNodes enforcing different restrictions can split over a blockThe blockchain can diverge permanently
Example in the sourcesTaproot, listed as a deployed soft fork in BIP-341A hard-forking change in the Bitcoin 0.3.6 release, mentioned in Bitcoin Optech's activation history

How it actually works

A soft fork changes the validity test for upgraded nodes. Suppose an older rule permits a set of blocks and a new rule removes some blocks from that set. A block satisfying the new rule also satisfies the older rule, which is why a non-upgraded node can accept it. A block satisfying only the older rule creates the problem: the non-upgraded node may accept it while the upgraded node rejects it.

Taproot shows the limits of backward compatibility. BIP-341 says non-upgraded nodes regard SegWit version 1 witness programs as anyone-can-spend scripts, although upgraded nodes enforce Taproot's spending rules. Both groups can follow blocks that obey the new rules, but the older group cannot check those particular spending conditions. Activation therefore concerns more than publishing new software: nodes must begin enforcing a compatible set of rules on the chain they follow.

How a Soft Fork Gets Activated

A Bitcoin soft fork activates when full nodes begin enforcing its additional consensus rules. Bitcoin Optech records an early method in Bitcoin 0.1.6: its nLockTime change was hardcoded to activate at block 31,000. Later approaches set out how nodes determine whether a proposed rule reaches its activation condition.

BIP-9 describes version-bit signaling. A miner sets a designated bit in a block header to signal readiness, and nodes count signals over periods of 2,016 blocks. Under the method described by Bitcoin Optech, reaching a 95% threshold starts a further 2,016-block lock-in period before activation. If signaling fails to reach the threshold before the deployment's timeout, that activation attempt ends.

BIP-8 describes an alternative that uses block heights for its start and timeout. Its LockinOnTimeout setting determines whether blocks must signal in the final period. When that setting is false, the proposed rules can still lock in if signaling meets the threshold. When it is true, nodes require signaling in the final period so the change locks in by the specified timeout height.

The developer glossary calls activation through miner signaling a miner-activated soft fork (MASF). It calls activation by a flag day or node enforcement instead of miner signaling a user-activated soft fork (UASF). These labels identify an activation route. Neither label removes the possibility that nodes with different rules will disagree about a block.

Bitcoin Optech describes a concrete disagreement during the 2012 Pay-to-Script-Hash (P2SH) activation attempt. Fewer than half of the last 1,000 blocks had signaled readiness at the first poll, yet some miners enforced the planned rule while the majority did not. Optech reports a fairly long alternative chain fork before a later poll found sufficient support and a revised activation proceeded. A soft fork can therefore be backward compatible in its rule design and still encounter a chain split during coordination.

This section follows the Bitcoin Optech activation topic and the BIP-9 and BIP-8 texts as read on 17 November 2026.

Soft Forks Bitcoin Has Shipped

Taproot is a deployed Bitcoin soft fork. BIP-341 labels itself a consensus soft fork and gives its status as Deployed. Its mainnet deployment used version-bit signaling with a 90% threshold and a minimum activation height. The BIP states that Taproot activated at block 709632.

SegWit also activated as a soft fork, but its activation history involves more than a single signaling threshold. Bitcoin Optech says SegWit was released with BIP-9 activation parameters and that initial miner support remained below the 95% threshold. Some users developed BIP-148, which would reject blocks that failed to signal from a specified date. BIP-91 changed the signaling threshold to 80% and shortened its monitoring and lock-in periods. Optech reports that BIP-91 activated and SegWit subsequently locked in and activated.

Optech says the extent to which each event contributed to SegWit's activation remains debated. That history is a reason to separate a proposed rule's content from the process used to coordinate enforcement. For the address-format effects of these changes, see SegWit and Taproot explained.

What Comes After Taproot

Several proposed Bitcoin soft forks have BIP headers, but none of the proposals listed here has a header status of Deployed as read on 17 November 2026. A BIP status describes the document. It does not, by itself, establish that nodes enforce its proposed rules. The official BIP repository holds the numbered proposal texts and their headers.

BIP-119, which specifies CHECKTEMPLATEVERIFY (OP_CTV), has status Draft. BIP-347 covers OP_CAT in Tapscript and has status Complete. That Complete label applies to the specification. Its text says OP_CAT would be activated through a soft fork, so it must not be read as an activation notice. BIP-443, for OP_CHECKCONTRACTVERIFY (OP_CCV), has status Draft.

BIP-345, for OP_VAULT, has status Closed and names BIP-443 as its proposed replacement. These proposals are discussed in what is a Bitcoin covenant. BIP-360 proposes Pay-to-Merkle-Root (P2MR) as a new output type and has status Draft. what is BIP-360 covers that proposal. BIP-360's header lists it as Draft, not Deployed.

What a Soft Fork Means for Your Own Coins

A proposed Bitcoin soft fork does not change coins held in an existing address type. A draft describes a possible rule. Activation is the point when full nodes begin enforcing an additional rule. Holding bitcoin at an existing address therefore requires no action merely because a proposal has been published.

If an activated change adds an output type, its new spending rules apply to coins sent to that output type. Taproot illustrates the distinction: BIP-341 defines rules for SegWit version 1 outputs, while older nodes interpret those outputs under their existing rules. A person does not acquire a new output type simply because its BIP exists.

Node operation presents a separate choice. A node operator chooses software that determines which rules that node enforces. Because a non-upgraded node does not enforce a soft fork's new restriction, its acceptance of a block is not independent verification of that restriction. Bitcoin Optech identifies the remaining network-wide risk: when nodes apply different rules to the same block, their views of the valid chain may diverge.

Takeaway on Bitcoin Soft Forks

A Bitcoin soft fork lets stricter rules operate while non-upgraded nodes can still accept compliant blocks. Activation remains a coordination problem because those older nodes cannot reject every block that violates the new restriction. The distinction matters when reading a proposal: a rule can be specified in a BIP without becoming a rule that Bitcoin nodes enforce.

For the proposals listed above, the stated BIP headers do not report deployment. A specific proposal's activation software or signaling period would change the account of its status and require checking that proposal's deployment details. Read the status and activation details in a proposal's official BIP header when assessing a Bitcoin soft fork.

Start here

  1. 1Read the soft fork and hard fork definitions in the [Bitcoin developer glossary](https://developer.bitcoin.org/glossary.html), then note which kind of rule change old nodes can accept.
  2. 2Open [BIP-9](https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki) and find its signaling bit, timeout, and deployment states.
  3. 3Compare the height-based settings and LockinOnTimeout parameter in [BIP-8](https://github.com/bitcoin/bips/blob/master/bip-0008.mediawiki) with BIP-9's signaling method.
  4. 4Read [Bitcoin Optech's activation history](https://bitcoinops.org/en/topics/soft-fork-activation/) for the 2012 P2SH chain split and the SegWit activation account.
  5. 5Choose a proposal in the [BIP repository](https://github.com/bitcoin/bips) and read its status header before treating its proposed rules as active.

Strengths

  • Blocks that satisfy the stricter rules remain recognizable as valid to non-upgraded nodes.
  • BIP-9 defines a signaling and timeout process so nodes can determine whether that deployment reaches lock-in.
  • A BIP header and activation specification let readers distinguish a documented proposal from a deployed rule.

Common misunderstandings

  • Backward compatibility does not mean an older node checks the new restriction.
  • Miner signaling is an activation signal. Full nodes enforce consensus rules.
  • A BIP header marked Complete does not necessarily mean its proposed consensus rule has activated.
  • Different enforcement rules can cause a chain split even when the proposed change is a soft fork.

Common questions

What is a hard fork in crypto?

A hard fork is a blockchain divergence that commonly occurs when non-upgraded nodes cannot validate blocks created under newer consensus rules. That differs from a soft fork, whose compliant new blocks remain valid under the old rules. The Bitcoin developer glossary uses these definitions for protocol forks, separately from software or Git codebase forks.

Has Bitcoin ever hard forked?

Bitcoin Optech's activation history mentions a Bitcoin 0.3.6 code revision that made a hard-forking change. It also describes a later two-step proposal requiring a hard fork that was withdrawn after opposition. Those mentions are not presented as a complete history of every Bitcoin fork.

Is a soft fork backward compatible?

Yes. A soft fork restricts validity so old nodes can still accept blocks following the new rules. An old node does not enforce the added restriction, however, which is why differently configured nodes can disagree about a block that breaks it.

What is a user-activated soft fork?

A user-activated soft fork (UASF) is a soft fork activated through a flag day or node enforcement rather than miner signaling, according to the Bitcoin developer glossary. The label describes how nodes begin enforcing the rule. It does not mean every node has upgraded.

Is this financial advice?

No. This page provides general information about Bitcoin protocol mechanics, including rule changes and activation. It does not recommend a financial decision.

Sources

Related guides

Ready to put this into practice?

Exchange sign-up bonuses pay both you and a referrer after a qualifying trade.

See bonuses →