BIP Index
Of the 400-plus Bitcoin Improvement Proposals (BIPs), this index maintains dedicated pages for 19 core specifications. Articles may link directly to other primary proposals, including drafts, without adding a dedicated index page. What each page carries is a summary in plain language, not a translation: the original document is authoritative, and for implementation or verification you should always consult the primary source linked from every page.
| No. | Title | Status | Assigned |
|---|---|---|---|
| BIP 8 | Version bits with lock-in by heightInformational | Complete | |
| BIP 9 | Version bits with timeout and delayInformational | Deployed | |
| BIP 32 | Hierarchical Deterministic WalletsInformational / Applications | Deployed | |
| BIP 34 | Block v2, Height in CoinbaseSpecification / Consensus (soft fork) | Deployed | |
| BIP 39 | Mnemonic code for generating deterministic keysSpecification / Applications | Deployed | |
| BIP 44 | Multi-Account Hierarchy for Deterministic WalletsSpecification / Applications | Deployed | |
| BIP 49 | Derivation scheme for P2WPKH-nested-in-P2SH based accountsSpecification / Applications | Deployed | |
| BIP 84 | Derivation scheme for P2WPKH based accountsSpecification / Applications | Deployed | |
| BIP 86 | Key Derivation for Single Key P2TR OutputsSpecification / Applications | Deployed | |
| BIP 125 | Opt-in Full Replace-by-Fee SignalingSpecification / Applications | Deployed | |
| BIP 141 | Segregated Witness (Consensus layer)Specification / Consensus (soft fork) | Deployed | |
| BIP 143 | Transaction Signature Verification for Version 0 Witness ProgramSpecification / Consensus (soft fork) | Deployed | |
| BIP 144 | Segregated Witness (Peer Services)Specification / Peer Services | Deployed | |
| BIP 173 | Base32 address format for native v0-16 witness outputsInformational / Applications | Deployed | |
| BIP 174 | Partially Signed Bitcoin Transaction FormatSpecification / Applications | Deployed | |
| BIP 340 | Schnorr Signatures for secp256k1Specification | Deployed | |
| BIP 341 | Taproot: SegWit version 1 spending rulesSpecification / Consensus (soft fork) | Deployed | |
| BIP 342 | Validation of Taproot ScriptsSpecification / Consensus (soft fork) | Deployed | |
| BIP 350 | Bech32m format for v1+ witness addressesSpecification / Applications | Deployed |
Status and Type were read from the source documents in the bips repository on 2026-11-03. The next check is due by 2027-02-01.
What a BIP is, and how to read Status and Type
A BIP (Bitcoin Improvement Proposal) is the document format used to propose, describe, and discuss changes and conventions in Bitcoin. Because Bitcoin has no central authority that decides changes, a BIP is a proposal and its record rather than a decision: it takes effect only when implementations adopt it and nodes enforce it as a validation rule. Numbers are assigned in the order proposals are accepted and say nothing about importance.
Each BIP opens with a preamble carrying a Status and a Type. Under the current process (BIP 3), Status is one of Draft, Complete, Deployed, or Closed, where Deployed means the proposal is actually in use. Type distinguishes Specification, Informational, and Process documents, while Layer indicates which layer a change touches (Consensus, Peer Services, or Applications).