
The ideas
underneath it all.
Bitcoin Improvement Proposals describe shared conventions and technical changes. Follow the connections from a recovery phrase to a signed transaction.
Explore the standardsFollow the connections.
One common route through the standards, not a mandatory stack. Taproot accounts use BIP86 instead of BIP84; wallet implementations vary.
49 standards
From randomness to words
A way to represent computer-generated randomness as a word sequence, then derive a wallet seed from those words and an optional passphrase.
Deployed Explore the standardOne seed. A tree of keys.
Hierarchical deterministic wallets derive related keys from a root, making organized accounts and address sequences possible.
Deployed Explore the standardAn address for every account
A shared hierarchy gives purpose, coin type, account, change and address index their own place in a derivation path.
Deployed Explore the standardNative SegWit accounts
A derivation convention for single-key P2WPKH accounts, using purpose 84.
Deployed Explore the standardSingle-key Taproot accounts
A derivation convention for single-key Taproot outputs, using purpose 86.
Deployed Explore the standardPass a transaction. Keep the keys.
The PSBT format packages an unsigned transaction with information needed by separate creators, updaters, signers and finalizers.
Deployed Explore the standardSchnorr signatures
A precise Schnorr signature scheme for the secp256k1 curve used by Bitcoin.
Deployed Explore the standardTaproot spending rules
Taproot combines a key-spend path with the ability to commit to alternative script conditions.
Deployed Explore the standardDescribe the wallet, not just its keys
Descriptors express how keys and scripts produce a wallet’s outputs. The general format also defines an error-detecting checksum.
Deployed Explore the standardSpend to a script hash
P2SH lets an address commit to a spending script without putting the whole script in the receiving address.
Deployed Explore the standardThe familiar payment link
The original bitcoin: URI format carries a destination and optional amount or payment label.
Closed Explore the standardA shared path for multisig
A derivation hierarchy organizes multisig accounts and script types under purpose 48.
Deployed Explore the standardSegWit inside a familiar address
Purpose 49 defines accounts for P2WPKH nested inside P2SH.
Deployed Explore the standardA lock until a point in time
CHECKLOCKTIMEVERIFY can require a spending transaction to respect an absolute block-height or time lock.
Deployed Explore the standardPut the keys in the same order
Lexicographic sorting of compressed public keys makes multisig script construction deterministic.
Complete Explore the standardA lock measured from confirmation
Sequence fields can express relative transaction locks based on the age of the outputs being spent.
Deployed Explore the standardA spending path with a delay
CHECKSEQUENCEVERIFY lets a script require a relative lock, working with BIP 68 sequence rules.
Deployed Explore the standardWhy a payment can be replaced
BIP 125 describes opt-in transaction-replacement signalling and an associated relay policy.
Deployed Explore the standardSegWit: a different transaction structure
Segregated Witness separates witness data and introduces block weight and versioned witness programs.
Deployed Explore the standardWhat a SegWit signature commits to
A signing digest for version-0 witness programs includes the input amount and reuses shared transaction hashes.
Deployed Explore the standardRecognize a native SegWit address
Bech32 encodes witness addresses with a human-readable prefix and a checksum.
Deployed Explore the standardBech32m for newer witness versions
Bech32m changes the checksum constant for witness version 1 and later addresses.
Deployed Explore the standardThe script side of Taproot
Tapscript defines validation rules for Taproot script-path spends, including Schnorr signature checks.
Deployed Explore the standardPSBT, version two
PSBT v2 stores transaction pieces in input and output maps rather than a single global unsigned transaction.
Deployed Explore the standardCarry Taproot through a PSBT
Additional PSBT fields carry Taproot signatures, scripts, key origins and related information.
Deployed Explore the standardDescribe a multisig wallet
The multi() and sortedmulti() descriptor expressions record a threshold and public keys.
Deployed Explore the standardDescribe a Taproot wallet
The tr() descriptor expression combines an internal key with an optional script tree.
Deployed Explore the standardAgree on the same multisig wallet
Bitcoin Secure Multisig Setup specifies how participants exchange and verify a shared wallet configuration.
Complete Explore the standardEncrypt the peer-to-peer connection
Version-2 Bitcoin P2P transport adds opportunistic encryption to node connections.
Deployed Explore the standardMany signers. One Schnorr signature.
MuSig2 combines participant keys and partial signatures into a BIP 340-compatible signature.
Deployed Explore the standardDerive from an aggregate key
BIP 328 defines a BIP 32-compatible extended public key for MuSig2 aggregate keys.
Complete Explore the standardReceive without reusing an on-chain address
Silent Payments lets a recipient publish static payment information while senders create distinct on-chain outputs.
Complete Explore the standardPayment instructions under a name
DNS-based payment instructions use DNSSEC-authenticated records to publish a payment URI.
Complete Explore the standardCoordinate MuSig2 in a PSBT
Additional PSBT fields carry MuSig2 participant keys, public nonces and partial signatures.
Complete Explore the standardSilent Payments in a signing package
A proposed PSBT v2 extension carries the data needed to coordinate Silent Payment outputs.
Proposal · Draft Explore the standardA policy a signing device can understand
Wallet policies describe descriptor-based accounts using a compact template and separate key information.
Complete Explore the standardOne descriptor. Several branches.
Multipath key expressions compactly describe alternatives such as receiving and change branches.
Draft Explore the standardA proposed consensus cleanup
A soft-fork proposal addresses timewarp behavior and several validation edge cases.
Proposal · Complete Explore the standardCommit to a transaction template
CHECKTEMPLATEVERIFY proposes an opcode that restricts a spend to a committed transaction template.
Proposal · Draft Explore the standardA proposed script-only commitment
Pay-to-Merkle-Root proposes an output format without Taproot’s key-path spending route.
Proposal · Draft Explore the standardModern Bitcoin payment links
The replacement for BIP 21 documents current bitcoin: URI usage and extensible payment instructions.
Complete Explore the standardPut MuSig2 in a descriptor
The musig() key expression describes an aggregate key assembled from multiple participants.
Draft Explore the standardA reusable payment code
Payment codes let compatible wallets derive fresh payment addresses from a publicly shared identifier.
Deployed Explore the standardA payment made together
Payjoin lets sender and receiver negotiate a transaction that includes contributions from both parties.
Deployed Explore the standardDerive separate backups from one root
BIP 85 derives deterministic entropy from a BIP 32 root for applications such as child mnemonic phrases.
Deployed Explore the standardLet a light wallet check locally
Client-side block filtering lets a wallet download compact filters and decide locally which blocks may interest it.
Deployed Explore the standardA compact clue about a block
Compact block filters encode selected block data using Golomb-Rice coding for efficient light-client checks.
Deployed Explore the standardKeep the story behind your coins
A JSON Lines format carries wallet labels and related metadata between compatible applications.
Draft Explore the standardMake spending policies easier to reason about
Miniscript expresses a structured subset of Bitcoin Script so tools can analyze and compose spending conditions.
Draft Explore the standardStatus labels are copied from the official repository, checked 13 November 2026. “Complete” describes the specification, not activation. Newer standards are a selection, not a ranking by adoption. A BIP number is not itself evidence of network activation, universal wallet support or endorsement.
The complete official BIP repository ↗