The BIP process
Reading as Holder. What matters when you hold your own coins.9 of 29 claims
What a BIP isCurious
BIP 3 states that BIPs do not define what Bitcoin is, that individual BIPs do not represent Bitcoin community consensus, and that a BIP is a personal recommendation by its authors to the Bitcoin community.1: open 2 sources
FactCuriousEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
BIPs do not define what Bitcoin is: individual BIPs do not represent Bitcoin community consensus
Fundamentals, What is the Significance of BIPs?, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
A BIP represents a personal recommendation by the BIP authors to the Bitcoin community.
Fundamentals, What is the Significance of BIPs?, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2History, hash and citation
According to BIP 3, the document that sets out the BIP process, no formal or informal decision body governs Bitcoin development or decides whether BIPs are adopted.2: open 1 source
FactCuriousEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
No formal or informal decision body governs Bitcoin development or decides adoption of BIPs.
Fundamentals, What is the Purpose of the BIPs Repository?, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 1/1History, hash and citation
Anyone may submit a BIP: BIP 3, the document that sets out the BIP process, states that BIPs may be submitted by anyone, provided the content is of high quality.3: open 1 source
FactCuriousEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
BIPs may be submitted by anyone, provided the content is of high quality
Fundamentals, What is a BIP?, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 1/1History, hash and citation
A number is not adoptionUser
A BIP number does not mean Bitcoin adopted a proposal. The bitcoin/bips README says publishing a BIP there shows it is in scope and met formal criteria, but not that it is a good idea, has community consensus or is about to be adopted.4: open 2 sources
FactUserEstablishedMedium confidence
T2bitcoin/bips READMEDocumentation, says this directly
but does not indicate that it is a good idea, has community consensus, or that it is about to be adopted
Introduction, before the BIP table, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
BIPs do not define what Bitcoin is: individual BIPs do not represent Bitcoin community consensus
Fundamentals, What is the Significance of BIPs?, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2History, hash and citation
BIP 3 notes that some BIPs may never be adopted, some may be adopted by one or more Bitcoin clients or related software, and some may end up changing the consensus rules the Bitcoin ecosystem jointly enforces.5: open 2 sources
FactUserEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
Some BIPs may never be adopted.
Fundamentals, What is the Significance of BIPs?, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
Some may even end up changing the consensus rules that the Bitcoin ecosystem jointly enforces.
Fundamentals, What is the Significance of BIPs?, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2History, hash and citation
The bitcoin/bips repository README states that acceptance and adoption of a BIP ultimately rest with Bitcoin users, and BIP 3 says that once a BIP is Complete it is up to the Bitcoin community to evaluate, adopt, ignore or reject it.6: open 2 sources
FactUserEstablishedMedium confidence
T2bitcoin/bips READMEDocumentation, says this directly
ultimately acceptance and adoption rests with the Bitcoin users
Introduction, before the BIP table, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
After a BIP is advanced to Complete, it is up to the Bitcoin community to evaluate, adopt, ignore, or reject a BIP.
Workflow, Adoption of Proposals, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2History, hash and citation
Under BIP 3, the bitcoin/bips repository does not track sentiment about proposals or their adoption beyond whether a BIP is in active use. BIP 3 encourages individual Bitcoin projects to publish lists of the BIPs they implement.7: open 2 sources
FactUserEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
The BIPs repository does not track the sentiment on proposals and does not track the adoption of BIPs beyond whether they are in active use or not.
Workflow, Adoption of Proposals, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
Individual Bitcoin projects are encouraged to publish a list of BIPs they implement.
Workflow, Adoption of Proposals, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2History, hash and citation
What your software implementsHolder
Whether a wallet or node follows a given BIP depends on that software, not on the BIP. Bitcoin Core, for example, keeps a list of the BIPs it implements in doc/bips.md, and as of its master branch on 20 November 2026 that list includes BIP 32 but not BIP 39, the mnemonic seed phrase standard.8: open 2 sources
FactHolderEstablishedMedium confidence
T1Bitcoin Core doc/bips.mdSource code, says this directly
BIPs that are implemented by Bitcoin Core:
First line and list of implemented BIPs, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, supports part of it
Individual Bitcoin projects are encouraged to publish a list of BIPs they implement.
Workflow, Adoption of Proposals, read 2026-11-20
bitcoin/bitcoin at a690300ee0 contains this text in doc/bips.md.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:doc/bips.md | grep -nF 'bip-0032'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2, code 1/1History, hash and citation
The process documentsBuilder
As of block 976,761 (20 November 2026), BIP 3, "Updated BIP Process", is the process document in force for the bitcoin/bips repository. Its preamble gives Status Deployed and Type Process, and the text says it replaces BIP 2 as the guideline for the BIP process.9: open 2 sources
FactBuilderEstablishedHigh confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
This BIP replaces BIP 2 as the guideline for the BIP process.
Backward Compatibility, read 2026-11-20
BIP 3's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0003.mediawiki | grep -m1 -E '^ *Statuss?:'BIP 3's Type is "Process" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0003.mediawiki | grep -m1 -E '^ *Types?:'BIP 3's Title is "Updated BIP Process" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0003.mediawiki | grep -m1 -E '^ *Titles?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2, code 3/3History, hash and citation
As of block 976,761 (20 November 2026), BIP 2, "BIP process, revised", has Status Closed, and its preamble names BIP 3 as its replacement. BIP 2 had itself replaced BIP 1, the original BIP process document.10: open 2 sources
FactBuilderEstablishedHigh confidence
T1BIP 2: BIP process, revisedBIP, says this directly
Proposed-Replacement: 3
Preamble, read 2026-11-20
BIP 2's Status is "Closed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0002.mediawiki | grep -m1 -E '^ *Statuss?:'BIP 1's Status is "Closed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0001.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2, code 2/2History, hash and citation
BIP 3 asks authors to present a first sketch of a proposal to the Bitcoin Development Mailing List and to avoid opening a pull request in the bitcoin/bips repository with a BIP draft out of the blue.11: open 3 sources
How it worksBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
As a first sketch of the proposal is taking shape, the authors should present it to the
Workflow, Ideation, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
Authors should avoid opening a pull request with a BIP draft out of the blue.
Workflow, Ideation, read 2026-11-20
T2bitcoin/bips READMEDocumentation, says this directly
People wishing to submit a BIP should first describe their idea to the
Introduction, before the BIP table, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3History, hash and citation
Authors do not choose their own BIP numbers. Under BIP 3, only BIP Editors may assign a number, and a number counts as assigned only after a BIP Editor has announced it publicly in the proposal's pull request to the bitcoin/bips repository.12: open 3 sources
How it worksBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
Only BIP Editors may assign BIP numbers.
Workflow, Progression through BIP Statuses, Draft, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
A number may be considered assigned only after it has been publicly announced in the pull request by a BIP Editor.
Workflow, Progression through BIP Statuses, Draft, read 2026-11-20
T2bitcoin/bips READMEDocumentation, says this directly
After a proposal meets the editorial criteria, a BIP Editor will assign a number to it
Introduction, before the BIP table, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3History, hash and citation
BIP Editors, as BIP 3 describes them, check editorial criteria for a new BIP, such as prior discussion on the Bitcoin Development Mailing List and correct Layer and Type headers, then assign a number and merge. BIP 3 states that editors do not evaluate whether a proposal is likely to be adopted.13: open 4 sources
How it worksBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
Editors do NOT evaluate whether the proposal is likely to be adopted.
BIP Editors, BIP Editor Responsibilities and Workflow, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
The idea has been previously proposed to the Bitcoin Development Mailing List and discussed there
BIP Editors, BIP Editor Responsibilities and Workflow, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
The defined Layer and Type headers must be correctly assigned for the given specification
BIP Editors, BIP Editor Responsibilities and Workflow, read 2026-11-20
T2bitcoin/bips READMEDocumentation, supports part of it
The BIP Editors are expected to be liberal with publishing BIPs
Introduction, before the BIP table, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 4/4History, hash and citation
Statuses, types and layersBuilder
BIP 3 cut the number of BIP status values from nine under BIP 2 to four: Draft, Complete, Deployed and Closed. A BIP in Complete status can only move to Deployed or Closed.14: open 2 sources
FactBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
Status field values are reduced from nine to four:
Backward Compatibility, Changes from BIP 2, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
A Complete BIP can only move to Deployed or Closed.
Workflow, Progression through BIP Statuses, Complete, read 2026-11-20
BIP 3's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0003.mediawiki | grep -m1 -E '^ *Statuss?:'BIP 8's Status is "Complete" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0008.mediawiki | grep -m1 -E '^ *Statuss?:'BIP 2's Status is "Closed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0002.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2, code 3/3History, hash and citation
Under BIP 3, any community member may request that a Complete BIP advance to Deployed by showing evidence that the BIP is in active use, and a Deployed BIP is considered final.15: open 2 sources
How it worksBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
Then, a BIP may be advanced to Deployed upon request by any community member with evidence
Workflow, Progression through BIP Statuses, Deployed, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
Once Deployed, the BIP is considered final.
Workflow, Progression through BIP Statuses, Deployed, read 2026-11-20
BIP 141's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0141.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2, code 1/1History, hash and citation
In BIP 3, the Closed status marks BIPs that are only of historical significance. Closed BIPs are not deleted, and if a Draft BIP appears stalled for a year, anyone may propose that its status be changed to Closed.16: open 3 sources
How it worksBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
The Closed Status provides value to the audience by indicating which documents are only of historical significance.
Workflow, Progression through BIP Statuses, Closed (footnote), read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
appears stalled for a year, anyone may propose the BIP status be updated to Closed.
Workflow, Progression through BIP Statuses, Draft, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
BIPs do not get deleted, they are retained even after being updated to Closed.
Workflow, Progression through BIP Statuses, Closed, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3History, hash and citation
BIP 3 defines three BIP types: a Specification BIP sets technical rules for a new feature or for interoperability between implementations, an Informational BIP describes a design issue or gives guidelines or information, and a Process BIP describes or changes a process surrounding Bitcoin.17: open 3 sources
DefinitionBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
defines a set of technical rules describing a new feature or affecting the interoperability of implementations
BIP Format and Structure, BIP Types, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
describes a process surrounding Bitcoin, or proposes a change to (or an event in) a process.
BIP Format and Structure, BIP Types, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
describes a Bitcoin design issue, or provides general guidelines or other information to the Bitcoin community.
BIP Format and Structure, BIP Types, read 2026-11-20
BIP 3's Type is "Process" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0003.mediawiki | grep -m1 -E '^ *Types?:'BIP 9's Type is "Informational" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0009.mediawiki | grep -m1 -E '^ *Types?:'BIP 141's Type is "Specification" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0141.mediawiki | grep -m1 -E '^ *Types?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3, code 3/3History, hash and citation
BIP 3 supersedes BIP 2's Standards Track type, used for changes affecting most or all Bitcoin implementations, with the similar Specification type. On BIP 3's activation, Standards Track BIPs and eligible Informational BIPs are assigned the Specification type.18: open 3 sources
FactBuilderEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
The Standards Track type is superseded by the similar Specification type.
Backward Compatibility, Changes from BIP 2, read 2026-11-20
T1BIP 2: BIP process, revisedBIP, says this directly
A Standards Track BIP describes any change that affects most or all Bitcoin implementations
BIP types, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
Standards Track BIPs and eligible Informational BIPs are assigned the Specification type.
Backward Compatibility, Updates to Existing BIPs should this BIP be Activated, BIP Types, read 2026-11-20
BIP 341's Type is "Specification" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0341.mediawiki | grep -m1 -E '^ *Types?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3, code 1/1History, hash and citation
A BIP's Layer header, when present, names the part of Bitcoin the BIP applies to, using the classification in BIP 123: the Consensus layer, the Peer Services layer, the API/RPC layer and the Applications layer.19: open 3 sources
DefinitionBuilderEstablishedHigh confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
The layer of Bitcoin the BIP applies to using the BIP classification defined in
BIP Header Preamble, Header Descriptions, Layer, read 2026-11-20
T1BIP 123: BIP ClassificationBIP, says this directly
The peer services layer specifies how nodes find each other and propagate messages.
Classification system, Peer Services Layer, read 2026-11-20
T1BIP 123: BIP ClassificationBIP, supports part of it
The API/RPC layer specifies higher level calls accessible to applications.
Classification system, API/RPC Layer, read 2026-11-20
BIP 123's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0123.mediawiki | grep -m1 -E '^ *Statuss?:'BIP 341's Layer is "Consensus (soft fork)" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0341.mediawiki | grep -m1 -E '^ *Layers?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3, code 2/2History, hash and citation
How the process changedResearcher
Process BIPs follow a different rule for becoming Deployed: under BIP 3, a Process BIP moves from Complete to Deployed when it reaches rough consensus on the Bitcoin Development Mailing List, after its advancement has been open to discussion there for at least one month.20: open 2 sources
How it worksResearcherEstablishedMedium confidence
T1BIP 3: Updated BIP ProcessBIP, says this directly
A Process BIP may change status from Complete to Deployed when it achieves rough consensus
Workflow, Progression through BIP Statuses, Deployed, Process BIPs, read 2026-11-20
T1BIP 3: Updated BIP ProcessBIP, says this directly
A proposal is said to have rough consensus if its advancement has been open to discussion on the mailing list
Workflow, Progression through BIP Statuses, Deployed, Process BIPs, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2History, hash and citation
Optech Newsletter #382 (28 November 2025) reported a motion on the Bitcoin-Dev mailing list to activate BIP 3 in place of BIP 2. bitcoin/bips pull request #1820, "Process: Activate BIP3", which applies the changes BIP 3 prescribes on activation, was merged on 14 January 2026.21: open 2 sources
EventResearcherEstablishedMedium confidence
T1bitcoin/bips PR #1820: Process: Activate BIP3Pull request, says this directly
This is a first draft of applying the changes prescribed by BIP 3 in the section
PR description; merged 14 January 2026, read 2026-11-20
T2Bitcoin Optech NewsletterBitcoin Optech, says this directly
After that date, BIP3 will replace BIP2 as the BIP process.
News, Motion to activate BIP3, published 2025-11-28, read 2026-11-20
Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2History, hash and citation
Activation happens outside the processResearcher
BIP 9 specifies version bits: miners signal readiness for a soft fork by setting a bit in the block version, support is tallied each 2,016-block retarget period, and on mainnet a deployment locks in when at least 1,916 blocks (95%) of a period signal before its timeout.22: open 3 sources
How it worksResearcherEstablishedHigh confidence
T1BIP 9: Version bits with timeout and delayBIP, says this directly
The threshold is ≥1916 blocks (95% of 2016), or ≥1512 for testnet (75% of 2016).
Specification, Parameters and State transitions, read 2026-11-20
T1BIP 9: Version bits with timeout and delayBIP, says this directly
The timeout specifies a time at which the deployment is considered failed.
Specification, Parameters, read 2026-11-20
T1Bitcoin Core src/consensus/params.h, struct BIP9DeploymentSource code, says this directly
uint32_t threshold{1916};
struct BIP9Deployment, threshold, read 2026-11-20
BIP 9's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0009.mediawiki | grep -m1 -E '^ *Statuss?:'BIP 9's Type is "Informational" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0009.mediawiki | grep -m1 -E '^ *Types?:'bitcoin/bitcoin at a690300ee0 contains this text in src/consensus/params.h.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:src/consensus/params.h | grep -nF 'uint32_t threshold{1916};'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3, code 3/3History, hash and citation
BIP 8 is an alternative to BIP 9 version bits that uses block heights instead of timestamps for start and timeout, and adds a lockinontimeout flag that, when set, requires blocks to signal in the final period so the soft fork locks in by the timeout height.23: open 3 sources
How it worksResearcherEstablishedMedium confidence
T1BIP 8: Version bits with lock-in by heightBIP, says this directly
Block heights are used for start and timeout rather than POSIX timestamps.
Abstract, read 2026-11-20
T1BIP 8: Version bits with lock-in by heightBIP, says this directly
blocks are required to signal in the final period, ensuring the soft fork has locked in by timeoutheight.
Specification, Parameters, read 2026-11-20
T2Bitcoin Optech topic, Soft fork activationBitcoin Optech, background
BIP8’s flexibility allowed it to be used to compare a variety of activation proposals
Topic summary, BIP8, read 2026-11-20
BIP 8's Status is "Complete" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0008.mediawiki | grep -m1 -E '^ *Statuss?:'BIP 8's Type is "Informational" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0008.mediawiki | grep -m1 -E '^ *Types?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 3/3, code 2/2History, hash and citation
The soft fork combining BIP 68, BIP 112 and BIP 113 (often called CSV) was the first deployed with BIP 9 version bits: Bitcoin Core 0.12.1 signaled it on bit 0 from 1 May 2016, and its rules have been active on mainnet since block 419,328.24: open 4 sources
EventResearcherEstablishedHigh confidence
T1Bitcoin Core 0.12.1 release notesRelease notes, says this directly
setting bit 0 to indicate support for this combined
Notable changes, first version bits BIP9 softfork deployment, read 2026-11-20
T2BIP 9 deployment assignments (bips repository)Documentation, says this directly
active since #419328
Deployments table, csv row, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, CMainParamsSource code, says this directly
consensus.CSVHeight = 419328;
CMainParams, consensus.CSVHeight, read 2026-11-20
T2Bitcoin Optech topic, Soft fork activationBitcoin Optech, says this directly
This activation method was first used with the soft fork that added BIP68 consensus-enforced sequence numbers,
Topic summary, BIP9, read 2026-11-20
bitcoin/bitcoin at a690300ee0 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:src/kernel/chainparams.cpp | grep -nF 'consensus.CSVHeight = 419328;'Block 419,328 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 419328Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 4/4, code 1/1, chain 1/1 (esplora pair agreed)History, hash and citation
Segregated witness (BIP 141) was deployed with BIP 9 version bits on bit 1, released in Bitcoin Core 0.13.1 with a signaling start of 15 November 2016, and its rules have been active on mainnet since block 481,824.25: open 4 sources
EventResearcherEstablishedHigh confidence
T1BIP 141: Segregated Witness (Consensus layer)BIP, says this directly
For Bitcoin mainnet, the BIP9 starttime will be midnight 15 November 2016 UTC (Epoch timestamp 1479168000)
Deployment, read 2026-11-20
T1Bitcoin Core 0.13.1 release notesRelease notes, says this directly
Segwit's version bit is bit 1, and nodes will begin
Notable changes, Segregated witness soft fork, read 2026-11-20
T2BIP 9 deployment assignments (bips repository)Documentation, says this directly
active since #481824
Deployments table, segwit row, read 2026-11-20
T2Bitcoin Optech topic, Soft fork activationBitcoin Optech, says this directly
The segwit soft fork was released with BIP9 activation parameters.
Topic summary, BIP9, read 2026-11-20
bitcoin/bitcoin at a690300ee0 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:src/kernel/chainparams.cpp | grep -nF 'consensus.SegwitHeight = 481824;'Block 481,824 has hash 0000000000000000...
Run it yourself
bitcoin-cli getblockhash 481824BIP 141's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0141.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 4/4, code 2/2, chain 1/1 (esplora pair agreed)History, hash and citation
The Taproot soft fork activated on mainnet at block 709,632 through Speedy Trial, a variation of BIP 9 version bits released in Bitcoin Core 0.21.1, with a lock-in threshold of 1,815 of 2,016 blocks (90%) and a minimum activation height of block 709,632.26: open 4 sources
EventResearcherEstablishedHigh confidence
T1Bitcoin Core 0.21.1 release notesRelease notes, says this directly
Activation for taproot is being managed using a variation of BIP9 versionbits called Speedy Trial (described in BIP341).
Taproot soft fork, read 2026-11-20
T1BIP 341: Taproot: SegWit version 1 spending rulesBIP, says this directly
the threshold is 1815 blocks (90%) instead of 1916 blocks (95%)
Deployment, read 2026-11-20
T1BIP 341: Taproot: SegWit version 1 spending rulesBIP, says this directly
the min_activation_height is block 709632
Deployment, read 2026-11-20
T1BIP 341: Taproot: SegWit version 1 spending rulesBIP, says this directly
The deployment did activate at height 709632 on Bitcoin mainnet.
Deployment, read 2026-11-20
bitcoin/bips at a7f91321f2 contains this text in bip-0341.mediawiki.
Run it yourself
git clone https://github.com/bitcoin/bips && git -C bips show a7f91321f25b5be8d93e901775621c21519e80b7:bip-0341.mediawiki | grep -nF 'the min_activation_height is block 709632'BIP 341's Status is "Deployed" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0341.mediawiki | grep -m1 -E '^ *Statuss?:'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 4/4, code 2/2History, hash and citation
After a soft fork has activated, Bitcoin Core can replace its version bits deployment with a hardcoded activation height, called a buried deployment (BIP 90). As of Bitcoin Core master on 20 November 2026, CSV is buried at block 419,328 and segwit at block 481,824.27: open 2 sources
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core src/consensus/params.h, enum BuriedDeploymentSource code, says this directly
A buried deployment is one where the height of the activation has been hardcoded into
Comment above enum BuriedDeployment, read 2026-11-20
T1Bitcoin Core src/kernel/chainparams.cpp, CMainParamsSource code, says this directly
consensus.SegwitHeight = 481824;
CMainParams, consensus.SegwitHeight, read 2026-11-20
bitcoin/bitcoin at a690300ee0 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:src/kernel/chainparams.cpp | grep -nF 'consensus.CSVHeight = 419328;'bitcoin/bitcoin at a690300ee0 contains this text in src/kernel/chainparams.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:src/kernel/chainparams.cpp | grep -nF 'consensus.SegwitHeight = 481824;'bitcoin/bitcoin at a690300ee0 contains this text in src/consensus/params.h.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:src/consensus/params.h | grep -nF 'the client implementation long after the consensus change has activated. See BIP 90.'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2, code 3/3History, hash and citation
As of Bitcoin Core master on 20 November 2026, GetBlockScriptFlags in src/validation.cpp turns on the P2SH, segwit and Taproot script rules for every block except two listed exceptions, because only one historical mainnet block violated the Taproot rules and one violated P2SH.28: open 2 sources
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core src/validation.cpp, GetBlockScriptFlagsSource code, says this directly
ConsensusScriptVerifyFlags flags{SCRIPT_VERIFY_P2SH | SCRIPT_VERIFY_WITNESS | SCRIPT_VERIFY_TAPROOT};
GetBlockScriptFlags, read 2026-11-20
T1Bitcoin Core src/validation.cpp, GetBlockScriptFlagsSource code, says this directly
Similarly, only one historical block violated the TAPROOT rules on
GetBlockScriptFlags, comment, read 2026-11-20
bitcoin/bitcoin at a690300ee0 contains this text in src/validation.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show a690300ee0d523de0b91e59b00a16fe47297cb85:src/validation.cpp | grep -nF 'ConsensusScriptVerifyFlags flags{SCRIPT_VERIFY_P2SH | SCRIPT_VERIFY_WITNESS | SCRIPT_VERIFY_TAPROOT};'Checked at block 976,764, 20 Nov 2026, 18:01 UTC: quotes 2/2, code 1/1History, hash and citation