Skip to content

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

Bitcoin Soft Forks — Consensus Activation Registry (P2SH to Taproot)

Every consensus-changing Bitcoin soft fork, from P2SH to Taproot — BIP numbers, activation mechanism, block height and date, and what each one changed. Free CSV/JSON + REST under CC BY 4.0.

Quick answer

A Bitcoin soft fork is a backward-compatible tightening of the consensus rules: nodes that don't upgrade still accept the new blocks, so the network never splits if a majority of hashpower enforces it. Nearly every capability Bitcoin has gained — P2SH multisig, time-locks, SegWit, Taproot — arrived as a soft fork. This registry lists 8 consensus-changing soft forks with their BIP numbers, activation mechanism, activation block height and date, and what each one changed.

From P2SH (2012) to Taproot (2021), each soft fork tightened the rules without splitting the chain. The activation method evolved from timestamp flag days to IsSuperMajority to BIP9 version bits to Speedy Trial — increasingly miner-signalled, with users (UASF) as the ultimate backstop.

Download CSV Download JSON REST API →

Soft forkBIP(s)Activation mechanismBlockActivatedStatusWhat it changed
BIP30 — Duplicate-TXID rule30Flag day (block timestamp)91,8422012-03-15ActiveDisallowed a block containing a transaction whose ID duplicates an existing unspent transaction, closing a coinbase-overwrite flaw.
P2SH — Pay-to-Script-Hash16Flag day (block timestamp)173,8052012-04-01ActiveIntroduced Pay-to-Script-Hash (the '3' addresses): senders pay to a hash of a redeem script that the recipient supplies when spending — the basis for practical multisig.
BIP34 — Height in coinbase34IsSuperMajority (75% then 95%)227,9312013-03-24ActiveRequired the block height in the coinbase and bumped block version to 2, preventing duplicate coinbase txids and introducing version-based soft-fork signalling.
BIP66 — Strict DER signatures66IsSuperMajority (95%)363,7252015-07-04ActiveEnforced strict DER encoding of ECDSA signatures, removing an OpenSSL-dependent malleability source. Its activation caused a brief accidental chain split among non-upgraded miners.
CLTV — CheckLockTimeVerify65IsSuperMajority (95%)388,3812015-12-14ActiveAdded OP_CHECKLOCKTIMEVERIFY, enabling outputs spendable only after an absolute block height or time — a building block for payment channels and escrow.
CSV — Relative lock-time68, 112, 113BIP9 version bits (95%)419,3282016-07-04ActiveRelative lock-time (BIP68), OP_CHECKSEQUENCEVERIFY (BIP112) and median-time-past (BIP113) — together enabling bidirectional payment channels and the Lightning Network.
SegWit — Segregated Witness141, 143, 147BIP9 version bits + BIP91 lock-in481,8242017-08-24ActiveMoved signature (witness) data outside the txid, fixing transaction malleability, raising effective capacity via block weight, and laying the groundwork for Lightning and Taproot.
Taproot — Schnorr + Tapscript340, 341, 342Speedy Trial (BIP9, 90%)709,6322021-11-14ActiveSchnorr signatures (BIP340), Taproot (BIP341) and Tapscript (BIP342) — key aggregation and Merkelized script paths giving multisig and complex scripts better privacy and efficiency.

Source: the Bitcoin BIP repository and the canonical activation heights in Bitcoin Core. Related glossary: soft fork, P2SH, SegWit, Taproot, version bits, CLTV, CSV. See the open data hub.