Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
The Bitcoin Improvement Proposal Atlas · 2026-11-17

Every BIP ever numbered. What shipped, what blew up, what’s next.

218 proposals sit in the official bitcoin/bips repository. Only 8 soft-fork activations ever changed Bitcoin’s consensus rules — the rest is wallets, networking, process, and a long list of fights. Here is all of it, sourced, searchable and linked to the people and episodes of Bitcoin Takeover.

Deployed 80Complete 22Draft 59Closed 57activated soft fork
Every square is a BIP. Tap one.
Statuses as written in each BIP header at commit a7f9132 (2026-11-17). BIP 3 replaced the old Final/Rejected/Withdrawn labels with Draft · Complete · Deployed · Closed.
01

The shape of 218 proposals

#

Click any bar to filter the explorer. 63 BIPs touch consensus; 13 of them are part of an activated soft fork. Every one of the 12 hard-fork proposals is Closed.

Status funnel

Where proposals end up

80 Deployed: in active use (BIP 3: evidence of deployment, or a soft fork’s activation criteria met)80Deployed37%22 Complete: authors finished; recommended for adoption22Complete10%59 Draft: being worked on59Draft27%57 Closed: historical only: abandoned, rejected, replaced or withdrawn57Closed26%
Deployed — in active use (BIP 3: evidence of deployment, or a soft fork’s activation criteria met)Complete — authors finished; recommended for adoptionDraft — being worked onClosed — historical only: abandoned, rejected, replaced or withdrawn
Layer

What part of Bitcoin they touch

ApplicationsApplications: 38 DeployedApplications: 15 CompleteApplications: 30 DraftApplications: 17 Closed100Consensus (soft fork)Consensus (soft fork): 16 DeployedConsensus (soft fork): 3 CompleteConsensus (soft fork): 21 DraftConsensus (soft fork): 11 Closed51Peer ServicesPeer Services: 16 DeployedPeer Services: 1 CompletePeer Services: 3 DraftPeer Services: 10 Closed30Consensus (hard fork)Consensus (hard fork): 12 Closed12API/RPCAPI/RPC: 3 DeployedAPI/RPC: 1 Draft4Process / no layerProcess / no layer: 7 DeployedProcess / no layer: 3 CompleteProcess / no layer: 4 DraftProcess / no layer: 7 Closed21
Proposals by year assigned (current status)

2011–2026: two war years and a 2026 boom

01020302011: 3 Deployed2011: 5 Closed820112012: 10 Deployed2012: 1 Complete2012: 5 Closed1620122013: 6 Deployed2013: 1 Closed720132014: 5 Deployed2014: 1 Complete2014: 4 Closed1020142015: 12 Deployed2015: 2 Complete2015: 1 Draft2015: 16 Closed3120152016: 8 Deployed2016: 1 Draft2016: 9 Closed1820162017: 8 Deployed2017: 2 Complete2017: 6 Draft2017: 9 Closed2520172018: 1 Complete2018: 3 Draft2018: 1 Closed520182019: 4 Deployed2019: 3 Complete2019: 3 Draft1020192020: 7 Deployed2020: 3 Complete2020: 1 Draft2020: 1 Closed1220202021: 10 Deployed2021: 1 Draft2021: 2 Closed1320212022: 1 Deployed2022: 5 Draft2022: 1 Closed720222023: 1 Deployed2023: 3 Complete2023: 2 Draft2023: 1 Closed720232024: 2 Deployed2024: 4 Complete2024: 9 Draft1520242025: 2 Deployed2025: 1 Complete2025: 6 Draft2025: 1 Closed1020252026: 1 Deployed2026: 1 Complete2026: 21 Draft2026: 1 Closed242026Block size warSegWit / UASFCovenants · quantum · BIP 3
Top authors

Who writes the BIPs

Pieter WuillePieter Wuille: 23 DeployedPieter Wuille: 1 DraftPieter Wuille: 3 Closed27Ava ChowAva Chow: 13 DeployedAva Chow: 2 CompleteAva Chow: 3 Draft18Luke DashjrLuke Dashjr: 3 DeployedLuke Dashjr: 3 CompleteLuke Dashjr: 7 Closed13Gavin AndresenGavin Andresen: 9 DeployedGavin Andresen: 3 Closed12Matt CoralloMatt Corallo: 3 DeployedMatt Corallo: 3 CompleteMatt Corallo: 1 DraftMatt Corallo: 1 Closed8BtcDrakBtcDrak: 2 DeployedBtcDrak: 4 DraftBtcDrak: 1 Closed7Karl-Johan AlmKarl-Johan Alm: 2 CompleteKarl-Johan Alm: 4 DraftKarl-Johan Alm: 1 Closed7Mark FriedenbachMark Friedenbach: 3 DeployedMark Friedenbach: 3 Draft6Eric LombrozoEric Lombrozo: 4 DeployedEric Lombrozo: 2 Closed6Johnson LauJohnson Lau: 3 DeployedJohnson Lau: 3 Closed6Anthony TownsAnthony Towns: 2 DeployedAnthony Towns: 2 CompleteAnthony Towns: 2 Draft6Amir TaakiAmir Taaki: 1 DeployedAmir Taaki: 4 Closed5Fabian JahrFabian Jahr: 2 DeployedFabian Jahr: 3 Draft5Jonas SchnelliJonas Schnelli: 2 DeployedJonas Schnelli: 1 DraftJonas Schnelli: 2 Closed5
The people behind the BIPs

Faces of the proposals #

Every author with two or more BIPs, plus everyone with a Wiki page. Photos are each person’s own X or GitHub picture and link to that profile; initials where we could not confidently match an account.

Pieter Wuille
Pieter Wuille27 BIPs · Wiki · X
Ava Chow
Ava Chow18 BIPs · X
Luke Dashjr
Luke Dashjr13 BIPs · Wiki · X
Gavin Andresen
Gavin Andresen12 BIPs · Wiki · X
Matt Corallo
Matt Corallo8 BIPs · Wiki · X
BtcDrak
BtcDrak7 BIPs · X
Karl-Johan Alm
Karl-Johan Alm7 BIPs · X
Anthony Towns
Anthony Towns6 BIPs · X
Eric Lombrozo
Eric Lombrozo6 BIPs · Wiki · X
Johnson Lau
Johnson Lau6 BIPs · Wiki · GitHub
Jonas Nick
Jonas Nick5 BIPs · X
Jonas Schnelli
Jonas Schnelli5 BIPs · X
Antoine Poinsot
Antoine Poinsot4 BIPs · Wiki · X
Brandon Black
Brandon Black4 BIPs · X
Jeremy Rubin
Jeremy Rubin4 BIPs · Wiki · X
Mike Hearn
Mike Hearn4 BIPs · Wiki · GitHub
Pavol Rusnak
Pavol Rusnak4 BIPs · X
Peter Todd
Peter Todd4 BIPs · Wiki · X
Steven Roose
Steven Roose4 BIPs · X
Tim Ruffing
Tim Ruffing4 BIPs · X
Craig Raw
Craig Raw3 BIPs · X
Jeff Garzik
Jeff Garzik3 BIPs · Wiki · X
Jimmy Song
Jimmy Song3 BIPs · X
Rusty Russell
Rusty Russell3 BIPs · X
Shaolin Fry
Shaolin Fry3 BIPs · X
Chris Belcher
Chris Belcher2 BIPs · X
CryptAxe2 BIPs
Ethan Heilman
Ethan Heilman2 BIPs · X
Kristov Atlas
Kristov Atlas2 BIPs · X
Nicolas Dorier
Nicolas Dorier2 BIPs · X
Paul Sztorc
Paul Sztorc2 BIPs · Wiki · X
Pyth2 BIPs
Ruben Somsen
Ruben Somsen2 BIPs · X
Sean Bowe
Sean Bowe2 BIPs · X
josibake
josibake2 BIPs · GitHub
Jameson Lopp
Jameson Lopp1 BIP · Wiki · X
02

8 times Bitcoin’s rules changed

#

Every consensus soft fork that activated on mainnet, with the block it started and how it was switched on. Heights come from Bitcoin Core’s chain parameters and the BIPs; dates from the block headers (UTC).

2012

P2SH · Pay to Script Hash

2012-04-01 · BIP 16

Let anyone pay to a short hash of a script (the “3…” addresses). Multisig and later wrapped SegWit became as easy to receive as a normal payment.

Miner coinbase vote (“/P2SH/”, 550 of ~1,000 blocks), then a flag day: timestamps ≥ 1333238400
Sources · 3BIP 16, “Pay to Script Hash”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 13, “Address Format for pay-to-script-hash”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, doc/bips.md — BIPs implemented by Bitcoin Core (master, read 20 Nov 2026)
2013

BIP 34 · Height in coinbase

Block 227,931 · 2013-03-25 · BIP 34

Every block must write its own height into the coinbase. Coinbase transactions became unique, and the first miner-signalled upgrade mechanism was born.

Version supermajority: 750/1,000 then 950/1,000 blocks (version 2)
Sources · 3BIP 34, “Block v2, Height in Coinbase”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, src/kernel/chainparams.cpp — mainnet BIP34/65/66/CSV/SegWit heights · mempool.space, block 227,931
2015

BIP 66 · Strict DER signatures

Block 363,725 · 2015-07-04 · BIP 66

Forced one exact signature encoding so Bitcoin no longer depended on OpenSSL's quirks for consensus, and removed a malleability source.

Version supermajority (version 3), 95% rule
Sources · 4BIP 66, “Strict DER signatures”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 90, “Buried Deployments”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, src/kernel/chainparams.cpp — mainnet BIP34/65/66/CSV/SegWit heights · mempool.space, block 363,725
2015

CLTV · OP_CHECKLOCKTIMEVERIFY

Block 388,381 · 2015-12-14 · BIP 65

Coins can be locked until a future date or block height. The building block for timelocked refunds, payment channels and the Lightning Network.

Version supermajority (version 4), 95% rule
Sources · 4BIP 65, “OP_CHECKLOCKTIMEVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 90, “Buried Deployments”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, src/kernel/chainparams.cpp — mainnet BIP34/65/66/CSV/SegWit heights · mempool.space, block 388,381
2016

CSV · Relative timelocks

Block 419,328 · 2016-07-04 · BIP 68 BIP 112 BIP 113

“Spendable N blocks after this coin confirmed” (relative timelocks) plus median-time-past for lock times. Lightning's penalty and timeout paths rely on it.

BIP 9 version bits — the first BIP 9 deployment
Sources · 5BIP 68, “Relative lock-time using consensus-enforced sequence numbers”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 112, “CHECKSEQUENCEVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 113, “Median time-past as endpoint for lock-time calculations”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, src/kernel/chainparams.cpp — mainnet BIP34/65/66/CSV/SegWit heights · mempool.space, block 419,328
2017

SegWit · Segregated Witness

Block 481,824 · 2017-08-24 · BIP 141 BIP 143 BIP 147

Moved signatures into a separate “witness”, fixed third-party malleability, replaced the 1 MB size limit with 4 million weight units and added script versioning. It made Lightning practical.

BIP 9 bit 1 (95%), after BIP 91 forced signalling and the BIP 148 UASF deadline
Sources · 6BIP 141, “Segregated Witness (Consensus layer)”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 143, “Transaction Signature Verification for Version 0 Witness Program”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 147, “Dealing with dummy stack element malleability”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, src/kernel/chainparams.cpp — mainnet BIP34/65/66/CSV/SegWit heights · mempool.space, block 481,824 · Bitcoin: All the Hard Forks and Soft Forks (BTCTKVR: Forks!)
2021

Taproot · Schnorr + Tapscript

Block 709,632 · 2021-11-14 · BIP 340 BIP 341 BIP 342

Schnorr signatures, key aggregation and MAST-style script trees: complex spending conditions can look like an ordinary single-signature payment. Also the upgrade path for future opcodes.

Speedy Trial: BIP 9 variant, bit 2, 90% (1,815 of 2,016), min_activation_height 709,632
Sources · 5BIP 340, “Schnorr Signatures for secp256k1”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 341, “Taproot: SegWit version 1 spending rules”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 342, “Validation of Taproot Scripts”, bitcoin/bips (commit a7f9132, 2026-11-17) · mempool.space, block 709,632 · Bitcoin Core 0.21.1 release notes (Taproot activation parameters)
BIP 42 — A finite monetary supply: a code fix (Bitcoin Core v0.9.2) for a bug that would have restarted the block subsidy after block 13,440,000. No activation moment; it matters only centuries from now.
Sources · 2BIP 42, “A finite monetary supply for Bitcoin”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, doc/bips.md — BIPs implemented by Bitcoin Core (master, read 20 Nov 2026)
BIP 91 / BIP 148 — Not soft forks of their own but mechanisms that forced SegWit signalling in July–August 2017. Both are marked Deployed in the repository.
Sources · 3BIP 91, “Reduced threshold Segwit MASF”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 148, “Mandatory activation of segwit deployment”, bitcoin/bips (commit a7f9132, 2026-11-17) · Fork Wars: the block size war timeline (Bitcoin Takeover)
BIP 90 — Buried deployments: replaced the old version-counting triggers of BIP 34/65/66 with fixed heights (Bitcoin Core v0.14.0).
Sources · 2BIP 90, “Buried Deployments”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Core, doc/bips.md — BIPs implemented by Bitcoin Core (master, read 20 Nov 2026)
Since Taproot — No consensus change has activated on Bitcoin since block 709,632 (14 Nov 2021). The closest call was BIP-110: nodes enforcing it split off at block 961,632 on 8 Aug 2026 and the rest of the network carried on without it.
Sources · 3BIP 110, “Reduced Data Temporary Softfork”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin BLAKE2b: The Fork That Fired the Miners (BTCTKVR: Forks!) · mempool.space, block 961,632 (first block of BIP-110's mandatory-signalling window)
03

The silent backbone

#
74standards in use

Consensus forks get the headlines, but most BIPs that matter never touch consensus. Your seed words, your hardware wallet’s PSBT, your node’s encrypted connections and compact blocks are all BIPs. We count a non-consensus BIP as in use when its header says Deployed (BIP 3 requires evidence of active use) or Bitcoin Core lists it as implemented (74 BIPs in doc/bips.md). A selection:

Keys, seeds & wallets

BIP 32
Hierarchical Deterministic Wallets
HD wallets: one master seed deterministically produces an entire tree of keys. Practically every modern wallet is built on this.
✓ Bitcoin Core: since v0.13.0.
BIP 39
Mnemonic code for generating deterministic keys
The 12/24-word seed phrase. Probably the most widely used BIP for ordinary people, although Bitcoin Core itself never adopted it.
✓ Repo status: Deployed
BIP 43
Purpose Field for Deterministic Wallets
Reserved the first level of an HD wallet path for a “purpose” number, so 44/49/84/86 could coexist.
✓ Bitcoin Core: in v0.21.0
BIP 44
Multi-Account Hierarchy for Deterministic Wallets
The m/44'/0'/0' account structure for HD wallets, used by most multi-coin hardware and software wallets.
✓ Bitcoin Core: in v0.21.0
BIP 49
Derivation scheme for P2WPKH-nested-in-P2SH based accounts
Derivation paths for wrapped SegWit (“3…” P2SH-P2WPKH) accounts.
✓ Bitcoin Core: in v0.21.0
BIP 84
Derivation scheme for P2WPKH based accounts
Derivation paths for native SegWit (bc1q…) single-sig wallets.
✓ Bitcoin Core: in v0.21.0
BIP 86
Key Derivation for Single Key P2TR Outputs
Derivation paths for single-key Taproot (bc1p…) wallets.
✓ Bitcoin Core: since v23.0.
BIP 85
Deterministic Entropy From BIP32 Keychains
Derive child seeds and passwords deterministically from one master key (BIP-85 “child seeds”).
✓ Repo status: Deployed
BIP 47
Reusable Payment Codes for Hierarchical Deterministic Wallets
Reusable payment codes (PayNyms): a static code you can publish without address reuse.
✓ Repo status: Deployed
BIP 380
Output Script Descriptors General Operation
Output script descriptors: a compact text format that fully describes which scripts a wallet watches — the backbone of modern wallet backups.
✓ Bitcoin Core: as of v0.17.0.
BIP 386
tr() Output Script Descriptors
tr() descriptors for Taproot outputs.
✓ Bitcoin Core: as of v22.0.
BIP 379
Miniscript
Miniscript: a structured language for Bitcoin scripts that wallets can analyse, compose and sign generically.
✓ Bitcoin Core: in v24.0
BIP 388
Wallet Policies for Descriptor Wallets
Wallet policies: a descriptor variant designed for hardware wallets to register and display multisig policies.
✓ Repo status: Complete
BIP 390
musig() Descriptor Key Expression
musig() descriptor key expressions (Bitcoin Core v30 parsing, v31 signing).
✓ Bitcoin Core: in v30.0
BIP 327
MuSig2 for BIP340-compatible Multi-Signatures
MuSig2: several parties produce one Schnorr signature for one aggregated key. Multisig that looks like single-sig on-chain.
✓ Bitcoin Core: as of v30.0.
BIP 328
Derivation Scheme for MuSig2 Aggregate Keys
This document specifies how BIP 32 extended public keys can be constructed from a BIP 327 MuSig2 aggregate public key and how such keys should be used for key derivation.
✓ Bitcoin Core: as of v30.0

Transactions & addresses

BIP 13
Address Format for pay-to-script-hash
The “3…” address format for pay-to-script-hash. Every multisig and wrapped-SegWit address you have seen comes from here.
✓ Bitcoin Core: since v0.6.0.
BIP 21
URI Scheme
The bitcoin: URI scheme behind every clickable or QR-code payment request.
✓ Bitcoin Core: since v0.6.0.
BIP 173
Base32 address format for native v0-16 witness outputs
Bech32 — the bc1q… address format with strong error detection.
✓ Bitcoin Core: as of v0.16.0.
BIP 350
Bech32m format for v1+ witness addresses
Bech32m — the bc1p… address format for Taproot and future witness versions, fixing a Bech32 weakness.
✓ Bitcoin Core: as of v22.0.
BIP 174
Partially Signed Bitcoin Transaction Format
PSBT: a standard file format for passing an unsigned transaction between wallets, hardware signers and coordinators.
✓ Bitcoin Core: as of v0.17.0.
BIP 370
PSBT Version 2
PSBT version 2: a more flexible PSBT format; created by default by Bitcoin Core's PSBT RPCs from v32.
✓ Bitcoin Core: as of v32.0.
BIP 371
Taproot Fields for PSBT
Taproot fields for PSBT, so hardware and multisig wallets can sign Taproot.
✓ Bitcoin Core: as of v24.0.
BIP 373
MuSig2 PSBT Fields
MuSig2 fields for PSBT.
✓ Bitcoin Core: as of v30.0
BIP 125
Opt-in Full Replace-by-Fee Signaling
Opt-in Replace-by-Fee: a transaction can signal that it may be replaced by a higher-fee version, making fee bumping routine.
✓ Repo status: Deployed
BIP 322
Generic Signed Message Format
Generic signed messages that work for every address type, not just legacy ones.
✓ Repo status: Complete
BIP 78
A Simple Payjoin Proposal
Payjoin (P2EP): the receiver adds an input to the sender's payment, breaking the common-input-ownership heuristic used by chain analysis.
✓ Repo status: Deployed
BIP 431
Topology Restrictions for Pinning
TRUC (v3) transactions: a topology rule that makes Lightning fee bumping resistant to pinning (Bitcoin Core v28).
✓ Bitcoin Core: as of v28.0.
BIP 433
Pay to Anchor (P2A)
Pay to Anchor (P2A): a keyless anchor output anyone can use to bump fees via CPFP (Bitcoin Core v28).
✓ Bitcoin Core: as of v28.0.

Peer-to-peer network

BIP 152
Compact Block Relay
Compact blocks: send a block as short transaction IDs because peers already have most transactions. Blocks propagate far faster.
✓ Bitcoin Core: as of v0.13.0.
BIP 157
Client Side Block Filtering
Client-side block filtering protocol (Neutrino) — light clients download filters and check locally, without telling servers their addresses.
✓ Bitcoin Core: as of v0.19.0
BIP 158
Compact Block Filters for Light Clients
The compact block filter format used by BIP 157 light clients.
✓ Bitcoin Core: as of v0.19.0
BIP 324
Version 2 P2P Encrypted Transport Protocol
Encrypted P2P transport (v2): node-to-node traffic is encrypted and harder to fingerprint. On by default since Bitcoin Core v27.
✓ Bitcoin Core: as of v26.0
BIP 339
WTXID-based transaction relay
Relay transactions by wtxid (including the witness), fixing a class of relay problems after SegWit.
✓ Bitcoin Core: as of v0.21.0.
BIP 155
addrv2 message
addrv2: lets nodes gossip Tor v3, I2P and CJDNS addresses.
✓ Bitcoin Core: as of v0.21.0.
BIP 159
NODE_NETWORK_LIMITED service bit
NODE_NETWORK_LIMITED: pruned nodes can still serve recent blocks.
✓ Bitcoin Core: as of v0.16.0
BIP 130
sendheaders message
Add a new message, "sendheaders", which indicates that a node prefers to receive new block announcements via a "headers" message rather than an "inv".
✓ Bitcoin Core: as of v0.12.0.
BIP 133
feefilter message
Add a new message, "feefilter", which serves to instruct peers not to send "inv"'s to the node for transactions with fees below the specified fee rate.
✓ Bitcoin Core: as of v0.13.0.
BIP 37
Connection Bloom filtering
Bloom filters for light wallets: a phone wallet asks a node only for transactions matching a filter. Disabled by default in Bitcoin Core since v0.19.
✓ Bitcoin Core: since v0.8.0.
BIP 111
NODE_BLOOM service bit
The NODE_BLOOM service bit, so nodes could advertise (or stop offering) bloom filter service.
✓ Bitcoin Core: as of v0.13.0.
BIP 434
Peer Feature Negotiation
Peer feature negotiation for the P2P protocol (Bitcoin Core v32).
✓ Bitcoin Core: as of v32.0.
04

The Drama Hall

#

20 fights that defined how Bitcoin changes — each with what was proposed, both sides in their own terms, why it escalated and how it ended. Quotes are verbatim from the linked mailing-list posts, GitHub threads, X posts, forum threads and news reports; everything else is summarised from the cited sources.

2011–2012 · BIP 12 BIP 16 BIP 17 BIP 18

The P2SH War

Activated#
What it proposed

A way to pay to a script hash so senders need not know a multisig's full script. Three rival designs: OP_EVAL (BIP 12), P2SH (BIP 16) and OP_CHECKHASHVERIFY (BIP 17), plus BIP 18.

BIP 16 · Gavin Andresen

Evaluate a serialized script whose hash the output commits to. Miners vote by writing “/P2SH/” into the coinbase; 550 of about 1,000 blocks (≈55%) triggers it.

VS

BIP 17 · Luke Dashjr

A new opcode, OP_CHECKHASHVERIFY, instead of special-casing a script pattern. Miners vote with “p2sh/CHV”; needs at least 60%.

Why it blew up

Competing code, competing coinbase votes and competing thresholds for the same feature — an early template for every activation fight that followed. OP_EVAL (BIP 12) had already been replaced over complexity concerns.

Outcome

BIP 16 shipped in Bitcoin Core v0.6.0 and took effect on 1 April 2012. BIP 17 is Closed. P2SH's “3…” addresses (BIP 13) became the standard for multisig.

In the Bitcoin Takeover Wiki
“The Motivation for this BIP (and BIP 13, the pay-to-script-hash address type) is somewhat controversial; several people feel that it is unnecessary, and complex/multisignature transaction types should be supported by simply giving the sender the complete {serialized script}.”
— BIP 16 text, BIP 16 · source
Full dossier: timeline & 4 quotes →
2012–2019 · BIP 37 BIP 157

Bloom filters (BIP 37) switched off by default

Shipped#
What it proposed

BIP 37 (2012) let light wallets ask full nodes for matching transactions using bloom filters. In 2019 Matt Corallo proposed turning that service off by default in Bitcoin Core.

Switch it off · Matt Corallo and most reviewers

BIP 37 filtering is a known denial-of-service target and leaks privacy. Older nodes would keep serving it for years, and newer wallets were expected to move on.

VS

Light-wallet users and developers

Bloom filters were how light wallets worked without trusting a central server. Nicolas Dorier wanted them kept at least for peers you whitelist on your own node.

Why it blew up

It decided whether ordinary nodes keep serving phone wallets, which pitted node resources against light-client independence. One commenter called it sabotage.

Outcome

Merged for Bitcoin Core 0.19.0: peerbloomfilters now defaults to false, but operators can switch it back on. In the thread, compact block filters (BIP 157) were raised as the alternative.

In the Bitcoin Takeover Wiki
“BIP 37 bloom filters have been well-known to be a significant DoS target for some time.”
— Matt Corallo, GitHub, PR #16152 · source
Full dossier: timeline & 4 quotes →
2013–2020 · BIP 70

BIP 70 and the BitPay payment-protocol fight

Removed#
What it proposed

BIP 70 (2013) replaced copying an address with a payment request fetched from the merchant’s server and authenticated with X.509 certificates.

BitPay

From late 2017 it required the Payment Protocol on its invoices, saying wallets that matter already supported it.

VS

Samourai, Bitcoin Core contributors and many users

BIP 70 adds certificate and network attack surface and depends on the merchant’s server. Mandating it locked out wallets that can only pay an address.

Why it blew up

A dominant payment processor made an optional standard mandatory, so people whose wallets lacked it could no longer pay BitPay invoices.

Outcome

Bitcoin Core disabled BIP 70 by default in 0.19.0 and removed it entirely in 0.20.0. The BIP header still says Deployed because other software kept using it.

In the Bitcoin Takeover Wiki
“These true bitcoin wallets all already ‘speak’ Payment Protocol”
— BitPay, quoted by Bitcoin Magazine · source
Full dossier: timeline & 4 quotes →
2013–today · BIP 39

Seed words: the standard Core never adopted

Standoff#
What it proposed

BIP 39 turns a wallet’s secret into a list of 12 to 24 words from a fixed wordlist, with a built-in checksum, and stretches the words into a seed with PBKDF2.

Most hardware and mobile wallets

BIP 39, written by Marek Palatinus, Pavol Rusnak, Aaron Voisine and Sean Bowe, became the common backup format. Its header says Deployed.

VS

Electrum and Bitcoin Core contributors

The checksum depends on the wordlist and there is no version number, so a seed doesn’t say how to derive its wallet. Electrum refuses to generate BIP 39 seeds and Bitcoin Core never implemented them.

Why it blew up

Bitcoin’s most widely used backup format was rejected by the reference implementation and by one of the oldest wallets, so people moving seeds between wallets still run into incompatible formats.

Outcome

Still a standoff. BIP 39 is Deployed across the ecosystem, Electrum keeps its own Seed Version System, and Bitcoin Core has no BIP 39 support.

“BIP39 still requires the wordlist in order to compute its checksum, which is plainly inconsistent”
— Electrum documentation, electrum.readthedocs.io · source
Full dossier: timeline & 3 quotes →
2014–2017 · BIP 62

Malleability, Mt. Gox and BIP 62

Superseded#
What it proposed

BIP 62 (2014) listed the ways a third party could change a transaction’s ID without invalidating its signature, and proposed rules to close them one by one.

Mt. Gox

Blamed a long-known Bitcoin “design issue”, suspended bitcoin withdrawals, and said it would allow them again once a fix was “approved and standardized”.

VS

Bitcoin developers

Malleability was known and wallets and exchanges could handle it in their own software. Their 11 February alert said emergency protocol fixes were not required.

Why it blew up

The largest exchange of the day blamed the protocol for its frozen withdrawals, which turned a known quirk into a public fight over who was responsible.

Outcome

BIP 62 never activated and is now Closed. Segregated Witness (BIP 141, active August 2017) moved signatures out of the transaction ID, and BIP 141 calls this approach superior to BIP 62’s canonical-signature rules.

In the Bitcoin Takeover Wiki
“Bitcoin transactions are subject to a design issue that has been largely ignored, while known to at least a part of the Bitcoin core developers and mentioned on the BitcoinTalk forums.”
— Mt. Gox, statement posted on Bitcointalk · source
Full dossier: timeline & 3 quotes →
Rejected#
What it proposed

Raise the 1 MB block size limit by hard fork: 8 MB doubling every two years (BIP 101), 2 MB (BIP 102, BIP 109), miner-voted sizes (BIP 100) and growth formulas (BIPs 103–107).

Big blocks · Andresen, Hearn, Garzik, Classic, Unlimited

On-chain payments must stay cheap; raise the limit now. Shipped in Bitcoin XT (BIP 101) and Bitcoin Classic (BIP 109).

VS

Small blocks · SegWit first

Bigger blocks centralise validation; add capacity with SegWit and second layers such as Lightning, without a hard fork.

Why it blew up

Two years of client wars, roundtables and agreements over who decides Bitcoin's rules: developers, miners, businesses or users. BIP 101's 75% trigger was never reached.

Outcome

None of the hard-fork BIPs activated; every one is Closed. Bitcoin Cash split on 1 August 2017 to raise the limit on its own chain.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
“It can start being in versions way ahead, so by the time it reaches that block number and goes into effect, the older versions that don't have it are already obsolete.”
— Satoshi Nakamoto, Bitcointalk · source
Full dossier: timeline & 9 quotes →
2015–2024 · BIP 125

Replace-by-fee: opt-in, then full

Shipped#
What it proposed

Let an unconfirmed transaction be replaced by a version that pays a higher fee. BIP 125 (2015) made this opt-in: a transaction signals that it may be replaced. “Full-RBF” drops the signal, so any unconfirmed transaction can be replaced.

Full-RBF camp · Peter Todd and many Core contributors

Miners can always take the higher-fee version, so “first-seen” was never a real guarantee. Reliable replacement helps fee bumping and multi-party protocols, and accepting unconfirmed payments as final had long been discouraged.

VS

Zero-conf services · e.g. Muun, and Mike Hearn in 2015

Businesses that accept unconfirmed payments relied on first-seen relay. Full-RBF turns a miner-only attack into one anyone can run from a wallet, so these services had to switch off instant payments.

Why it blew up

It set a promise many merchants relied on (an unconfirmed payment usually sticks) against the incentive argument that miners will take the higher fee. When Bitcoin Core 24.0 shipped a mempoolfullrbf option in 2022, there were calls to pull it before release.

Outcome

Opt-in RBF (BIP 125) was merged in November 2015 (PR #6871). Bitcoin Core 24.0 added mempoolfullrbf, off by default, and a pull request to disable it on mainnet (#26287) was closed. By March 2024 Peter Todd estimated 95%+ of hash power ran full-RBF, and Bitcoin Core 28.0 turned it on by default (mempoolfullrbf=1).

In the Bitcoin Takeover Wiki
“This article lays out the case against RBF-SE and argues it is harmful to Bitcoin.”
— Mike Hearn, bitcoin-dev (quoted in the reply) · source
Full dossier: timeline & 7 quotes →

SegWit, the UASF and SegWit2x

Activated#
What it proposed

Segregated Witness as a soft fork via BIP 9 (95% of miners), then — when miners stalled — a user-activated deadline (BIP 148) and a miner-side bridge (BIP 91).

SegWit + UASF · Core developers, Shaolin Fry, many node runners

Fix malleability and add capacity by soft fork. If miners won't signal, reject their blocks from 1 August 2017 (BIP 148).

VS

Miners and the New York Agreement

Withhold signalling as leverage; activate SegWit only as part of “SegWit2x”, with a 2 MB hard fork about 90 days later.

Why it blew up

It put the question “who activates soft forks?” to a live test, with a chain-split threat from users (BIP 148) and a hard-fork threat from businesses and miners (SegWit2x).

Outcome

BIP 91 locked in on 21 July and activated on 26 July 2017; SegWit locked in at block 479,808 (9 Aug) and activated at block 481,824 (24 Aug 2017). Bitcoin Cash split on 1 August. The 2 MB half (SegWit2x) was suspended on 8 November 2017.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
“As such, soft forks rules are actually always enforced by the nodes, not the miners.”
— shaolinfry, bitcoin-dev · source
Full dossier: timeline & 5 quotes →
2016–2026 · BIP 2 BIP 3

Who runs the BIPs repo? Editors and BIP 3

Resolved#
What it proposed

BIP 2 (2016) set the BIP process and made BIP editors responsible for assigning numbers and merging. By early 2024 the repository had a months-long backlog, and BIP 3 later rewrote the process.

Add editors

Ava Chow proposed new editors with the same permissions as Luke Dashjr to clear the backlog and answer authors in a timely manner.

VS

Not that list

The nominations became a weeks-long argument over who should hold the merge button. Matt Corallo backed only some candidates and objected to the rest.

Why it blew up

The editor role decides whether a proposal gets a number and a merge. With one active editor and more than a hundred open pull requests, proposals were left waiting for answers.

Outcome

In April 2024 five new editors were added: Bryan “Kanzure” Bishop, Jon Atack, Mark “Murch” Erhardt, Olaoluwa “Roasbeef” Osuntokun and Ruben Somsen. BIP 3 reached rough consensus and was deployed in January 2026, replacing BIP 2 and cutting nine statuses down to four.

In the Bitcoin Takeover Wiki
“There's 133 pull requests open in the #Bitcoin Improvement Proposal repository, going back several months.😵”
— Luke Dashjr, X · source
Full dossier: timeline & 3 quotes →
2017–2026 · BIP 300 BIP 301

Drivechains

Chain split#
What it proposed

Sidechains secured by Bitcoin miners: hashrate escrows for the peg (BIP 300) and blind merged mining (BIP 301), by Paul Sztorc and CryptAxe.

For · Paul Sztorc, LayerTwo Labs

Let users opt into new features on sidechains without changing Bitcoin itself; miners earn more fees.

VS

Against · critics including Peter Todd's 2023 analysis

Puts miners in charge of sidechain funds and changes their incentives in ways critics consider unsafe for Bitcoin.

Why it blew up

A decade-long argument about whether Bitcoin should host sidechains at the consensus level, waged on podcasts as much as on mailing lists.

Outcome

Both BIPs remain Draft and never activated on Bitcoin. Sztorc's eCash (ECX), a 2026 hard fork of Bitcoin (block 973,728), was built to activate them natively.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
“It's unclear to me what the incentive is for miners to do any of this.”
— Peter Todd, bitcoin-dev · source
Full dossier: timeline & 3 quotes →
Unresolved#
What it proposed

A dozen ways to give Bitcoin script more introspection: APO (118), OP_VAULT (345), TXHASH (346), OP_CAT (347), CSFS (348), INTERNALKEY (349), PAIRCOMMIT (442), CCV (443), TEMPLATEHASH (446) and the BIP 448 bundle.

Minimal bundles

LNHANCE (CTV + CSFS + INTERNALKEY + PAIRCOMMIT) or BIP 448 (TEMPLATEHASH + CSFS + INTERNALKEY): small, analysable opcodes aimed at Lightning, Ark, vaults and DLCs.

VS

General or not at all

OP_CAT and script restoration for maximum flexibility — or no covenants, for fear of complexity and recursive covenants.

Why it blew up

Competing packages target overlapping use cases, and reviewers have not converged on one. Every new proposal splits review attention further.

Outcome

Nothing activated on mainnet. On Bitcoin Inquisition signet: APO and CTV since 2022-09-06, OP_CAT since 2024-04-30, CSFS and INTERNALKEY since 2025-10-06, TEMPLATEHASH since about 2026-07-26. OP_CAT is Complete (1 Mar 2026); OP_VAULT is Closed.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
“When spitballing about ways to do cool stuff with Bitcoin Script, I'd say about 90% of the time it ends with "we could do this if only we had CAT".”
— Andrew Poelstra, bitcoin-dev · source
Full dossier: timeline & 3 quotes →
2017–2018 · BIP 141

Covert ASICBoost and SegWit

Resolved#
What it proposed

In April 2017 Gregory Maxwell proposed a soft fork (never given a BIP number) to block the covert form of ASICBoost, a mining shortcut he said was built into a major manufacturer’s chips and that SegWit would interfere with.

Gregory Maxwell

Covert ASICBoost gave its user a hidden edge worth up to $100 million a year and a reason to block protocol upgrades such as SegWit.

VS

Bitmain

It said it had tested ASICBoost on testnet but never used it on mainnet, demanded proof, and called Maxwell’s maths incorrect.

Why it blew up

It tied the SegWit standoff to a patent-protected mining edge, which made a technical fight look like a commercial one.

Outcome

Maxwell’s soft fork was not deployed. SegWit activated in August 2017. Overt ASICBoost (version rolling) later shipped in miner firmware, and in 2018 AntPool was reported to have mined a block with it.

In the Bitcoin Takeover Wiki
“Reverse engineering of a particular mining chip has demonstrated conclusively that ASICBOOST has been implemented in hardware.”
— Gregory Maxwell, bitcoin-dev · source
Full dossier: timeline & 4 quotes →
2019–2026 · BIP 54 BIP 53

Consensus Cleanup and the 64-byte question

Unresolved#
What it proposed

Fix four old bugs in one soft fork (BIP 54): the timewarp attack, slow-to-validate blocks, 64-byte transaction Merkle weaknesses and duplicate coinbases.

For · authors Antoine Poinsot and Matt Corallo

Close real attack vectors — a timewarp attacker could drop difficulty to its minimum within 38 days — with minimal side effects.

VS

Objections

Banning exactly-64-byte transactions remains the most contested rule; others argued the timewarp fix closes off designs like forward blocks or a soft-fork fix for 2106.

Why it blew up

Low drama by Bitcoin standards, but it is the test of whether Bitcoin can still ship any soft fork at all.

Outcome

Complete since 22 May 2026. Active on Inquisition signet since block 291,168 (12 Feb 2026); Core PR #35793 under review, regtest only. Antoine Riard, for himself, suggested activation could be considered in the second half of 2027.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
“i believe it's more important to fix the timewarp bug than people usually think;”
— Antoine Poinsot, bitcoin-dev · source
Full dossier: timeline & 4 quotes →

Taproot: LOT=true vs Speedy Trial

Activated#
What it proposed

Activate Taproot (BIPs 340–342), which almost nobody opposed — but argue fiercely about how: BIP 8 with lockinontimeout=true, or a miner vote that could simply fail.

LOT=true · BIP 8, BIP 343 client

Make signalling mandatory at the end so miners cannot veto an upgrade users want (the lesson many drew from 2017).

VS

LOT=false / Speedy Trial · Bitcoin Core

Never force a chain split: give miners a short, 90% window and try again later if it fails.

Why it blew up

Taproot itself was uncontroversial; the activation method became a proxy fight over the lessons of the UASF.

Outcome

Bitcoin Core 0.21.1 shipped Speedy Trial (bit 2, 90%). Taproot locked in at block 687,285 (12 Jun 2021) and activated at block 709,632 (14 Nov 2021). BIP 343 was Closed on 1 June 2026, “no longer relevant”.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
  • S15 E50: Vlad on the Speedy Trial backlash▶ listen at 38:53timestamp transcript-derived, pending a listen
  • S15 E50: Murch on Taproot and inscriptions▶ listen at 53:56timestamp transcript-derived, pending a listen
  • S15 E50: Murch on “Taproot caused ordinals”▶ listen at 54:45timestamp transcript-derived, pending a listen
“As we saw in 2017 with BIP 9, coordinating activation by miner signal alone, despite its potential benefits, also leaves open the door to a miner veto.”
— Luke Dashjr, bitcoin-dev · source
Full dossier: timeline & 4 quotes →
2020–2026 · BIP 119

CTV: the covenant that keeps knocking

Unresolved#
What it proposed

OP_CHECKTEMPLATEVERIFY (BIP 119, Jeremy Rubin): an output can commit to the exact transaction that spends it — vaults, congestion control, channel factories, cheaper DLCs.

For · Rubin, the 2025 open-letter signers, the 2026 activation client

Simple, non-recursive, well-understood and reviewed for years. Activate it, or say clearly why not.

VS

Sceptics

Not flexible or generic enough, little real experimentation (Optech's summary of criticisms); worries that activation is being pushed without broad consensus.

Why it blew up

Three activation pushes: a 2022 Speedy Trial proposal, a July 2025 open letter signed by 66 people, and a 2026 activation client signalling on bit 5 (90%, 30 Mar 2026 – 30 Mar 2027, min height 1,001,952).

Outcome

Still Draft. In difficulty period 484 the signalling monitor counted 0 of 920 blocks (0.00%) on 20 Nov 2026. Its successor-style rival BIP 446 (TEMPLATEHASH) arrived in 2026.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
“I still do not know exactly what happened and why.”
— Jeremy Rubin, bitcoin-dev · source
Full dossier: timeline & 5 quotes →
2023–2026 · BIP 110

OP_RETURN, inscriptions and BIP-110

Chain split#
What it proposed

After the Ordinals wave and Bitcoin Core 30.0 lifting its default OP_RETURN limit, BIP-110 proposed a one-year soft fork to “Temporarily limit the size of data fields at the consensus level”.

Bitcoin Core (relay policy)

“This is not endorsing or condoning non-financial data usage, but accepting that as a censorship-resistant system, Bitcoin can and will be used for use cases not everyone agrees on.”

VS

Bitcoin Knots / BIP-110

Arbitrary data distorts incentives; restrict it at the consensus level with a 55% threshold and mandatory signalling.

Why it blew up

The first fork fight since 2017 about what goes in blocks rather than how big they are — and the first to end in an actual split of nodes enforcing a soft fork.

Outcome

BIP-110 nodes split off at block 961,632 on 8 August 2026. The minority SHA-256d chain made eight blocks in 22 days and became Bitcoin BLAKE2b. BIP-110 was marked Closed on 9 August 2026 “following a chain split with stalled mining”.

In the Bitcoin Takeover Wiki
Heard on Bitcoin Takeover
“Since the restrictions on the usage of OP_RETURN outputs encourage harmful practices while being ineffective in deterring unwanted usage, i propose to drop them.”
— Antoine Poinsot, bitcoin-dev · source
Full dossier: timeline & 6 quotes →
2023–2026 ·

Ordinals: the BIP that never got a number

Refused#
What it proposed

Casey Rodarmor’s “Ordinal Numbers” pull request (#1408, January 2023) asked for a BIP number for a scheme that gives every satoshi a serial number.

Casey Rodarmor and supporters

A BIP documents a standard people use; it is not an endorsement, so being controversial is no reason to refuse a number.

VS

Opponents, incl. Luke Dashjr

Numbering sats harms fungibility and encourages spam. The standard should live in its own repository, like Lightning’s BOLTs or SatoshiLabs’ SLIPs.

Why it blew up

It turned the BIP editors’ merge button into a vote on inscriptions, and the pull request sat open for more than three years.

Outcome

On 4 March 2026 BIP editor Kanzure rejected the pull request, declined to assign a number and closed it.

In the Bitcoin Takeover Wiki
“An accepted BIP does not indicate endorsement by the BIP repo maintainers, Bitcoin Core, or the larger Bitcoin community.”
— Casey Rodarmor, GitHub, PR #1408 · source
Full dossier: timeline & 6 quotes →
2024–2026 · BIP 360 BIP 361

Quantum: migrate, sunset or wait?

Unresolved#
What it proposed

Prepare Bitcoin for quantum computers: a new output type without a quantum-exposed key path (BIP 360, P2MR) and a phased sunset of legacy signatures (BIP 361).

Act early · BIP 361 (Lopp et al.)

Phase A stops payments to quantum-vulnerable addresses; Phase B restricts ECDSA/Schnorr spending, with a rescue protocol, to prevent mass theft.

VS

No freeze · QSAVE and others

Never burn or freeze coins: QSAVE's drafts add a second spending factor with “no sunset”; Wuille argues no proposed output type is categorically quantum-secure.

Why it blew up

It touches the most sensitive question in Bitcoin — whether anyone's coins can ever be made unspendable — on a timeline nobody can predict.

Outcome

All Draft; no activation mechanism. 2026 brought SHRINCS, QSAVE drafts and a steady stream of PQ output-type debate on Delving Bitcoin.

In the Bitcoin Takeover Wiki
“It turns quantum security into a private incentive: fail to upgrade and you will certainly lose access to your funds”
— Jameson Lopp, bitcoin-dev · source
Full dossier: timeline & 4 quotes →
2024 · BIP 94

Testnet3 block storms and the testnet4 reset

Resolved#
What it proposed

BIP 94 starts a new test network, testnet4, that fixes the difficulty-reset rule testnet3 abused to produce “block storms”.

Reset now · Jameson Lopp

Testnet3’s difficulty bug and tiny block reward had broken it, and test coins were being bought and sold. Lopp then mined a storm of blocks to force the issue.

VS

Developers using testnet3

Attacking a shared test network mainly wasted builders’ time. Francis Pouliot likened it to fouling a jacuzzi to make people move spas.

Why it blew up

A well-known developer deliberately disrupted a public test network to win an argument, and some application builders had to halt their testing.

Outcome

Bitcoin Core 28.0 added testnet4 as specified in BIP 94, which is now Deployed.

In the Bitcoin Takeover Wiki
“TBTC is being actively bought and sold; one could argue that the fundamental principle of testnet coins having no value has been broken.”
— Jameson Lopp, bitcoindev mailing list · source
Full dossier: timeline & 3 quotes →
2025–today · BIP 177

BIP 177: call a satoshi a bitcoin

Unresolved#
What it proposed

An informational BIP that redefines “1 bitcoin” as today’s smallest unit, so what used to be 1 BTC becomes 100 million bitcoins and amounts are shown as whole numbers.

John Carvalho, backed by Jack Dorsey

Decimals confuse newcomers, and calling the smallest unit a bitcoin matches how the protocol actually counts.

VS

Sats-standard defenders

“21 million” is Bitcoin’s best-known fact. Turning it into 2.1 quadrillion would confuse people and blunt the scarcity message, and “sats” already works.

Why it blew up

It changes no code but does change the most-quoted number in Bitcoin, so everyone had an opinion.

Outcome

Assigned on 23 April 2025 and merged as a Draft. It is still a Draft, with no sign of consensus.

“BIP 177 is a sincere effort to prevent misunderstanding Bitcoin, and how it works, to ultimately empower users,”
— John Carvalho, quoted by Decrypt · source
Full dossier: timeline & 4 quotes →
05

What’s coming next

#

The soft-fork pipeline as of 2026-11-20. 24 consensus soft-fork BIPs are open (Draft or Complete); none has activation parameters in a Bitcoin Core release.

No probabilities here. Nobody can honestly put a percentage on a Bitcoin soft fork. Tiers reflect only the evidence listed on each card — BIP status, signet deployment, implementation review and public statements — read on 2026-11-20.
TIER 1

Closest to the finish line

Specification complete, implementation in review, broad support — but no activation parameters yet.

Consensus Cleanup

Unlocks: Removes the timewarp attack, caps worst-case validation time, kills the 64-byte transaction Merkle trick and duplicate coinbases.

Evidence
  • BIP status Complete (1.0.0, 22 May 2026)
  • Active on Bitcoin Inquisition signet since block 291,168 (12 Feb 2026)
  • Core PR #35793 under review (regtest only)
  • Testnet5 (BIP 95) activates it from block 1

Blockers: The 64-byte transaction rule is still the most contested; no activation method chosen. Riard (personal view): consider activation in H2 2027.

Sources · 7BIP 54, “Consensus Cleanup”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Optech Newsletter #430, 6 Nov 2026 — “Continued discussion of BIP54”, QSAVE, opt-in replay protection · Antoine Riard, “Getting BIP54 past the finish line”, Bitcoin-Dev mailing list, Nov 2026 (archive) · Delving Bitcoin, “Bitcoin Inquisition 29.4” (signet activation heights for APO, CTV, OP_CAT, CSFS, IKEY, BIP54, TEMPLATEHASH) · Bitcoin Core PR #35793 — BIP54 implementation (regtest only, no mainnet activation) · BIP 95, “Testnet 5”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Optech topic, “Consensus cleanup soft fork” (also covering BIP54)
TIER 2

Active debate

Working code and serious backers, but rival designs compete for the same soft-fork slot.

BIP 448 bundle: TEMPLATEHASH + CSFS + INTERNALKEY

Unlocks: Rebindable signatures and next-transaction commitments in Tapscript: LN-Symmetry, non-interactive Ark receives, simpler vaults and DLCs.

Evidence
  • All Draft
  • TEMPLATEHASH active on Inquisition signet since ~26 Jul 2026; CSFS and INTERNALKEY since 6 Oct 2025
  • A BIP448 GitHub organisation collects implementations, LN-Symmetry BOLT drafts and an Ark demo (Optech, Sep 2026)
  • Robin Linus on Bitcoin Takeover S17 E48: “We're going to get BIP 448, TEMPLATEHASH”

Blockers: BIP 448 says activation is “left to be determined at a later date”; competes with LNHANCE/CTV.

Sources · 5BIP 448, “Taproot-native (Re)bindable Transactions”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 446, “OP_TEMPLATEHASH”, bitcoin/bips (commit a7f9132, 2026-11-17) · Delving Bitcoin, “Bitcoin Inquisition 29.4” (signet activation heights for APO, CTV, OP_CAT, CSFS, IKEY, BIP54, TEMPLATEHASH) · Bitcoin Optech Newsletter, 4 Sep 2026 — “BIP448 and CSFS/CTV demos and applications” · S17 E48: Robin Linus — “We're going to get BIP 448, TEMPLATEHASH”

CTV (and LNHANCE)

Unlocks: Vaults, congestion control, channel factories; with CSFS, LN-Symmetry-style channels.

Evidence
  • BIP 119 is Draft
  • Activation client signalling bit 5 since 30 Mar 2026; timeout 30 Mar 2027; 90%; min height 1,001,952
  • 0 of 920 blocks signalling in period 484 (20 Nov 2026)
  • LNHANCE proposed as a package in Dec 2025

Blockers: Essentially no miner signalling; no Bitcoin Core release carries it; reviewers split between CTV- and TEMPLATEHASH-based bundles.

Sources · 5BIP 119, “CHECKTEMPLATEVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17) · Delving Bitcoin, “BIP 119 CTV activation client” (1440000bytes, 9 Feb 2026) · ctv-activation.github.io — deployment parameters and meeting logs · bip119monitor.com — BIP-119 signalling, period 484 (read 20 Nov 2026, 01:45 UK time: 0 of 920 blocks, 0.00%) · Bitcoin Optech Newsletter, 5 Dec 2025 — “LNHANCE soft fork”

OP_CAT

Unlocks: Concatenation in Tapscript; enables many covenant and verification constructions (including recursive ones).

Evidence
  • BIP status Complete (1 Mar 2026)
  • Active on Inquisition signet since block 193,536 (30 Apr 2024)

Blockers: No activation parameters; generality (recursive covenants) is exactly what sceptics fear.

Sources · 2BIP 347, “OP_CAT in Tapscript”, bitcoin/bips (commit a7f9132, 2026-11-17) · Delving Bitcoin, “Bitcoin Inquisition 29.4” (signet activation heights for APO, CTV, OP_CAT, CSFS, IKEY, BIP54, TEMPLATEHASH)
TIER 3

Research and early drafts

Promising or necessary, but years of design and review remain — or the community is split on whether to do it at all.

Quantum migration

Unlocks: A path off quantum-vulnerable signatures before a capable quantum computer exists.

Evidence
  • BIP 360 (P2MR) and BIP 361 (sunset) are Draft
  • 2026 Optech coverage: SHRINCS, QSAVE drafts, PQ output-type debate

Blockers: No agreement on whether to freeze vulnerable coins, which signature scheme, or when.

Sources · 5BIP 360, “Pay-to-Merkle-Root (P2MR)”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 361, “Post Quantum Migration and Legacy Signature Sunset”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Optech Newsletter, 24 Apr 2026 — BIPs #1895 publishes BIP361 · Bitcoin Optech Newsletter #430, 6 Nov 2026 — “Continued discussion of BIP54”, QSAVE, opt-in replay protection · Bitcoin Optech Newsletter #425, 2 Oct 2026 — PQC output types; comparing covenant vaults

Cross-input signature aggregation

Unlocks: Smaller multi-input transactions — cheaper coinjoins, payjoins and consolidations.

Evidence
  • Three drafts added in 2026
  • BIP 460 leaves activation unspecified

Blockers: New witness version needed; interacts with the quantum output-type debate.

Sources · 4BIP 458, “Half-Aggregation of BIP 340 Signatures”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 459, “DahLIAS fully aggregated signatures for secp256k1”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 460, “CISA for Taproot Key Path Spends in SegWit v2”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Optech Newsletter #430, 6 Nov 2026 — “Continued discussion of BIP54”, QSAVE, opt-in replay protection

Great Script Restoration

Unlocks: Re-enable opcodes disabled in 2010 (arithmetic, string ops) under a runtime budget.

Evidence
  • Both Draft (2026)
  • Varops benchmarking called for in Dec 2025

Blockers: Large surface area; needs extensive benchmarking and review.

Sources · 3BIP 440, “Varops Budget For Script Runtime Constraint”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 441, “Restoration of disabled script (Tapleaf 0xC2)”, bitcoin/bips (commit a7f9132, 2026-11-17) · Bitcoin Optech Newsletter, 5 Dec 2025 — “LNHANCE soft fork”

Other covenant designs

Unlocks: APO for LN-Symmetry; CCV (MATT) for vaults and fraud proofs; TXHASH as a general template opcode.

Evidence
  • All Draft
  • APO active on Inquisition signet since 2022

Blockers: Overlap with the 448/LNHANCE bundles.

Sources · 4BIP 118, “SIGHASH_ANYPREVOUT for Taproot Scripts”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 443, “OP_CHECKCONTRACTVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17) · BIP 346, “OP_TXHASH”, bitcoin/bips (commit a7f9132, 2026-11-17) · Delving Bitcoin, “Bitcoin Inquisition 29.4” (signet activation heights for APO, CTV, OP_CAT, CSFS, IKEY, BIP54, TEMPLATEHASH)
06

Explore all 218 BIPs

#

Search titles, authors and summaries. Filters combine and update the link, so any view is shareable. Click a row for a quick view; every BIP also has its own page.

218 of 218 BIPs
BIPTitle · what it doesLayerYearStatusAdoption
1BIP Purpose and Guidelines
The original rulebook for writing a BIP (2011), modelled on Python's PEPs. Replaced by BIP 2, then BIP 3.
Process / no layer2011Closed
2BIP process, revisedWho runs the BIPs repo? Editors and BIP 3
The 2016 rewrite of the BIP process that introduced statuses like Final, Rejected and Replaced. Superseded by BIP 3.
Process / no layer2016Closed
3Updated BIP ProcessWho runs the BIPs repo? Editors and BIP 3
The current BIP process (2025): just four statuses — Draft, Complete, Deployed, Closed — and the rule that a BIP number says nothing about whether an idea is good or…
Process / no layer2025DeployedDeployed (ecosystem)
8Version bits with lock-in by heightTaproot
An activation method where miner signalling can be made mandatory at the end (“lockinontimeout”). The engine behind the 2021 LOT=true debate.
Process / no layer2017CompleteComplete, awaiting adoption
9Version bits with timeout and delaySegWit, the UASF and SegWit2x
Version bits: miners flip a bit in the block header to signal readiness for an upgrade; several upgrades can be signalled at once. Used for CSV and SegWit, and a…
Process / no layer2015DeployedIn Bitcoin Core
10Multi-Sig Transaction Distribution
The enabling of multi-signature transactions in Bitcoin will introduce a great deal of extra functionality to the users of the network, but also a great deal of extra…
Applications2011Closed
11M-of-N Standard Transactions
Made M-of-N multisig outputs standard, so shared custody became possible on-chain.
Applications2011DeployedIn Bitcoin Core
12OP_EVALThe P2SH War
OP_EVAL, an opcode to run a script from the stack. Its own text records the objection that evaluating data as code adds complexity; P2SH (BIP 16) replaced it.
Consensus (soft fork)2011Closed
13Address Format for pay-to-script-hash
The “3…” address format for pay-to-script-hash. Every multisig and wrapped-SegWit address you have seen comes from here.
Applications2011DeployedIn Bitcoin Core
14Protocol Version and User Agent
Defined the user agent string nodes use to identify their software to peers.
Peer Services2011DeployedIn Bitcoin Core
15Aliases
Aliases.
Applications2011Closed
16Pay to Script HashThe P2SH War
Pay to Script Hash. The sender pays to a hash; the receiver reveals the full script when spending. Won the 2012 P2SH war against BIP 17.
Consensus (soft fork)2012DeployedActivated soft fork
17OP_CHECKHASHVERIFY (CHV)The P2SH War
OP_CHECKHASHVERIFY, Luke Dashjr's rival to P2SH. Lost the 2012 miner vote and is Closed.
Consensus (soft fork)2012Closed
18hashScriptCheckThe P2SH War
hashScriptCheck, a compromise variant of the P2SH idea from the same 2012 fight.
Consensus (soft fork)2012CompleteComplete, awaiting adoption
19M-of-N Standard Transactions (Low SigOp)
This BIP proposes M-of-N-signatures required transactions as a new 'standard' transaction type using the existing scripting system without significant modifications.
Applications2012Closed
20URI Scheme
This BIP proposes a URI scheme for making Bitcoin payments.
Applications2011Closed
21URI Scheme
The bitcoin: URI scheme behind every clickable or QR-code payment request.
Applications2012Closed
22getblocktemplate - Fundamentals
getblocktemplate: lets miners and pools build their own block templates instead of blindly trusting a pool server.
API/RPC2012DeployedIn Bitcoin Core
23getblocktemplate - Pooled Mining
This BIP describes extensions to the getblocktemplate JSON-RPC call to enhance pooled mining.
API/RPC2012DeployedIn Bitcoin Core
30Duplicate transactions
Banned new transactions that duplicate the txid of an earlier one with unspent outputs (two historic exceptions at blocks 91,842 and 91,880).
Consensus (soft fork)2012DeployedActivated soft fork
31Pong message
This document describes a trivial protocol extension that makes it easier for clients to detect dead peer connections.
Peer Services2012DeployedIn Bitcoin Core
32Hierarchical Deterministic Wallets
HD wallets: one master seed deterministically produces an entire tree of keys. Practically every modern wallet is built on this.
Applications2012DeployedIn Bitcoin Core
33Stratized Nodes
As the Bitcoin network scales, roles are fast becoming specialised. In the beginning, a single Bitcoin user would perform the synonymous roles of miner, merchant and…
Peer Services2012Closed
34Block v2, Height in Coinbase
Blocks must include their height in the coinbase; introduced the version-number supermajority upgrade method.
Consensus (soft fork)2012DeployedActivated soft fork
35mempool message
The mempool P2P message, letting a peer ask what unconfirmed transactions you have.
Peer Services2012DeployedIn Bitcoin Core
36Custom Services
This BIP adds new fields to the version message which clients can use to announce custom services without polluting the limited 64-bit services field. It also makes…
Peer Services2012Closed
37Connection Bloom filteringBloom filters (BIP 37) switched off by default
Bloom filters for light wallets: a phone wallet asks a node only for transactions matching a filter. Disabled by default in Bitcoin Core since v0.19.
Peer Services2012DeployedIn Bitcoin Core
38Passphrase-protected private key
Passphrase-encrypted private keys (the “6P…” paper-wallet format).
Applications2012DeployedDeployed (ecosystem)
39Mnemonic code for generating deterministic keysSeed words
The 12/24-word seed phrase. Probably the most widely used BIP for ordinary people, although Bitcoin Core itself never adopted it.
Applications2013DeployedDeployed (ecosystem)
42A finite monetary supply for Bitcoin
A tongue-in-cheek April 1st BIP with a real fix: without it, the block reward would have restarted far in the future.
Consensus (soft fork)2014DeployedIn Bitcoin Core
43Purpose Field for Deterministic Wallets
Reserved the first level of an HD wallet path for a “purpose” number, so 44/49/84/86 could coexist.
Applications2014DeployedIn Bitcoin Core
44Multi-Account Hierarchy for Deterministic Wallets
The m/44'/0'/0' account structure for HD wallets, used by most multi-coin hardware and software wallets.
Applications2014DeployedIn Bitcoin Core
45Structure for Deterministic P2SH Multisignature Wallets
This BIP defines a structure for hierarchical deterministic P2SH multi-party multi-signature wallets (HDPM wallets from now on) based on the algorithm described in…
Applications2014CompleteComplete, awaiting adoption
46Address Scheme for Timelocked Fidelity Bonds
This BIP defines the derivation scheme for HD wallets which create timelocked addresses used for creating fidelity bonds. It also gives advice to wallet developers on…
Applications2022Draft
47Reusable Payment Codes for Hierarchical Deterministic Wallets
Reusable payment codes (PayNyms): a static code you can publish without address reuse.
Applications2015DeployedDeployed (ecosystem)
48Multi-Script Hierarchy for Multi-Sig Wallets
This BIP defines a logical hierarchy for deterministic multi-sig wallets based on an algorithm described in BIP-0067 (BIP67 from now on), BIP-0032 (BIP32 from now on),…
Applications2020DeployedDeployed (ecosystem)
49Derivation scheme for P2WPKH-nested-in-P2SH based accounts
Derivation paths for wrapped SegWit (“3…” P2SH-P2WPKH) accounts.
Applications2016DeployedIn Bitcoin Core
50March 2013 Chain Fork Post-Mortem
The post-mortem of the March 2013 chain split between versions 0.7 and 0.8.
Process / no layer2013DeployedDeployed (ecosystem)
52Durable, Low Energy Bitcoin PoW
As Bitcoin gained utility and value over the preceding decade, the network incentivized the purchase of billions of dollars in mining equipment and electricity. With…
Consensus (hard fork)2021Closed
53Disallow 64-byte transactionsConsensus Cleanup and the 64-byte question
This BIP describes the rationale for disallowing transactions that are serialized to 64 bytes without the transaction's witness. We describe the weaknesses to the…
Consensus (soft fork)2025Draft
54Consensus CleanupConsensus Cleanup and the 64-byte question
Consensus Cleanup: fixes the timewarp bug, caps worst-case block validation time, bans 64-byte transactions and makes duplicate coinbases impossible. The front-runner…
Consensus (soft fork)2025CompleteComplete, awaiting adoption
60Fixed Length "version" Message (Relay-Transactions Field)
BIP 0037 introduced a new flag to version messages which says whether to relay new transaction messages to that node. The protocol version was upgraded to 70001, and…
Peer Services2013Closed
61Reject P2P message
The reject P2P message, telling a peer why its transaction or block was refused. Removed from Bitcoin Core in v0.20.
Peer Services2014DeployedIn Bitcoin Core
62Dealing with malleabilityMalleability, Mt. Gox and BIP 62
This document specifies proposed changes to the Bitcoin transaction validity rules in order to make malleability of transactions impossible (at least when the sender…
Consensus (soft fork)2014Closed
64getutxo message
This document describes a small P2P protocol extension that performs UTXO lookups given a set of outpoints.
Peer Services2014Closed
65OP_CHECKLOCKTIMEVERIFY
OP_CHECKLOCKTIMEVERIFY: lock coins until a date or block height.
Consensus (soft fork)2014DeployedActivated soft fork
66Strict DER signatures
Strict DER signature encoding, removing reliance on OpenSSL's parsing for consensus.
Consensus (soft fork)2015DeployedActivated soft fork
67Deterministic Pay-to-script-hash multi-signature addresses through public key sorting
This BIP describes a method to deterministically generate multi-signature pay-to-script-hash transaction scripts. It focuses on defining how the public keys must be…
Applications2015CompleteComplete, awaiting adoption
68Relative lock-time using consensus-enforced sequence numbers
Relative lock-time via the nSequence field: “not before N blocks after the coin confirmed”.
Consensus (soft fork)2015DeployedActivated soft fork
69Lexicographical Indexing of Transaction Inputs and Outputs
Currently there is no standard for bitcoin wallet clients when ordering transaction inputs and outputs. As a result, wallet clients often have a discernible blockchain…
Applications2015CompleteComplete, awaiting adoption
70Payment ProtocolBIP 70 and the BitPay payment-protocol fight
A payment protocol with signed invoices from the merchant. In the Bitcoin Core GUI from v0.9; disabled by default at build time since v0.19.
Applications2013DeployedIn Bitcoin Core
71Payment Protocol MIME types
This BIP defines a MIME (RFC 2046) Media Type for Bitcoin payment request messages.
Applications2013DeployedIn Bitcoin Core
72bitcoin: uri extensions for Payment Protocol
This BIP describes an extension to the bitcoin: URI scheme (BIP 21) to support the payment protocol (BIP 70).
Applications2013DeployedIn Bitcoin Core
73Use "Accept" header for response type negotiation with Payment Request URLs
This BIP describes an enhancement to the payment protocol (BIP 70) that addresses the need for short URLs when scanning from QR codes. It generalizes the specification…
Applications2013DeployedDeployed (ecosystem)
74Allow zero value OP_RETURN in Payment Protocol
This BIP alters the Payment Protocol to allow for zero value OP_RETURN outputs in serialized PaymentRequests.
Applications2016Closed
75Out of Band Address Exchange using Payment Protocol Encryption
This BIP is an extension to BIP 70 that provides two enhancements to the existing Payment Protocol. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",…
Applications2015DeployedDeployed (ecosystem)
77Async Payjoin
Async Payjoin: lets sender and receiver build a privacy-improving payjoin without both being online at once.
Applications2023Draft
78A Simple Payjoin Proposal
Payjoin (P2EP): the receiver adds an input to the sender's payment, breaking the common-input-ownership heuristic used by chain analysis.
Applications2019DeployedDeployed (ecosystem)
79Bustapay :: a practical coinjoin protocol
The way bitcoin transactions are normally created leaks more information than desirable, and as a result has been exploited by unreasonably effective blockchain…
Applications2018Closed
80Hierarchy for Non-Colored Voting Pool Deterministic Multisig Wallets
This BIP defines a logical hierarchy for non-colored voting pool deterministic multisig wallets based on an algorithm described in BIP-0032 (BIP32 from now on) and…
Process / no layer2014Closed
81Hierarchy for Colored Voting Pool Deterministic Multisig Wallets
This BIP defines a logical hierarchy for colored coin voting pool deterministic multisig wallets based on an algorithm described in BIP-0032 (BIP32 from now on) and…
Process / no layer2014Closed
83Dynamic Hierarchical Deterministic Key Trees
This BIP defines a scheme for key derivation that allows for dynamic creation of key hierarchies based on the algorithm described in BIP32.
Applications2015Closed
84Derivation scheme for P2WPKH based accounts
Derivation paths for native SegWit (bc1q…) single-sig wallets.
Applications2017DeployedIn Bitcoin Core
85Deterministic Entropy From BIP32 Keychains
Derive child seeds and passwords deterministically from one master key (BIP-85 “child seeds”).
Applications2020DeployedDeployed (ecosystem)
86Key Derivation for Single Key P2TR Outputs
Derivation paths for single-key Taproot (bc1p…) wallets.
Applications2021DeployedIn Bitcoin Core
87Hierarchy for Deterministic Multisig Wallets
This BIP defines a sane hierarchy for deterministic multisig wallets based on an algorithm described in BIP-0032 (BIP32 from now on), purpose scheme described in…
Applications2020CompleteComplete, awaiting adoption
88Hierarchical Deterministic Path Templates
This document describes a format for the representation of the templates that specify the constraints that can be imposed on BIP32 derivation paths. The constraints…
Applications2020CompleteComplete, awaiting adoption
89Chain Code Delegation
Chain Code Delegation (CCD) is a method for multi-signature wallets in which a privileged participant withholds BIP32 chain codes from one or more non-privileged…
Applications2025DeployedDeployed (ecosystem)
90Buried Deployments
Buried deployments: hard-codes the activation heights of BIPs 34, 65 and 66 instead of counting versions.
Process / no layer2016DeployedIn Bitcoin Core
91Reduced threshold Segwit MASFSegWit, the UASF and SegWit2x
SegSignal: an 80% miner-enforced rule that made all blocks signal SegWit in July 2017, defusing the BIP 148 deadline.
Consensus (soft fork)2017DeployedDeployed (ecosystem)
93codex32: Checksummed SSSS-aware BIP32 seeds
This document proposes a checksummed base32 format, "codex32", and a standard for backing up and restoring the master seed of a BIP-0032 hierarchical deterministic…
Applications2023Draft
94Testnet 4Testnet3 block storms and the testnet4 reset
Testnet4, the replacement for the broken testnet3 (Bitcoin Core v28).
Applications2024DeployedIn Bitcoin Core
95Testnet 5
Testnet5, the proposed replacement for testnet4, with BIP 54 rules active from block 1.
Applications2026DeployedDeployed (ecosystem)
98Fast Merkle Trees
In many applications it is useful to prove membership of a data element in a set without having to reveal the entire contents of that set. The Merkle hash-tree, where…
Consensus (soft fork)2017Draft
99Motivation and deployment of consensus rule changes ([soft/hard]forks)
This BIP attempts to create a taxonomy of the different types of consensus forks and proposes a deployment mechanism for each of them.
Process / no layer2015Closed
100Dynamic maximum block size by miner voteThe Block Size War
Jeff Garzik's miner-vote dynamic block size. Closed.
Consensus (hard fork)2015Closed
101Increase maximum block sizeThe Block Size War
Gavin Andresen's 8 MB blocks doubling every two years until 2036, shipped in Bitcoin XT. Closed after never reaching its 75% trigger.
Consensus (hard fork)2015Closed
102Block size increase to 2MBThe Block Size War
A simple one-time hard fork to 2 MB blocks. Closed.
Consensus (hard fork)2015Closed
103Block size following technological growthThe Block Size War
Pieter Wuille's slow-growth block size schedule (+17.7% per year). Closed.
Consensus (hard fork)2015Closed
104'Block75' - Max block size like difficultyThe Block Size War
Automatic adjustment of max block size with the target of keeping blocks 75% full, based on the average block size of the previous 2016 blocks. This would be done on…
Consensus (hard fork)2017Closed
105Consensus based block size retargeting algorithmThe Block Size War
A method of altering the maximum allowed block size of the Bitcoin protocol using a consensus based approach.
Consensus (hard fork)2015Closed
106Dynamically Controlled Bitcoin Block Size Max CapThe Block Size War
This BIP proposes replacing the fixed one megabyte maximum block size with a dynamically controlled maximum block size that may increase or decrease with difficulty…
Consensus (hard fork)2015Closed
107Dynamic limit on the block sizeThe Block Size War
This BIP proposes a dynamic limit to the block size based on transaction volume.
Consensus (hard fork)2015Closed
109Two million byte size limit with sigop and sighash limitsThe Block Size War
Bitcoin Classic's 2 MB hard fork with a sighash limit. Closed.
Consensus (hard fork)2016Closed
110Reduced Data Temporary SoftforkOP_RETURN, inscriptions and BIP-110
Reduced Data Temporary Softfork: one-year consensus limits on data in outputs, pushes and witnesses. Enforcing nodes split from Bitcoin on 8 Aug 2026; now Closed.
Consensus (soft fork)2025Closed
111NODE_BLOOM service bit
The NODE_BLOOM service bit, so nodes could advertise (or stop offering) bloom filter service.
Peer Services2015DeployedIn Bitcoin Core
112CHECKSEQUENCEVERIFY
OP_CHECKSEQUENCEVERIFY: scripts can enforce relative timelocks. A core ingredient of Lightning.
Consensus (soft fork)2015DeployedActivated soft fork
113Median time-past as endpoint for lock-time calculations
Lock times measured against median-time-past instead of a miner-chosen timestamp.
Consensus (soft fork)2015DeployedActivated soft fork
114Merkelized Abstract Syntax Tree
Merkelized Abstract Syntax Trees — an early design for hiding unused script branches, eventually realised in Taproot.
Consensus (soft fork)2016Closed
115Generic anti-replay protection using Script
This BIP describes a new opcode (OP_CHECKBLOCKATHEIGHT) for the Bitcoin scripting system that allows construction of transactions which are valid only on specific…
Consensus (soft fork)2016Closed
116MERKLEBRANCHVERIFY
A general approach to bitcoin contracts is to fully enumerate the possible spending conditions and then program verification of these conditions into a single script.…
Consensus (soft fork)2017Draft
117Tail Call Execution Semantics
BIP16 (Pay to Script Hash)[1] and BIP141 (Segregated Witness)[2] provide mechanisms by which script policy can be revealed at spend time as part of the execution…
Consensus (soft fork)2017Draft
118SIGHASH_ANYPREVOUT for Taproot ScriptsThe Covenant Zoo
SIGHASH_ANYPREVOUT (APO): signatures that can rebind to a different coin. Enables LN-Symmetry (eltoo). Still a draft.
Consensus (soft fork)2017Draft
119CHECKTEMPLATEVERIFYCTV
OP_CHECKTEMPLATEVERIFY (CTV): an output can commit to the exact transaction that must spend it. Vaults, congestion control and channel factories. Still a draft.
Consensus (soft fork)2020Draft
120Proof of Payment
This BIP describes a system called Proof of Payment, PoP. It is used to prove that a wallet has the credentials that were used to sign a previously generated…
Applications2015Closed
121Proof of Payment URI scheme
This is a proposal for a URI scheme to be used in the Proof of Payment process.
Applications2015Closed
122URI scheme for Blockchain references / exploration
This BIP proposes a URI scheme for looking up blocks, transactions and addresses on a Blockchain explorer, or in general to make proper Blockchain references.
Applications2015Draft
123BIP Classification
This document describes a classification scheme for BIPs. BIPs are classified by system layers with lower numbered layers involving more intricate interoperability…
Process / no layer2015DeployedDeployed (ecosystem)
124Hierarchical Deterministic Script Templates
This BIP defines a script template format that can be used by wallets to deterministically generate scripts with specific authorization policies using the key…
Applications2015Closed
125Opt-in Full Replace-by-Fee SignalingReplace-by-fee
Opt-in Replace-by-Fee: a transaction can signal that it may be replaced by a higher-fee version, making fee bumping routine.
Applications2015DeployedDeployed (ecosystem)
126Best Practices for Heterogeneous Input Script Transactions
When a Bitcoin transaction contains inputs that reference previous transaction outputs sent to different Bitcoin addresses, personally identifiable information of the…
Process / no layer2016Draft
127Simple Proof-of-Reserves Transactions
This BIP describes a simple way to construct proof-of-reserves transactions. This proposal formalizes a standard format for constructing such proofs, easing their…
Applications2019CompleteComplete, awaiting adoption
128Timelock-Recovery Storage Format
This document proposes a standard format for saving timelock-recovery plans, to allow different wallets to generate them, and different services to monitor/execute them.
Applications2026Draft
129Bitcoin Secure Multisig Setup (BSMS)
This document proposes a mechanism to set up multisig wallets securely.
Applications2020CompleteComplete, awaiting adoption
130sendheaders message
Add a new message, "sendheaders", which indicates that a node prefers to receive new block announcements via a "headers" message rather than an "inv".
Peer Services2015DeployedIn Bitcoin Core
131"Coalescing Transaction" Specification (wildcard inputs)
This specification defines a new type of transaction that supplements (not replaces) normal "non coalescing" bitcoin transactions.
Consensus (hard fork)2015Closed
132Committee-based BIP Acceptance Process
The current process for accepting a BIP is not clearly defined. While BIP-0001 defines the process for writing and submitting a Bitcoin Improvement Proposal to the…
Process / no layer2015Closed
133feefilter message
Add a new message, "feefilter", which serves to instruct peers not to send "inv"'s to the node for transactions with fees below the specified fee rate.
Peer Services2016DeployedIn Bitcoin Core
134Flexible Transactions
This BIP describes the next step in making Bitcoin's most basic element, the transaction, more flexible and easier to extend. At the same time this fixes all known…
Consensus (hard fork)2016Closed
135Generalized version bits voting
BIP9 introduced a mechanism for using the version bits to signal support for backwards-compatible changes (soft-forks) using a tally over the previous 2016 blocks…
Process / no layer2017Closed
136Bech32 Encoded Tx Position References
This document proposes a convenient, human usable encoding to refer to a confirmed transaction position within the Bitcoin blockchain--known as "TxRef". The primary…
Applications2017Draft
137Signatures of Messages using Private Keys
This document describes a signature format for signing messages with Bitcoin private keys. The specification is intended to describe the standard for signatures of…
Applications2019DeployedDeployed (ecosystem)
138Compact Encryption Scheme for Non-seed Wallet Data
This BIP defines a compact encryption scheme for output script descriptors (BIP-0380), wallet policies (BIP-0388), and other wallet metadata. The payload must not…
Applications2026Draft
139Wallet Metadata Export Format
This document specifies a format for exporting the metadata of a wallet: its accounts, descriptors, key information, signers, labels, transactions, coins, and…
Applications2026Draft
140Normalized TXID
This BIP describes the use of normalized transaction IDs (NTXIDs) in order to eliminate transaction malleability, both in the third-party modification scenario as well…
Consensus (soft fork)2015Closed
141Segregated Witness (Consensus layer)SegWit, the UASF and SegWit2x
Segregated Witness: moves signatures to a separate witness structure, fixes malleability, introduces block weight and versioned scripts.
Consensus (soft fork)2015DeployedActivated soft fork
142Address Format for Segregated Witness
This BIP describes new types of Bitcoin address to support native segregated witness transactions with 20-byte and 32-byte program.
Applications2015Closed
143Transaction Signature Verification for Version 0 Witness ProgramSegWit, the UASF and SegWit2x
A new signature hashing scheme for SegWit that fixes quadratic hashing and commits to input amounts (safer for hardware wallets).
Consensus (soft fork)2016DeployedActivated soft fork
144Segregated Witness (Peer Services)SegWit, the UASF and SegWit2x
How SegWit transactions and blocks are relayed between peers.
Peer Services2016DeployedIn Bitcoin Core
145getblocktemplate Updates for Segregated Witness
This BIP describes modifications to the getblocktemplate JSON-RPC call (BIP 22) to support segregated witness as defined by BIP 141.
API/RPC2016DeployedIn Bitcoin Core
146Dealing with signature encoding malleability
This document specifies proposed changes to the Bitcoin transaction validity rules to fix signature malleability related to ECDSA signature encoding.
Consensus (soft fork)2016Closed
147Dealing with dummy stack element malleabilitySegWit, the UASF and SegWit2x
Fixed the dummy-element malleability in OP_CHECKMULTISIG.
Consensus (soft fork)2016DeployedActivated soft fork
148Mandatory activation of segwit deploymentSegWit, the UASF and SegWit2x
UASF: from 1 Aug 2017, enforcing nodes would reject blocks not signalling SegWit. Users, not miners, set the deadline.
Consensus (soft fork)2017DeployedDeployed (ecosystem)
149Segregated Witness (second deployment)SegWit, the UASF and SegWit2x
A proposed second SegWit deployment with a user-activated fallback, made unnecessary when SegWit locked in.
Consensus (soft fork)2017Closed
150Peer Authentication
This BIP describes a way for peers to authenticate to other peers to guarantee node ownership and/or allow peers to access additional or limited node services, without…
Peer Services2016Closed
151Peer-to-Peer Communication Encryption
This BIP describes an alternative way that a peer can encrypt their communication between a selective subset of remote peers.
Peer Services2016Closed
152Compact Block Relay
Compact blocks: send a block as short transaction IDs because peers already have most transactions. Blocks propagate far faster.
Peer Services2016DeployedIn Bitcoin Core
154Rate Limiting via peer specified challenges
An anti-DoS system which provides additional service for peers which perform proof of work.
Peer Services2017Closed
155addrv2 message
addrv2: lets nodes gossip Tor v3, I2P and CJDNS addresses.
Peer Services2019DeployedIn Bitcoin Core
156Dandelion - Privacy Enhancing Routing
Dandelion: route a new transaction through a random path before broadcast to hide its origin. Closed; not in Bitcoin Core's implemented-BIPs list.
Peer Services2017Closed
157Client Side Block FilteringBloom filters (BIP 37) switched off by default
Client-side block filtering protocol (Neutrino) — light clients download filters and check locally, without telling servers their addresses.
Peer Services2017DeployedIn Bitcoin Core
158Compact Block Filters for Light Clients
The compact block filter format used by BIP 157 light clients.
Peer Services2017DeployedIn Bitcoin Core
159NODE_NETWORK_LIMITED service bit
NODE_NETWORK_LIMITED: pruned nodes can still serve recent blocks.
Peer Services2017DeployedIn Bitcoin Core
171Currency/exchange rate information API
A common interface for requesting currency exchange rate information from a server.
Applications2017Closed
172Define Bitcoin Subunits as Satoshis
This BIP proposes to formally define and standardize Bitcoin's smallest indivisible unit (1/100,000,000 of a bitcoin) as "satoshi" (singular) or "satoshis" (plural),…
Applications2025Draft
173Base32 address format for native v0-16 witness outputs
Bech32 — the bc1q… address format with strong error detection.
Applications2017DeployedIn Bitcoin Core
174Partially Signed Bitcoin Transaction Format
PSBT: a standard file format for passing an unsigned transaction between wallets, hardware signers and coordinators.
Applications2017DeployedIn Bitcoin Core
175Pay to Contract Protocol
Utilizing hierarchical deterministic wallets as described in BIP-0032 and the "Purpose Field" in BIP-0043, this document specifies the multiparty pay-to-contract key…
Applications2017Closed
176Bits Denomination
“Bits” (100 satoshis) as a display unit.
Process / no layer2017CompleteIn Bitcoin Core
177Redefine Bitcoin's Base UnitBIP 177
This BIP proposes redefining the commonly recognized "bitcoin" unit so that the base unit becomes the primary reference unit. Under this proposal, one bitcoin is…
Process / no layer2025Draft
178Version Extended WIF
An extension to the Wallet Import Format (WIF) to specify what kind of bitcoin address the private key corresponds to.
Applications2018Draft
179Name for payment recipient identifiers
This BIP proposes a new term for 'address'
Process / no layer2019CompleteComplete, awaiting adoption
180Block size/weight fraud proof
A fraud proof that enables light clients to detect oversized (or overweight) blocks.
Peer Services2017Closed
197Hashed Time-Locked Collateral Contract
This BIP describes a script for generalized debt agreement contract based on Hashed Time-Lock Contract (BIP 199) transactions according to the Atomic Loans…
Applications2019Draft
199Hashed Time-Locked Contract transactions
This BIP describes a script for generalized off-chain contract negotiation.
Applications2017Closed
300Hashrate Escrows (Consensus layer)Drivechains
Drivechain hashrate escrows: miners vote over months on sidechain withdrawals. Draft; never activated on Bitcoin.
Consensus (soft fork)2017Draft
301Blind Merged Mining (Consensus layer)Drivechains
Blind merged mining: sidechain blocks paid for by bids to Bitcoin miners, who need not run sidechain software. Draft.
Consensus (soft fork)2019Draft
310Stratum protocol extensions
This BIP provides a generic mechanism for specifying stratum protocol extensions. At the same time, one of the important extensions that is specified by this BIP is…
Applications2018Draft
320nVersion bits for general purpose use
This BIP reserves 16 bits of the block header nVersion field for general purpose use and removes their meaning for the purpose of version bits soft-fork signalling.…
Process / no layer2018Draft
321URI Scheme
This BIP proposes a URI scheme for describing Bitcoin payment instructions.
Applications2024CompleteComplete, awaiting adoption
322Generic Signed Message Format
Generic signed messages that work for every address type, not just legacy ones.
Applications2018CompleteComplete, awaiting adoption
32324 nVersion bits for general purpose use
24 bits are reserved in the nVersion field as extra nonce space for miners, providing for additional hashrate with header-only mining without relying on rolling nTime…
Process / no layer2026DraftIn Bitcoin Core
324Version 2 P2P Encrypted Transport Protocol
Encrypted P2P transport (v2): node-to-node traffic is encrypted and harder to fingerprint. On by default since Bitcoin Core v27.
Peer Services2019DeployedIn Bitcoin Core
325Signet
Signet: a test network where blocks are signed by a set of keys, giving developers a stable, predictable playground.
Applications2019CompleteIn Bitcoin Core
326Anti-fee-sniping in taproot transactions
This document proposes a certain type of wallet behaviour which uses BIP341 taproot[1]. It provides a greater anonymity set for off-chain protocols which will make use…
Applications2021Draft
327MuSig2 for BIP340-compatible Multi-Signatures
MuSig2: several parties produce one Schnorr signature for one aggregated key. Multisig that looks like single-sig on-chain.
Process / no layer2022DeployedIn Bitcoin Core
328Derivation Scheme for MuSig2 Aggregate Keys
This document specifies how BIP 32 extended public keys can be constructed from a BIP 327 MuSig2 aggregate public key and how such keys should be used for key…
Applications2024CompleteIn Bitcoin Core
329Wallet Labels Export Format
This document specifies a format for the export of labels that may be attached to various common types of records in a wallet.
Applications2022Draft
330Transaction announcements reconciliation
This document specifies a P2P protocol extension for reconciliation of transaction announcements between 2 nodes, which is a building block for efficient transaction…
Peer Services2019Draft
331Ancestor Package Relay
Peer-to-peer protocol messages enabling nodes to request and relay the unconfirmed ancestor package of a given transaction, and to request and relay transactions in…
Peer Services2022Draft
332Stale Tip Relay
Bitcoin miners sporadically produce stale blocks: valid blocks or valid block headers that do not become part of the node's active chain. This BIP defines a new…
Peer Services2026Draft
337Compressed Transactions
This document proposes a serialization scheme for compressing Bitcoin transactions. The compressed Bitcoin transactions can reach a serialized size of less than 50% of…
API/RPC2024Draft
338Disable transaction relay message
This BIP describes a change to the p2p protocol to allow a node to tell a peer that a connection will not be used for transaction relay, to support block-relay-only…
Peer Services2020Closed
339WTXID-based transaction relay
Relay transactions by wtxid (including the witness), fixing a class of relay problems after SegWit.
Peer Services2020DeployedIn Bitcoin Core
340Schnorr Signatures for secp256k1Taproot
Schnorr signatures for secp256k1 — provably secure, linear and batch-verifiable. Taproot's signature scheme.
Process / no layer2020DeployedActivated soft fork
341Taproot: SegWit version 1 spending rulesTaproot
Taproot spending rules (SegWit v1): key path for the common case, script path via a Merkle tree for the rest.
Consensus (soft fork)2020DeployedActivated soft fork
342Validation of Taproot ScriptsTaproot
Tapscript: the script rules inside Taproot, including OP_SUCCESS upgrade hooks for future opcodes.
Consensus (soft fork)2020DeployedActivated soft fork
343Mandatory activation of taproot deploymentTaproot
A LOT=true client for Taproot that would have forced activation. Closed in 2026 as no longer relevant.
Consensus (soft fork)2021Closed
345OP_VAULTThe Covenant Zoo
OP_VAULT: purpose-built vaults with a delay and recovery path. Closed.
Consensus (soft fork)2023Closed
346OP_TXHASHThe Covenant Zoo
OP_TXHASH: flexible hashing of parts of the spending transaction, a generalised CTV. Draft.
Consensus (soft fork)2024Draft
347OP_CAT in TapscriptThe Covenant Zoo
OP_CAT in Tapscript: concatenate two stack items. Tiny opcode, big design space (including recursive covenants). Complete since 1 Mar 2026; no activation parameters.
Consensus (soft fork)2023CompleteComplete, awaiting adoption
348CHECKSIGFROMSTACKThe Covenant Zoo
OP_CHECKSIGFROMSTACK: verify a signature over any message, not just the transaction. Part of the LNHANCE and BIP 448 bundles.
Consensus (soft fork)2024Draft
349OP_INTERNALKEYThe Covenant Zoo
OP_INTERNALKEY: push the Taproot internal key onto the stack, saving bytes in covenant scripts.
Consensus (soft fork)2024Draft
350Bech32m format for v1+ witness addresses
Bech32m — the bc1p… address format for Taproot and future witness versions, fixing a Bech32 weakness.
Applications2020DeployedIn Bitcoin Core
351Private Payments
This BIP makes it possible for two parties to transact using addresses that only they can calculate. This is done using exclusively on-chain methods and in a manner…
Applications2022Closed
352Silent Payments
Silent Payments: post one static address; every payment lands on a fresh, unlinkable output, with no interaction and no server.
Applications2023CompleteComplete, awaiting adoption
353DNS Payment Instructions
DNS payment instructions: pay a human-readable name like ₿user@domain using DNSSEC-proved records.
Applications2024CompleteComplete, awaiting adoption
360Pay-to-Merkle-Root (P2MR)Quantum
Pay-to-Merkle-Root (P2MR): nearly the same as a Taproot output but with the key path removed, so coins are not exposed to long-range quantum attacks. Draft.
Consensus (soft fork)2024Draft
361Post Quantum Migration and Legacy Signature SunsetQuantum
Post-Quantum Migration and Legacy Signature Sunset: a phased plan to stop sending to, and later spending from, quantum-vulnerable outputs. Draft.
Consensus (soft fork)2026Draft
370PSBT Version 2
PSBT version 2: a more flexible PSBT format; created by default by Bitcoin Core's PSBT RPCs from v32.
Applications2021DeployedIn Bitcoin Core
371Taproot Fields for PSBT
Taproot fields for PSBT, so hardware and multisig wallets can sign Taproot.
Applications2021DeployedIn Bitcoin Core
372Pay-to-contract tweak fields for PSBT
This document proposes additional fields for BIP 174 PSBTv0 and BIP 370 PSBTv2 that allow for pay-to-contract (P2C) key tweaking data to be included in a PSBT of any…
Applications2022Draft
373MuSig2 PSBT Fields
MuSig2 fields for PSBT.
Applications2024CompleteIn Bitcoin Core
374Discrete Log Equality Proofs
This document proposes a standard for 64-byte zero-knowledge discrete logarithm equality proofs (DLEQ proofs) over an elliptic curve. For given elliptic curve points…
Applications2024Draft
375Sending Silent Payments with PSBTs
This document proposes additional fields and updated role responsibilities for BIP370 PSBTv2 which adds support for sending to silent payments as described in BIP352.
Applications2025Draft
376Spending Silent Payment outputs with PSBTs
This document proposes additional per-input fields for BIP 370 PSBTv2 that allow BIP 352 Silent Payment tweaks to be included in a PSBT of version 2. These fields are…
Applications2026Draft
379Miniscript
Miniscript: a structured language for Bitcoin scripts that wallets can analyse, compose and sign generically.
Applications2023DeployedIn Bitcoin Core
380Output Script Descriptors General Operation
Output script descriptors: a compact text format that fully describes which scripts a wallet watches — the backbone of modern wallet backups.
Applications2021DeployedIn Bitcoin Core
381Non-Segwit Output Script Descriptors
This document specifies pk(), pkh(), and sh() output script descriptors. pk() descriptors take a key and produces a P2PK output script. pkh() descriptors take a key…
Applications2021DeployedIn Bitcoin Core
382Segwit Output Script Descriptors
This document specifies wpkh(), and wsh() output script descriptors. wpkh() descriptors take a key and produces a P2WPKH output script. wsh() descriptors take a script…
Applications2021DeployedIn Bitcoin Core
383Multisig Output Script Descriptors
This document specifies multi(), and sortedmulti() output script descriptors. Both functions take a threshold and one or more public keys and produce a multisig output…
Applications2021DeployedIn Bitcoin Core
384combo() Output Script Descriptors
This document specifies combo() output script descriptors. These take a key and produce P2PK, P2PKH, P2WPKH, and P2SH-P2WPKH output scripts if applicable to the key.
Applications2021DeployedIn Bitcoin Core
385raw() and addr() Output Script Descriptors
This document specifies raw() and addr() output script descriptors. raw() encapsulates a raw script as a descriptor. addr() encapsulates an address as a descriptor.
Applications2021DeployedIn Bitcoin Core
386tr() Output Script Descriptors
tr() descriptors for Taproot outputs.
Applications2021DeployedIn Bitcoin Core
387Tapscript Multisig Output Script Descriptors
This document specifies multi_a() and sortedmulti_a() output script descriptors. Like BIP 383's multi() and sortedmulti(), both functions take a threshold and one or…
Applications2024DeployedIn Bitcoin Core
388Wallet Policies for Descriptor Wallets
Wallet policies: a descriptor variant designed for hardware wallets to register and display multisig policies.
Applications2023CompleteComplete, awaiting adoption
389Multipath Descriptor Key Expressions
This document specifies a modification to Key Expressions of Descriptors that are described in BIP 380. This modification allows Key Expressions to indicate BIP 32…
Applications2022Draft
390musig() Descriptor Key Expression
musig() descriptor key expressions (Bitcoin Core v30 parsing, v31 signing).
Applications2024DraftIn Bitcoin Core
391Binary Output Descriptors
This document proposes an efficient container format for encoding an output descriptor as defined by BIP 380 and its extensions. Based on key-value maps as defined by…
Applications2026Closed
392Silent Payment Output Script Descriptors
This document specifies sp() output script descriptors for silent payments. sp() descriptors take silent payment key material and describe P2TR outputs when combined…
Applications2026Draft
393Output Script Descriptor Annotations
This document specifies an optional annotation syntax for output script descriptors as defined in BIP 380. Annotations are key/value pairs appended to a descriptor…
Applications2026Draft
394rawtr() Output Script Descriptors
This document specifies rawtr() output script descriptors. A rawtr() descriptor expresses a Pay-to-Taproot output by its output key directly, without stating an…
Applications2026Draft
431Topology Restrictions for Pinning
TRUC (v3) transactions: a topology rule that makes Lightning fee bumping resistant to pinning (Bitcoin Core v28).
Applications2024DraftIn Bitcoin Core
433Pay to Anchor (P2A)
Pay to Anchor (P2A): a keyless anchor output anyone can use to bump fees via CPFP (Bitcoin Core v28).
Applications2025DraftIn Bitcoin Core
434Peer Feature Negotiation
Peer feature negotiation for the P2P protocol (Bitcoin Core v32).
Peer Services2026CompleteIn Bitcoin Core
440Varops Budget For Script Runtime Constraint
A varops budget limiting script runtime, prerequisite for restoring disabled opcodes safely. Draft.
Consensus (soft fork)2026Draft
441Restoration of disabled script (Tapleaf 0xC2)
Great Script Restoration: bring back opcodes disabled in 2010 under a new Tapleaf version, bounded by BIP 440. Draft.
Consensus (soft fork)2026Draft
442OP_PAIRCOMMITThe Covenant Zoo
OP_PAIRCOMMIT: commit to two stack items at once; part of LNHANCE. Draft.
Consensus (soft fork)2024Draft
443OP_CHECKCONTRACTVERIFYThe Covenant Zoo
OP_CHECKCONTRACTVERIFY (MATT): carry state into the next output, enabling vaults and fraud-proof protocols. Draft.
Consensus (soft fork)2025Draft
446OP_TEMPLATEHASHThe Covenant Zoo
OP_TEMPLATEHASH: push a hash of the spending transaction — a Taproot-native successor to CTV. Draft; live on Bitcoin Inquisition signet.
Consensus (soft fork)2026Draft
448Taproot-native (Re)bindable TransactionsThe Covenant Zoo
Taproot-native (Re)bindable Transactions: deploy TEMPLATEHASH + CSFS + INTERNALKEY together. Draft; activation left to be determined.
Consensus (soft fork)2026Draft
449OP_TWEAKADD - x-only key tweak addition
This proposal defines a new tapscript opcode, OP_TWEAKADD, that takes an x-only public key and a 32-byte integer t on the stack and pushes the x-only public key…
Consensus (soft fork)2026Draft
450Formosa—Seed encoding by themed mnemonic stories
This BIP describes Formosa, an expansion of BIP-0039 for the generation of deterministic wallets. Where BIP-0039 maps each 11 bits of entropy to one word drawn from a…
Applications2026Draft
451Dust UTXO Disposal Protocol
This BIP specifies a standardized protocol for safely disposing of dust UTXOs by spending them to an OP_RETURN output with the entire value going to transaction fees.…
Applications2026Draft
458Half-Aggregation of BIP 340 Signatures
Half-aggregation of Schnorr signatures: n signatures in 32×(n+1) bytes instead of 64×n.
Applications2026Draft
459DahLIAS fully aggregated signatures for secp256k1
DahLIAS: fully aggregate signatures across keys and messages into one 64-byte signature.
Applications2026Draft
460CISA for Taproot Key Path Spends in SegWit v2
Cross-input signature aggregation (CISA) for a new SegWit v2 key path — cheaper coinjoins and batched payments. Draft; needs a soft fork.
Consensus (soft fork)2026Draft
461Deterministic ECDSA Signatures
This document specifies an ECDSA signing algorithm whose output is fully determined by the secret key and the message being signed. Its signatures are at most 70 bytes…
Applications2026DraftIn Bitcoin Core
No BIPs match. Try fewer filters.
07

Sources & method

#
Counts — parsed from every BIP header in bitcoin/bips at commit a7f9132 (2026-11-17). Re-run tools/parse_bips.py to refresh.
Adoption tiers — Activated soft fork (mainnet activation, cited) → In Bitcoin Core (listed in doc/bips.md) → Deployed (repo status) → Complete → Draft → Closed.
Plain English — 111 notable BIPs have hand-written summaries; the rest show the BIP’s own abstract, labelled as such.

171 sources cited on this page.

  1. BIP 30, “Duplicate transactions”, bitcoin/bips (commit a7f9132, 2026-11-17)
  2. Bitcoin Core, doc/bips.md — BIPs implemented by Bitcoin Core (master, read 20 Nov 2026)
  3. BIP 16, “Pay to Script Hash”, bitcoin/bips (commit a7f9132, 2026-11-17)
  4. BIP 13, “Address Format for pay-to-script-hash”, bitcoin/bips (commit a7f9132, 2026-11-17)
  5. BIP 34, “Block v2, Height in Coinbase”, bitcoin/bips (commit a7f9132, 2026-11-17)
  6. Bitcoin Core, src/kernel/chainparams.cpp — mainnet BIP34/65/66/CSV/SegWit heights
  7. mempool.space, block 227,931
  8. BIP 66, “Strict DER signatures”, bitcoin/bips (commit a7f9132, 2026-11-17)
  9. BIP 90, “Buried Deployments”, bitcoin/bips (commit a7f9132, 2026-11-17)
  10. mempool.space, block 363,725
  11. BIP 65, “OP_CHECKLOCKTIMEVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17)
  12. mempool.space, block 388,381
  13. BIP 68, “Relative lock-time using consensus-enforced sequence numbers”, bitcoin/bips (commit a7f9132, 2026-11-17)
  14. BIP 112, “CHECKSEQUENCEVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17)
  15. BIP 113, “Median time-past as endpoint for lock-time calculations”, bitcoin/bips (commit a7f9132, 2026-11-17)
  16. mempool.space, block 419,328
  17. BIP 141, “Segregated Witness (Consensus layer)”, bitcoin/bips (commit a7f9132, 2026-11-17)
  18. BIP 143, “Transaction Signature Verification for Version 0 Witness Program”, bitcoin/bips (commit a7f9132, 2026-11-17)
  19. BIP 147, “Dealing with dummy stack element malleability”, bitcoin/bips (commit a7f9132, 2026-11-17)
  20. mempool.space, block 481,824
  21. Bitcoin: All the Hard Forks and Soft Forks (BTCTKVR: Forks!)
  22. BIP 340, “Schnorr Signatures for secp256k1”, bitcoin/bips (commit a7f9132, 2026-11-17)
  23. BIP 341, “Taproot: SegWit version 1 spending rules”, bitcoin/bips (commit a7f9132, 2026-11-17)
  24. BIP 342, “Validation of Taproot Scripts”, bitcoin/bips (commit a7f9132, 2026-11-17)
  25. mempool.space, block 709,632
  26. Bitcoin Core 0.21.1 release notes (Taproot activation parameters)
  27. BIP 42, “A finite monetary supply for Bitcoin”, bitcoin/bips (commit a7f9132, 2026-11-17)
  28. BIP 91, “Reduced threshold Segwit MASF”, bitcoin/bips (commit a7f9132, 2026-11-17)
  29. BIP 148, “Mandatory activation of segwit deployment”, bitcoin/bips (commit a7f9132, 2026-11-17)
  30. Fork Wars: the block size war timeline (Bitcoin Takeover)
  31. BIP 110, “Reduced Data Temporary Softfork”, bitcoin/bips (commit a7f9132, 2026-11-17)
  32. Bitcoin BLAKE2b: The Fork That Fired the Miners (BTCTKVR: Forks!)
  33. mempool.space, block 961,632 (first block of BIP-110's mandatory-signalling window)
  34. BIP 3, “Updated BIP Process”, bitcoin/bips (commit a7f9132, 2026-11-17)
  35. BIP 12, “OP_EVAL”, bitcoin/bips (commit a7f9132, 2026-11-17)
  36. BIP 17, “OP_CHECKHASHVERIFY (CHV)”, bitcoin/bips (commit a7f9132, 2026-11-17)
  37. BIP 18, “hashScriptCheck”, bitcoin/bips (commit a7f9132, 2026-11-17)
  38. bitcoin-dev, Luke-Jr, “Re: Fw: Quote on BIP 16” (29 Jan 2012), b10c mirror
  39. bitcoin-dev, Luke-Jr, “Re: BIP16/17 replacement” (31 Jan 2012), b10c mirror
  40. bitcoin-dev, Gavin Andresen, “BIP 16 status update” (27 Feb 2012), b10c mirror
  41. BIP 37, “Connection Bloom filtering”, bitcoin/bips (commit a7f9132, 2026-11-17)
  42. BIP 157, “Client Side Block Filtering”, bitcoin/bips (commit a7f9132, 2026-11-17)
  43. Bitcoin Core PR #16152, “Disable bloom filtering by default” (Matt Corallo) — merged
  44. Bitcoin Core 0.19.0 release notes
  45. BIP 70, “Payment Protocol”, bitcoin/bips (commit a7f9132, 2026-11-17)
  46. Bitcoin Magazine, “Wallet developers express security concerns over BitPay’s Payment Protocol policy”
  47. r/Bitcoin, achow101: “Annoyed by BitPay’s exclusive use of the payment protocol?”
  48. Bitcoin Core PR #15584, disable BIP70 support by default
  49. Bitcoin Core 0.20.0 release notes
  50. BIP 39, “Mnemonic code for generating deterministic keys”, bitcoin/bips (commit a7f9132, 2026-11-17)
  51. Electrum documentation, “Electrum Seed Version System”
  52. Bitcoin Stack Exchange, “Is there a reason why Bitcoin Core does not implement BIP39?” (answer by Ava Chow)
  53. BIP 62, “Dealing with malleability”, bitcoin/bips (commit a7f9132, 2026-11-17)
  54. Bitcointalk, Mt. Gox statement on transaction malleability (10 Feb 2014)
  55. bitcoin.org alert, “Transaction malleability” (11 Feb 2014)
  56. The Verge, “Mt. Gox blames account freeze on Bitcoin-wide vulnerability” (10 Feb 2014)
  57. BIP 101, “Increase maximum block size”, bitcoin/bips (commit a7f9132, 2026-11-17)
  58. BIP 109, “Two million byte size limit with sigop and sighash limits”, bitcoin/bips (commit a7f9132, 2026-11-17)
  59. Bitcoin Wiki (en.bitcoin.it), “Bitcoin XT”
  60. bitcoin/bips pull request #329, “Withdraw BIP 101 proposal” (Gavin Andresen, Feb 2016)
  61. Bitcoin Roundtable, “Bitcoin Roundtable Consensus”, Medium, 20 Feb 2016 (Wayback Machine copy)
  62. Bitcoin Cash: The Big Block Breakaway (BTCTKVR: Forks!)
  63. Bitcointalk, satoshi, “Re: [PATCH] increase block size limit” (4 Oct 2010)
  64. bitcoin-dev, Gregory Maxwell, “Capacity increases for the Bitcoin system.” (7 Dec 2015), b10c mirror
  65. bitcoin-dev, Mike Hearn, “Re: Block size following technological growth” (31 Jul 2015), b10c mirror
  66. r/Bitcoin, theymos (moderator), “It's time for a break: About the recent mess & temporary new rules” (Aug 2015)
  67. bitcoin-dev, Jeff Garzik, “Re: Block size: It's economics & user preparation & moral hazard” (18 Dec 2015), b10c mirror
  68. BIP 125, “Opt-in Full Replace-by-Fee Signaling”, bitcoin/bips (commit a7f9132, 2026-11-17)
  69. Bitcoin Core PR #6871, opt-in full-RBF (BIP 125) — merged Nov 2015
  70. bitcoincore.org, Opt-in RBF FAQ
  71. Bitcoin Core 24.0 release notes
  72. bitcoin-dev, Dario Sneidermanis (Muun), “Full-RBF peer discovery” / zero-conf warning (7 Oct 2022), b10c mirror
  73. Bitcoin Core PR #26287, “Temporarily disable -mempoolfullrbf for the main chain” — closed
  74. Bitcoin Core 28.0 release notes
  75. Digital Currency Group, “Bitcoin Scaling Agreement at Consensus 2017”, Medium, 23 May 2017 (Wayback Machine copy)
  76. Mike Belshe et al., “Segwit2x Final Steps”, bitcoin-segwit2x mailing list, 8 Nov 2017 (Wayback Machine copy)
  77. bitcoin-dev, shaolinfry, “Moving towards user activated soft fork activation” (25 Feb 2017), b10c mirror
  78. bitcoin-dev, James Hilliard, “Reduced signalling threshold activation of existing segwit deployment” (22 May 2017), b10c mirror
  79. BIP 2, “BIP process, revised”, bitcoin/bips (commit a7f9132, 2026-11-17)
  80. @LukeDashjr on X, 23 Feb 2024: BIP repo backlog
  81. bitcoin-dev, Ava Chow, “Adding New BIP Editors” (27 Feb 2024), b10c mirror
  82. bitcoin-dev, Matt Corallo in the BIP editors thread (21 Apr 2024), b10c mirror
  83. Bitcoin Optech Newsletter #299 (24 Apr 2024) — new BIP editors
  84. Bitcoin Optech Newsletter (16 Jan 2026) — BIP 3 deployed
  85. BIP 300, “Hashrate Escrows (Consensus layer)”, bitcoin/bips (commit a7f9132, 2026-11-17)
  86. BIP 301, “Blind Merged Mining (Consensus layer)”, bitcoin/bips (commit a7f9132, 2026-11-17)
  87. Peter Todd, “Drivechains: A Detailed Analysis” (2023)
  88. drivechain.info
  89. eCash (ECX): Paul Sztorc Forks Bitcoin to Prove a Point (BTCTKVR: Forks!)
  90. bitcoin-dev, Peter Todd, “Re: Drivechain -- Request for Discussion” (22 May 2017), b10c mirror
  91. bitcoin-dev, Paul Sztorc, “Two Drivechain BIPs” (1 Dec 2017), b10c mirror
  92. BIP 347, “OP_CAT in Tapscript”, bitcoin/bips (commit a7f9132, 2026-11-17)
  93. BIP 448, “Taproot-native (Re)bindable Transactions”, bitcoin/bips (commit a7f9132, 2026-11-17)
  94. BIP 446, “OP_TEMPLATEHASH”, bitcoin/bips (commit a7f9132, 2026-11-17)
  95. BIP 345, “OP_VAULT”, bitcoin/bips (commit a7f9132, 2026-11-17)
  96. Bitcoin Optech Newsletter, 5 Dec 2025 — “LNHANCE soft fork”
  97. Bitcoin Optech Newsletter, 4 Sep 2026 — “BIP448 and CSFS/CTV demos and applications”
  98. Bitcoin Optech Newsletter, 1 Aug 2025 — Taproot-native OP_TEMPLATEHASH proposal
  99. Delving Bitcoin, “Bitcoin Inquisition 29.4” (signet activation heights for APO, CTV, OP_CAT, CSFS, IKEY, BIP54, TEMPLATEHASH)
  100. bitcoin-dev, Andrew Poelstra, “Re: Proposed BIP for OP_CAT” (21 Oct 2023), b10c mirror
  101. bitcoin-dev, James O'Beirne, “Re: Proposed BIP for OP_CAT” (26 Oct 2023), b10c mirror
  102. bitcoin-dev, Matt Corallo, “Re: CTV + CSFS: a letter” (9 Jun 2025), b10c mirror
  103. bitcoin-dev, Gregory Maxwell, “BIP proposal: Inhibiting a covert attack on the Bitcoin POW function” (5 Apr 2017), learnbitcoin archive
  104. Secondary: Bitcoin Stack Exchange, answers quoting Bitmain’s April 2017 statement and noting overt-AsicBoost firmware
  105. CoinGeek, “Bitmain activates controversial mining hack AsicBoost” (2018)
  106. Bitcointalk, ASICBoost thread (April 2017)
  107. BIP 54, “Consensus Cleanup”, bitcoin/bips (commit a7f9132, 2026-11-17)
  108. BIP 53, “Disallow 64-byte transactions”, bitcoin/bips (commit a7f9132, 2026-11-17)
  109. Bitcoin Optech topic, “Consensus cleanup soft fork” (also covering BIP54)
  110. Bitcoin Optech Newsletter #430, 6 Nov 2026 — “Continued discussion of BIP54”, QSAVE, opt-in replay protection
  111. Antoine Riard, “Getting BIP54 past the finish line”, Bitcoin-Dev mailing list, Nov 2026 (archive)
  112. Bitcoin Core PR #35793 — BIP54 implementation (regtest only, no mainnet activation)
  113. bitcoin-dev, Antoine Poinsot, “Great Consensus Cleanup Revival” (24 Mar 2024), b10c mirror
  114. bitcoin-dev, Eric Voskuil, “RE: Consensus Cleanup BIP draft” (31 Mar 2025), b10c mirror
  115. BIP 8, “Version bits with lock-in by height”, bitcoin/bips (commit a7f9132, 2026-11-17)
  116. BIP 343, “Mandatory activation of taproot deployment”, bitcoin/bips (commit a7f9132, 2026-11-17)
  117. Bitcoin Core PR #21377, “Speedy trial support for versionbits” (ajtowns; opened 6 Mar 2021, merged 15 Apr 2021)
  118. bitcoin-dev, Luke Dashjr, “LOT=False is dangerous and shouldn't be used” (28 Feb 2021), b10c mirror
  119. bitcoin-dev, David A. Harding, “Taproot activation proposal “Speedy Trial”” (6 Mar 2021), b10c mirror
  120. bitcoin-dev, Keagan McClelland, “Re: Taproot activation proposal “Speedy Trial”” (6 Mar 2021), b10c mirror
  121. BIP 119, “CHECKTEMPLATEVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17)
  122. Jeremy Rubin, “7 Theses on a next step for BIP-119”, rubin.io, 17 Apr 2022
  123. Bitcoin Optech Newsletter, 27 Apr 2022, “Discussion about activating CTV”
  124. Bitcoin Optech Newsletter, 4 Jul 2025, “Open letter about CTV and CSFS”
  125. Bitcoin Optech Newsletter, 2 Jan 2026, “CTV activation meeting”
  126. Bitcoin Optech topic — OP_CHECKTEMPLATEVERIFY (uses, alternatives, criticisms)
  127. Delving Bitcoin, “BIP 119 CTV activation client” (1440000bytes, 9 Feb 2026)
  128. ctv-activation.github.io — deployment parameters and meeting logs
  129. bip119monitor.com — BIP-119 signalling, period 484 (read 20 Nov 2026, 01:45 UK time: 0 of 920 blocks, 0.00%)
  130. bitcoin-dev, Jeremy Rubin, “On The Drama” (2 May 2022), b10c mirror
  131. bitcoin-dev, James O'Beirne, “CTV + CSFS: a letter” (9 Jun 2025), b10c mirror
  132. bitcoin-dev, Antoine Poinsot, “Re: CTV + CSFS: a letter” (17 Jun 2025), b10c mirror
  133. Bitcoin Core, “Bitcoin Core development and transaction relay policy” (6 Jun 2025)
  134. Bitcoin Core PR #32406, “policy: uncap datacarrier by default” (instagibbs; opened 2 May 2025, merged 9 Jun 2025)
  135. Bitcoin Core 30.0 release notes (datacarriersize default 100,000; multiple OP_RETURN outputs)
  136. bitcoin-dev, Antoine Poinsot, “Relax OP_RETURN standardness restrictions” (17 Apr 2025), b10c mirror
  137. Bitcoin Core PR #32406, “policy: uncap datacarrier by default” (instagibbs) — GitHub conversation
  138. bitcoin-dev, Murch, “BIP 110: update status to closed” (9 Aug 2026), b10c mirror
  139. bitcoin/bips PR #1408, “Ordinal Numbers” (Casey Rodarmor) — closed without a number
  140. BIP 360, “Pay-to-Merkle-Root (P2MR)”, bitcoin/bips (commit a7f9132, 2026-11-17)
  141. BIP 361, “Post Quantum Migration and Legacy Signature Sunset”, bitcoin/bips (commit a7f9132, 2026-11-17)
  142. Bitcoin Optech Newsletter, 24 Apr 2026 — BIPs #1895 publishes BIP361
  143. Bitcoin Optech Newsletter, 26 Jun 2026 — BIPs #2198 updates BIP360 (P2MR)
  144. Bitcoin Optech Newsletter #425, 2 Oct 2026 — PQC output types; comparing covenant vaults
  145. Bitcoin Optech topic — Quantum resistance
  146. bitcoin-dev, Jameson Lopp, “A Post Quantum Migration Proposal” (12 Jul 2025), b10c mirror
  147. bitcoin-dev, Peter Todd, “Re: A Post Quantum Migration Proposal” (19 Jul 2025), b10c mirror
  148. BIP 94, “Testnet 4”, bitcoin/bips (commit a7f9132, 2026-11-17)
  149. bitcoindev Google Group, Jameson Lopp, “The Future of Bitcoin Testnet” (31 Mar 2024)
  150. Cointelegraph, “Bitcoiners furious after Jameson Lopp admits griefing testnet to prove point”
  151. Jameson Lopp, “Griefing Bitcoin’s Testnet”, blog.lopp.net
  152. BIP 177, “Redefine Bitcoin's Base Unit”, bitcoin/bips (commit a7f9132, 2026-11-17)
  153. @BitcoinErrorLog on X, 23 Apr 2025: BIP 177 announced
  154. @BitcoinErrorLog on X, 9 May 2025: BIP 177 merged
  155. Decrypt, “Goodbye, Satoshi? Jack Dorsey wants Bitcoin rebrand”
  156. CryptoSlate, “Bitcoin debate reignited with satoshi unit redefinition proposal”
  157. @parkeralewis on X, 17 May 2025: “Easy A. Sats standard”
  158. BIP 95, “Testnet 5”, bitcoin/bips (commit a7f9132, 2026-11-17)
  159. S17 E48: Robin Linus — “We're going to get BIP 448, TEMPLATEHASH”
  160. BIP 458, “Half-Aggregation of BIP 340 Signatures”, bitcoin/bips (commit a7f9132, 2026-11-17)
  161. BIP 459, “DahLIAS fully aggregated signatures for secp256k1”, bitcoin/bips (commit a7f9132, 2026-11-17)
  162. BIP 460, “CISA for Taproot Key Path Spends in SegWit v2”, bitcoin/bips (commit a7f9132, 2026-11-17)
  163. BIP 440, “Varops Budget For Script Runtime Constraint”, bitcoin/bips (commit a7f9132, 2026-11-17)
  164. BIP 441, “Restoration of disabled script (Tapleaf 0xC2)”, bitcoin/bips (commit a7f9132, 2026-11-17)
  165. BIP 118, “SIGHASH_ANYPREVOUT for Taproot Scripts”, bitcoin/bips (commit a7f9132, 2026-11-17)
  166. BIP 443, “OP_CHECKCONTRACTVERIFY”, bitcoin/bips (commit a7f9132, 2026-11-17)
  167. BIP 346, “OP_TXHASH”, bitcoin/bips (commit a7f9132, 2026-11-17)
  168. BIP 352, “Silent Payments”, bitcoin/bips (commit a7f9132, 2026-11-17)
  169. BIP 77, “Async Payjoin”, bitcoin/bips (commit a7f9132, 2026-11-17)
  170. Bitcoin Core release tags (v32.0, v32.1)
  171. Bitcoin Optech Newsletter #431, 13 Nov 2026 — testnet5 genesis plan
0:000:00