Skip to content
Satoshi Gazette
Data DeskDated snapshot

Protocol

Where each Bitcoin Improvement Proposal stands in the BIP repository’s own words, and the security advisories Bitcoin Core has posted.

Bitcoin Improvement Proposals, by the status the BIPs repository gives them

213BIPs

linked from the BIPs repository’s index at commit 927b6de, its newest when the desk read it on

Bars show how many BIPs carry each status, most first, with BIP 3’s meaning under each
  1. Deployed78 BIPs

    Advanced on evidence of active use, or for a Process BIP rough consensus; considered final.

  2. Closed57 BIPs

    Of historical interest only: not being worked on, promoted or in active use.

  3. Draft56 BIPs

    Published with a number; its authors may still be changing it.

  4. Complete22 BIPs

    Its authors have finished their planned work and recommend adoption.

A status is where a document stands in the repository’s own process, BIP 3. The desk maps and renames nothing.

Not an endorsement, and not an activation: a status does not say a consensus change is in force. Under BIP 3 a BIP can be Deployed on one established project shipping support for it.

Issuer · bitcoin/bips at commit 927b6de ·repository last changed  ·read  ·BIPs index ↗

Dates, sources & limits

Dataset sg-bip-status, method 1.0.0. Every status is the BIP repository's own: the Status header in the BIP's preamble, in the four words BIP 3 sets (Draft, Complete, Deployed, Closed). Type and layer are read the same way. The desk maps and renames nothing, and each time it reads the files it checks the words against BIP 3's own text. A status is the repository's label for a document. It is not an endorsement, and it does not say a consensus change has activated: under BIP 3 a BIP can be Deployed on the evidence of one established project shipping support for it.

The repository is read without an account or a token. The desk reads its commits feed for the newest commit, then the README index and every BIP file the index links, each at that commit, so one read describes one state of the repository. The feed's time for that commit is GitHub's clock. Files are read from raw.githubusercontent.com at most one a second and kept on the desk's machine by commit, so a second run on the same commit asks for the feed alone.

A change is recorded when a BIP's status differs from the one in the desk's previous saved file, or when the index lists a BIP the desk has not recorded before. It is dated by the day the desk saw it, not the day it happened: the repository may have made the change on any day since the desk's previous read. Recorded changes are added to and never rewritten. The first read records none.

A BIP is held when its preamble cannot be read as BIP 3 lays it out, names a status, type or layer outside BIP 3's words, or disagrees with the index on number, layer, type or status. A held row keeps what the desk last recorded, with the reason and the day the hold began, is left out of the counts by status and records no change. Nothing is guessed. A read writes nothing when the feed, the index or any file fails, when the feed's newest commit is older than the one already read, when the index drops a BIP the desk has recorded or lists fewer than 150, when more than one row in twenty would be held, or when BIP 3's own words have changed.

Authors is the number of lines in the preamble's Authors header. One line can name more than one person. Names and addresses are not kept. A number the index lists without a document is kept apart, in the index's own words, and is not counted as a BIP with a status.

Listed without a document at this commit: 40, Stratum wire protocol (“BIP number allocated”); 41, Stratum mining protocol (“BIP number allocated”); 63, Stealth Addresses (“BIP number allocated”).

Check a row yourself, here BIP 3’s own preamble: curl -s https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0003.md | head -20

The BIPs repository is public on GitHub and is read without an account: its commits feed and its raw files only. Each BIP names its own licence in its preamble where it has one. The desk keeps facts from the index and the preambles (number, title, layer, type, status, the date a number was assigned, the BIPs a preamble names as replaced or as a proposed replacement, and a count of author lines) and none of a BIP's text.

Status changes the desk has recorded

None yet. The desk first read the repository on , and a first read has nothing earlier to differ from. A change is listed here from the day a later read finds a BIP’s status different.

Seen is the day the desk read the change, not the day it happened: the repository may have made it on any day since the desk’s previous read.

Every BIP, by status

By number within each status. A number opens the BIP’s own file at commit 927b6de, the one each row was read from.

Draft56 BIPs

Published with a number; its authors may still be changing it.

BIPs the repository lists as Draft: number, title, type and layer
BIPTitleType and layer
BIP 46 ↗Address Scheme for Timelocked Fidelity BondsSpecificationApplications
BIP 53 ↗Disallow 64-byte transactionsSpecificationConsensus (soft fork)
BIP 77 ↗Async PayjoinSpecificationApplications
BIP 93 ↗codex32: Checksummed SSSS-aware BIP32 seedsInformationalApplications
BIP 95 ↗Testnet 5SpecificationApplications
BIP 98 ↗Fast Merkle TreesSpecificationConsensus (soft fork)
BIP 116 ↗MERKLEBRANCHVERIFYSpecificationConsensus (soft fork)
BIP 117 ↗Tail Call Execution SemanticsSpecificationConsensus (soft fork)
BIP 118 ↗SIGHASH_ANYPREVOUT for Taproot ScriptsSpecificationConsensus (soft fork)
BIP 119 ↗CHECKTEMPLATEVERIFYSpecificationConsensus (soft fork)
BIP 122 ↗URI scheme for Blockchain references / explorationSpecificationApplications
BIP 126 ↗Best Practices for Heterogeneous Input Script TransactionsInformationalNo layer named
BIP 128 ↗Timelock-Recovery Storage FormatSpecificationApplications
BIP 136 ↗Bech32 Encoded Tx Position ReferencesInformationalApplications
BIP 138 ↗Compact Encryption Scheme for Non-seed Wallet DataSpecificationApplications
BIP 172 ↗Define Bitcoin Subunits as SatoshisInformationalApplications
BIP 177 ↗Redefine Bitcoin's Base UnitInformationalNo layer named
BIP 178 ↗Version Extended WIFSpecificationApplications
BIP 197 ↗Hashed Time-Locked Collateral ContractSpecificationApplications
BIP 300 ↗Hashrate Escrows (Consensus layer)SpecificationConsensus (soft fork)
BIP 301 ↗Blind Merged Mining (Consensus layer)SpecificationConsensus (soft fork)
BIP 310 ↗Stratum protocol extensionsInformationalApplications
BIP 320 ↗nVersion bits for general purpose useSpecificationNo layer named
BIP 323 ↗24 nVersion bits for general purpose useSpecificationNo layer named
BIP 326 ↗Anti-fee-sniping in taproot transactionsInformationalApplications
BIP 329 ↗Wallet Labels Export FormatInformationalApplications
BIP 330 ↗Transaction announcements reconciliationSpecificationPeer Services
BIP 331 ↗Ancestor Package RelaySpecificationPeer Services
BIP 332 ↗Stale Tip RelaySpecificationPeer Services
BIP 337 ↗Compressed TransactionsSpecificationAPI/RPC
BIP 346 ↗OP_TXHASHSpecificationConsensus (soft fork)
BIP 348 ↗CHECKSIGFROMSTACKSpecificationConsensus (soft fork)
BIP 349 ↗OP_INTERNALKEYSpecificationConsensus (soft fork)
BIP 360 ↗Pay-to-Merkle-Root (P2MR)SpecificationConsensus (soft fork)
BIP 361 ↗Post Quantum Migration and Legacy Signature SunsetInformationalConsensus (soft fork)
BIP 372 ↗Pay-to-contract tweak fields for PSBTSpecificationApplications
BIP 374 ↗Discrete Log Equality ProofsSpecificationApplications
BIP 375 ↗Sending Silent Payments with PSBTsSpecificationApplications
BIP 376 ↗Spending Silent Payment outputs with PSBTsSpecificationApplications
BIP 379 ↗MiniscriptSpecificationApplications
BIP 389 ↗Multipath Descriptor Key ExpressionsSpecificationApplications
BIP 390 ↗musig() Descriptor Key ExpressionSpecificationApplications
BIP 392 ↗Silent Payment Output Script DescriptorsSpecificationApplications
BIP 393 ↗Output Script Descriptor AnnotationsSpecificationApplications
BIP 431 ↗Topology Restrictions for PinningInformationalApplications
BIP 433 ↗Pay to Anchor (P2A)InformationalApplications
BIP 440 ↗Varops Budget For Script Runtime ConstraintSpecificationConsensus (soft fork)
BIP 441 ↗Restoration of disabled script (Tapleaf 0xC2)SpecificationConsensus (soft fork)
BIP 442 ↗OP_PAIRCOMMITSpecificationConsensus (soft fork)
BIP 443 ↗OP_CHECKCONTRACTVERIFYSpecificationConsensus (soft fork)
BIP 446 ↗OP_TEMPLATEHASHSpecificationConsensus (soft fork)
BIP 448 ↗Taproot-native (Re)bindable TransactionsSpecificationConsensus (soft fork)
BIP 449 ↗OP_TWEAKADD - x-only key tweak additionSpecificationConsensus (soft fork)
BIP 450 ↗Formosa—Seed encoding by themed mnemonic storiesSpecificationApplications
BIP 451 ↗Dust UTXO Disposal ProtocolSpecificationApplications
BIP 461 ↗Deterministic ECDSA SignaturesSpecificationApplications

Complete22 BIPs

Its authors have finished their planned work and recommend adoption.

BIPs the repository lists as Complete: number, title, type and layer
BIPTitleType and layer
BIP 8 ↗Version bits with lock-in by heightInformationalNo layer named
BIP 18 ↗hashScriptCheckSpecificationConsensus (soft fork)
BIP 45 ↗Structure for Deterministic P2SH Multisignature WalletsSpecificationApplications
BIP 54 ↗Consensus CleanupSpecificationConsensus (soft fork)
BIP 67 ↗Deterministic Pay-to-script-hash multi-signature addresses through public key sortingSpecificationApplications
BIP 69 ↗Lexicographical Indexing of Transaction Inputs and OutputsInformationalApplications
BIP 87 ↗Hierarchy for Deterministic Multisig WalletsSpecificationApplications
BIP 88 ↗Hierarchical Deterministic Path TemplatesInformationalApplications
BIP 127 ↗Simple Proof-of-Reserves TransactionsSpecificationApplications
BIP 129 ↗Bitcoin Secure Multisig Setup (BSMS)SpecificationApplications
BIP 176 ↗Bits DenominationInformationalNo layer named
BIP 179 ↗Name for payment recipient identifiersInformationalNo layer named
BIP 321 ↗URI SchemeSpecificationApplications
BIP 322 ↗Generic Signed Message FormatSpecificationApplications
BIP 325 ↗SignetSpecificationApplications
BIP 328 ↗Derivation Scheme for MuSig2 Aggregate KeysInformationalApplications
BIP 347 ↗OP_CAT in TapscriptSpecificationConsensus (soft fork)
BIP 352 ↗Silent PaymentsSpecificationApplications
BIP 353 ↗DNS Payment InstructionsSpecificationApplications
BIP 373 ↗MuSig2 PSBT FieldsSpecificationApplications
BIP 388 ↗Wallet Policies for Descriptor WalletsSpecificationApplications
BIP 434 ↗Peer Feature NegotiationSpecificationPeer Services

Deployed78 BIPs

Advanced on evidence of active use, or for a Process BIP rough consensus; considered final.

BIPs the repository lists as Deployed: number, title, type and layer
BIPTitleType and layer
BIP 3 ↗Updated BIP ProcessProcessNo layer named
BIP 9 ↗Version bits with timeout and delayInformationalNo layer named
BIP 11 ↗M-of-N Standard TransactionsSpecificationApplications
BIP 13 ↗Address Format for pay-to-script-hashSpecificationApplications
BIP 14 ↗Protocol Version and User AgentSpecificationPeer Services
BIP 16 ↗Pay to Script HashSpecificationConsensus (soft fork)
BIP 22 ↗getblocktemplate - FundamentalsSpecificationAPI/RPC
BIP 23 ↗getblocktemplate - Pooled MiningSpecificationAPI/RPC
BIP 30 ↗Duplicate transactionsSpecificationConsensus (soft fork)
BIP 31 ↗Pong messageSpecificationPeer Services
BIP 32 ↗Hierarchical Deterministic WalletsInformationalApplications
BIP 34 ↗Block v2, Height in CoinbaseSpecificationConsensus (soft fork)
BIP 35 ↗mempool messageSpecificationPeer Services
BIP 37 ↗Connection Bloom filteringSpecificationPeer Services
BIP 38 ↗Passphrase-protected private keySpecificationApplications
BIP 39 ↗Mnemonic code for generating deterministic keysSpecificationApplications
BIP 42 ↗A finite monetary supply for BitcoinSpecificationConsensus (soft fork)
BIP 43 ↗Purpose Field for Deterministic WalletsSpecificationApplications
BIP 44 ↗Multi-Account Hierarchy for Deterministic WalletsSpecificationApplications
BIP 47 ↗Reusable Payment Codes for Hierarchical Deterministic WalletsSpecificationApplications
BIP 48 ↗Multi-Script Hierarchy for Multi-Sig WalletsSpecificationApplications
BIP 49 ↗Derivation scheme for P2WPKH-nested-in-P2SH based accountsSpecificationApplications
BIP 50 ↗March 2013 Chain Fork Post-MortemInformationalNo layer named
BIP 61 ↗Reject P2P messageSpecificationPeer Services
BIP 65 ↗OP_CHECKLOCKTIMEVERIFYSpecificationConsensus (soft fork)
BIP 66 ↗Strict DER signaturesSpecificationConsensus (soft fork)
BIP 68 ↗Relative lock-time using consensus-enforced sequence numbersSpecificationConsensus (soft fork)
BIP 70 ↗Payment ProtocolSpecificationApplications
BIP 71 ↗Payment Protocol MIME typesSpecificationApplications
BIP 72 ↗bitcoin: uri extensions for Payment ProtocolSpecificationApplications
BIP 73 ↗Use "Accept" header for response type negotiation with Payment Request URLsSpecificationApplications
BIP 75 ↗Out of Band Address Exchange using Payment Protocol EncryptionSpecificationApplications
BIP 78 ↗A Simple Payjoin ProposalSpecificationApplications
BIP 84 ↗Derivation scheme for P2WPKH based accountsSpecificationApplications
BIP 85 ↗Deterministic Entropy From BIP32 KeychainsInformationalApplications
BIP 86 ↗Key Derivation for Single Key P2TR OutputsSpecificationApplications
BIP 89 ↗Chain Code DelegationSpecificationApplications
BIP 90 ↗Buried DeploymentsInformationalNo layer named
BIP 91 ↗Reduced threshold Segwit MASFSpecificationConsensus (soft fork)
BIP 94 ↗Testnet 4SpecificationApplications
BIP 111 ↗NODE_BLOOM service bitSpecificationPeer Services
BIP 112 ↗CHECKSEQUENCEVERIFYSpecificationConsensus (soft fork)
BIP 113 ↗Median time-past as endpoint for lock-time calculationsSpecificationConsensus (soft fork)
BIP 123 ↗BIP ClassificationProcessNo layer named
BIP 125 ↗Opt-in Full Replace-by-Fee SignalingSpecificationApplications
BIP 130 ↗sendheaders messageSpecificationPeer Services
BIP 133 ↗feefilter messageSpecificationPeer Services
BIP 137 ↗Signatures of Messages using Private KeysSpecificationApplications
BIP 141 ↗Segregated Witness (Consensus layer)SpecificationConsensus (soft fork)
BIP 143 ↗Transaction Signature Verification for Version 0 Witness ProgramSpecificationConsensus (soft fork)
BIP 144 ↗Segregated Witness (Peer Services)SpecificationPeer Services
BIP 145 ↗getblocktemplate Updates for Segregated WitnessSpecificationAPI/RPC
BIP 147 ↗Dealing with dummy stack element malleabilitySpecificationConsensus (soft fork)
BIP 148 ↗Mandatory activation of segwit deploymentSpecificationConsensus (soft fork)
BIP 152 ↗Compact Block RelaySpecificationPeer Services
BIP 155 ↗addrv2 messageSpecificationPeer Services
BIP 157 ↗Client Side Block FilteringSpecificationPeer Services
BIP 158 ↗Compact Block Filters for Light ClientsSpecificationPeer Services
BIP 159 ↗NODE_NETWORK_LIMITED service bitSpecificationPeer Services
BIP 173 ↗Base32 address format for native v0-16 witness outputsInformationalApplications
BIP 174 ↗Partially Signed Bitcoin Transaction FormatSpecificationApplications
BIP 324 ↗Version 2 P2P Encrypted Transport ProtocolSpecificationPeer Services
BIP 327 ↗MuSig2 for BIP340-compatible Multi-SignaturesInformationalNo layer named
BIP 339 ↗WTXID-based transaction relaySpecificationPeer Services
BIP 340 ↗Schnorr Signatures for secp256k1SpecificationNo layer named
BIP 341 ↗Taproot: SegWit version 1 spending rulesSpecificationConsensus (soft fork)
BIP 342 ↗Validation of Taproot ScriptsSpecificationConsensus (soft fork)
BIP 350 ↗Bech32m format for v1+ witness addressesSpecificationApplications
BIP 370 ↗PSBT Version 2SpecificationApplications
BIP 371 ↗Taproot Fields for PSBTSpecificationApplications
BIP 380 ↗Output Script Descriptors General OperationSpecificationApplications
BIP 381 ↗Non-Segwit Output Script DescriptorsSpecificationApplications
BIP 382 ↗Segwit Output Script DescriptorsSpecificationApplications
BIP 383 ↗Multisig Output Script DescriptorsSpecificationApplications
BIP 384 ↗combo() Output Script DescriptorsSpecificationApplications
BIP 385 ↗raw() and addr() Output Script DescriptorsSpecificationApplications
BIP 386 ↗tr() Output Script DescriptorsSpecificationApplications
BIP 387 ↗Tapscript Multisig Output Script DescriptorsSpecificationApplications

Closed57 BIPs

Of historical interest only: not being worked on, promoted or in active use.

BIPs the repository lists as Closed: number, title, type and layer
BIPTitleType and layer
BIP 1 ↗BIP Purpose and GuidelinesProcessNo layer named
BIP 2 ↗BIP process, revisedProcessNo layer named
BIP 10 ↗Multi-Sig Transaction DistributionInformationalApplications
BIP 12 ↗OP_EVALSpecificationConsensus (soft fork)
BIP 15 ↗AliasesSpecificationApplications
BIP 17 ↗OP_CHECKHASHVERIFY (CHV)SpecificationConsensus (soft fork)
BIP 19 ↗M-of-N Standard Transactions (Low SigOp)SpecificationApplications
BIP 20 ↗URI SchemeSpecificationApplications
BIP 21 ↗URI SchemeSpecificationApplications
BIP 33 ↗Stratized NodesSpecificationPeer Services
BIP 36 ↗Custom ServicesSpecificationPeer Services
BIP 52 ↗Durable, Low Energy Bitcoin PoWSpecificationConsensus (hard fork)
BIP 60 ↗Fixed Length "version" Message (Relay-Transactions Field)SpecificationPeer Services
BIP 62 ↗Dealing with malleabilitySpecificationConsensus (soft fork)
BIP 64 ↗getutxo messageSpecificationPeer Services
BIP 74 ↗Allow zero value OP_RETURN in Payment ProtocolSpecificationApplications
BIP 79 ↗Bustapay :: a practical coinjoin protocolInformationalApplications
BIP 80 ↗Hierarchy for Non-Colored Voting Pool Deterministic Multisig WalletsInformationalNo layer named
BIP 81 ↗Hierarchy for Colored Voting Pool Deterministic Multisig WalletsInformationalNo layer named
BIP 83 ↗Dynamic Hierarchical Deterministic Key TreesSpecificationApplications
BIP 99 ↗Motivation and deployment of consensus rule changes ([soft/hard]forks)InformationalNo layer named
BIP 100 ↗Dynamic maximum block size by miner voteSpecificationConsensus (hard fork)
BIP 101 ↗Increase maximum block sizeSpecificationConsensus (hard fork)
BIP 102 ↗Block size increase to 2MBSpecificationConsensus (hard fork)
BIP 103 ↗Block size following technological growthSpecificationConsensus (hard fork)
BIP 104 ↗'Block75' - Max block size like difficultySpecificationConsensus (hard fork)
BIP 105 ↗Consensus based block size retargeting algorithmSpecificationConsensus (hard fork)
BIP 106 ↗Dynamically Controlled Bitcoin Block Size Max CapSpecificationConsensus (hard fork)
BIP 107 ↗Dynamic limit on the block sizeSpecificationConsensus (hard fork)
BIP 109 ↗Two million byte size limit with sigop and sighash limitsSpecificationConsensus (hard fork)
BIP 110 ↗Reduced Data Temporary SoftforkSpecificationConsensus (soft fork)
BIP 114 ↗Merkelized Abstract Syntax TreeSpecificationConsensus (soft fork)
BIP 115 ↗Generic anti-replay protection using ScriptSpecificationConsensus (soft fork)
BIP 120 ↗Proof of PaymentSpecificationApplications
BIP 121 ↗Proof of Payment URI schemeSpecificationApplications
BIP 124 ↗Hierarchical Deterministic Script TemplatesInformationalApplications
BIP 131 ↗"Coalescing Transaction" Specification (wildcard inputs)SpecificationConsensus (hard fork)
BIP 132 ↗Committee-based BIP Acceptance ProcessProcessNo layer named
BIP 134 ↗Flexible TransactionsSpecificationConsensus (hard fork)
BIP 135 ↗Generalized version bits votingInformationalNo layer named
BIP 140 ↗Normalized TXIDSpecificationConsensus (soft fork)
BIP 142 ↗Address Format for Segregated WitnessSpecificationApplications
BIP 146 ↗Dealing with signature encoding malleabilitySpecificationConsensus (soft fork)
BIP 149 ↗Segregated Witness (second deployment)SpecificationConsensus (soft fork)
BIP 150 ↗Peer AuthenticationSpecificationPeer Services
BIP 151 ↗Peer-to-Peer Communication EncryptionSpecificationPeer Services
BIP 154 ↗Rate Limiting via peer specified challengesSpecificationPeer Services
BIP 156 ↗Dandelion - Privacy Enhancing RoutingSpecificationPeer Services
BIP 171 ↗Currency/exchange rate information APISpecificationApplications
BIP 175 ↗Pay to Contract ProtocolInformationalApplications
BIP 180 ↗Block size/weight fraud proofSpecificationPeer Services
BIP 199 ↗Hashed Time-Locked Contract transactionsSpecificationApplications
BIP 338 ↗Disable transaction relay messageSpecificationPeer Services
BIP 343 ↗Mandatory activation of taproot deploymentSpecificationConsensus (soft fork)
BIP 345 ↗OP_VAULTSpecificationConsensus (soft fork)
BIP 351 ↗Private PaymentsSpecificationApplications
BIP 391 ↗Binary Output DescriptorsSpecificationApplications

Bitcoin Core security advisories, by the day bitcoincore.org posted them

25advisories

in bitcoincore.org’s index of past advisories when the desk read it on ; the latest was posted on

Advisories posted so far · a step on each day a post went up

  1. · 4 advisories

  2. · 3 advisories

  3. · 2 advisories

  4. · 10 advisories

The date is the day the post went up. When a flaw was found, which releases fixed it and how severe it was are in each post, and are not read here.

Issuer · bitcoincore.org, read  ·advisory index ↗

Dates, sources & limits

Dataset sg-core-lifecycle, method 1.0.0. The past advisories as bitcoincore.org's index lists them, newest first. The date is the post's, from its URL; severity and fixed-in versions live in each post and are not parsed here.

The line starts at the index’s first post, on 20 Sep 2018, not at zero: a flaw disclosed before the index begins is not in it. Each step is the number of posts dated that day, and the line runs flat to the day the index was read.

Reproduce this page1 dataset: 1 committed file, 1 checksum and 1 builder

The builders are files in the Gazette’s repository, which is not public, so a reader cannot run the commands under Rebuild today. Each is printed so the builder is named beside the rule it applies and the sources it reads.

A dry run reads the sources as they stand, checks the result with the site’s own loader and prints one line of JSON saying whether the committed file would change. It leaves the committed file as it is; without --dry-run the same command writes it. Not every run builds the file again from nothing: some builders keep what the committed file holds and read only what is new, and each such entry says so under its command.

Downloads carries the same data: each file there is built from the committed file named here, and each dataset below says what its file holds. Download one, take its sha256 and set it against the one printed below and in the dataset’s metadata file.shasum -a 256 <file>

  • Bitcoin Improvement Proposals by status

    Dataset ID sg-bip-status · method 1.0.0

    Committed file
    content/data/bip-status.json
    Dated

    Latest record 3 Oct 2026, 14:43 UTC

    Dated snapshot · bitcoin/bips at commit 927b6de · read 3 Oct 2026

    On Downloads

    Bitcoin Improvement Proposals by status, sg-bip-status.json · 56 kB

    It holds the contents of content/data/bip-status.json.

    Its sha256 is e8901995d2ad65a8958b6576ca267b379d3bcebd4622c83fec7f9c7a7a19505c

    sg-bip-status.metadata.json carries the same checksum.

    Bitcoin Improvement Proposals by status: Its entry on Downloads →

    Rebuild

    Builder scripts/build-bip-status.mjs

    node scripts/build-bip-status.mjs --dry-run

    The run reads the index and every BIP again, at the repository’s newest commit. The status changes already recorded are kept as they are: each is dated by the day the desk saw it, which the repository does not hold.

    Refreshed by

    By hand, with the desk’s own builder and validator

    Its rule

    Each row is the BIP’s own preamble, read at one commit of the repository and matched against the repository’s index on number, layer, type and status. A preamble that does not read as BIP 3 lays it out, or disagrees with the index, is held at what was last recorded, with its reason; nothing is guessed. The four statuses are BIP 3’s own words, checked against BIP 3’s text on each read, and nothing is mapped onto them. A status is not an endorsement and does not say a consensus change has activated. A change is recorded on the day the desk sees it, not the day it happened, and a recorded change is never rewritten. A read that fails or is partial writes nothing.

    Bitcoin Improvement Proposals by status: Its entry in the method →

Also on this page

  • This page also prints the security advisories from Bitcoin Core release lifecycle (sg-core-lifecycle), which the register files under Nodes & releases. Its file and builder are listed in that page’s block.

    Reproduce Nodes & releases →