2026-11-20-seed-bip-process
Published
29 claims
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- A Bitcoin Improvement Proposal (BIP) is an improvement proposal for Bitcoin. BIP 3, the process document, says most BIPs give a concise, self-contained technical description of one new concept, feature or standard.
Held for the owner
Their text stays private until the owner approves it.
- 1 claim on bip-process
contested subject
Rejected
4 candidates
- BIP 2's nine status values listed by name
research: The fetched text appeared to come from a diagram whose exact characters I could not confirm; the count (nine to four) is cited from BIP 3 instead
- A mailing-list announcement that BIP 3 was deployed on 14 January 2026
research: gnusha.org returned 403 and the message id from search results resolved to a different message; the PR merge is cited instead
- Whether BIP 8 with lockinontimeout or BIP 148 played a role in segwit lock-in in 2017
research: Out of scope for a seed and close to contested history; needs primary sources and careful attribution
- Block hash of Taproot activation block 709,632
research: No fetched source gave the hash, so no chain.block-hash check was added
Could not settle
- The exact merge commit of bitcoin/bips PR
- BIP 141 and BIP 341 Type values (Specification) and BIP 341 Layer were taken from the README table, not the preamble text; the bip.field checks will confirm or fail them.
- The quote from PR
Injection attempts
No text in any source this run read tried to give the brain orders.
Read
20 sources
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/README.mediawiki
Which process document is in force; statement that publication is not endorsement; status column for BIPs 1, 2, 3, 8, 9, 141, 341
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0003.md
Preamble, significance of BIPs, statuses, types, numbering, editors, Process BIP rough consensus, changes from BIP 2, changelog
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0002.mediawiki
Status Closed, Replaces 1, Proposed-Replacement 3, Standards Track definition
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0123.mediawiki
Layer classification
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0009.mediawiki
Version bits threshold, states, timeout; status Deployed
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0009/assignments.mediawiki
CSV and segwit deployment rows with activation heights
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0008.mediawiki
Height-based version bits and lockinontimeout; status Complete
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0141.mediawiki
Segwit deployment parameters
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0341.mediawiki
Taproot deployment parameters (threshold 1815, min_activation_height 709632)
- https://raw.githubusercontent.com/bitcoin/bitcoin/a690300ee0d523de0b91e59b00a16fe47297cb85/src/kernel/chainparams.cpp
Buried CSV and segwit heights with block hashes in comments
- https://raw.githubusercontent.com/bitcoin/bitcoin/a690300ee0d523de0b91e59b00a16fe47297cb85/src/consensus/params.h
BuriedDeployment comment (BIP 90), BIP9Deployment default threshold
- https://raw.githubusercontent.com/bitcoin/bitcoin/a690300ee0d523de0b91e59b00a16fe47297cb85/src/validation.cpp
GetBlockScriptFlags always enabling P2SH, WITNESS, TAPROOT except two exception blocks
- https://raw.githubusercontent.com/bitcoin/bitcoin/a690300ee0d523de0b91e59b00a16fe47297cb85/doc/release-notes/release-notes-0.12.1.md
CSV deployment on bit 0
- https://raw.githubusercontent.com/bitcoin/bitcoin/a690300ee0d523de0b91e59b00a16fe47297cb85/doc/release-notes/release-notes-0.13.1.md
Segwit deployment on bit 1
- https://raw.githubusercontent.com/bitcoin/bitcoin/a690300ee0d523de0b91e59b00a16fe47297cb85/doc/release-notes/release-notes-0.21.1.md
Taproot Speedy Trial
- https://raw.githubusercontent.com/bitcoin/bitcoin/a690300ee0d523de0b91e59b00a16fe47297cb85/doc/bips.md
Bitcoin Core's list of implemented BIPs
- https://bitcoinops.org/en/topics/soft-fork-activation/
Expert coverage of activation, BIP 9 first use, BIP 8
- https://bitcoinops.org/en/newsletters/2025/11/28/
Motion to activate BIP 3
- https://github.com/bitcoin/bips/pull/1820
BIP 3 activation PR, merged 14 January 2026
- https://mailing-list.bitcoindevs.xyz/bitcoindev/458a5831-a1a2-4c21-ab61-dccd00ed5219@murch.one/
Checked for the BIP 3 deployment announcement; it was an earlier March 2025 message, not cited