Skip to content

BIP Index

An index of the Bitcoin Improvement Proposals cited across this library, each with a plain-language summary.

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). Every value shown here was read directly from the source document in the bips repository, and each page states the date it was verified.

This index is deliberately not exhaustive. Of the 400-plus proposals, it covers the 19 that the articles in this library actually cite. 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.

BIPs covered in this index
No.TitleStatusAssigned
BIP 8Version bits with lock-in by heightInformationalComplete
BIP 9Version bits with timeout and delayInformationalDeployed
BIP 32Hierarchical Deterministic WalletsInformational / ApplicationsDeployed
BIP 34Block v2, Height in CoinbaseSpecification / Consensus (soft fork)Deployed
BIP 39Mnemonic code for generating deterministic keysSpecification / ApplicationsDeployed
BIP 44Multi-Account Hierarchy for Deterministic WalletsSpecification / ApplicationsDeployed
BIP 49Derivation scheme for P2WPKH-nested-in-P2SH based accountsSpecification / ApplicationsDeployed
BIP 84Derivation scheme for P2WPKH based accountsSpecification / ApplicationsDeployed
BIP 86Key Derivation for Single Key P2TR OutputsSpecification / ApplicationsDeployed
BIP 125Opt-in Full Replace-by-Fee SignalingSpecification / ApplicationsDeployed
BIP 141Segregated Witness (Consensus layer)Specification / Consensus (soft fork)Deployed
BIP 143Transaction Signature Verification for Version 0 Witness ProgramSpecification / Consensus (soft fork)Deployed
BIP 144Segregated Witness (Peer Services)Specification / Peer ServicesDeployed
BIP 173Base32 address format for native v0-16 witness outputsInformational / ApplicationsDeployed
BIP 174Partially Signed Bitcoin Transaction FormatSpecification / ApplicationsDeployed
BIP 340Schnorr Signatures for secp256k1SpecificationDeployed
BIP 341Taproot: SegWit version 1 spending rulesSpecification / Consensus (soft fork)Deployed
BIP 342Validation of Taproot ScriptsSpecification / Consensus (soft fork)Deployed
BIP 350Bech32m format for v1+ witness addressesSpecification / ApplicationsDeployed

Status and Type were read from the source documents in the bips repository on 2026-08-17.

Related articles

The specifications make more sense alongside the articles that explain how they are used in practice.