BIP 30 · No duplicate txids
Stopped a new transaction from reusing the txid of an earlier transaction that still had unspent outputs, closing a way to overwrite coins.
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.
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.
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.
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).
Stopped a new transaction from reusing the txid of an earlier transaction that still had unspent outputs, closing a way to overwrite coins.
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.
Every block must write its own height into the coinbase. Coinbase transactions became unique, and the first miner-signalled upgrade mechanism was born.
Forced one exact signature encoding so Bitcoin no longer depended on OpenSSL's quirks for consensus, and removed a malleability source.
Coins can be locked until a future date or block height. The building block for timelocked refunds, payment channels and the Lightning Network.
“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.
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.
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.
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:
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.
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.
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.
A new opcode, OP_CHECKHASHVERIFY, instead of special-casing a script pattern. Miners vote with “p2sh/CHV”; needs at least 60%.
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.
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.
“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 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.
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.
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.
It decided whether ordinary nodes keep serving phone wallets, which pitted node resources against light-client independence. One commenter called it sabotage.
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.
“BIP 37 bloom filters have been well-known to be a significant DoS target for some time.”
BIP 70 (2013) replaced copying an address with a payment request fetched from the merchant’s server and authenticated with X.509 certificates.
From late 2017 it required the Payment Protocol on its invoices, saying wallets that matter already supported it.
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.
A dominant payment processor made an optional standard mandatory, so people whose wallets lacked it could no longer pay BitPay invoices.
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.
“These true bitcoin wallets all already ‘speak’ Payment Protocol”
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.
BIP 39, written by Marek Palatinus, Pavol Rusnak, Aaron Voisine and Sean Bowe, became the common backup format. Its header says Deployed.
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.
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.
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”
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.
Blamed a long-known Bitcoin “design issue”, suspended bitcoin withdrawals, and said it would allow them again once a fix was “approved and standardized”.
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.
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.
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.
“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.”
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).
On-chain payments must stay cheap; raise the limit now. Shipped in Bitcoin XT (BIP 101) and Bitcoin Classic (BIP 109).
Bigger blocks centralise validation; add capacity with SegWit and second layers such as Lightning, without a hard fork.
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.
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.
“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.”
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.
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.
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.
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.
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).
“This article lays out the case against RBF-SE and argues it is harmful to Bitcoin.”
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).
Fix malleability and add capacity by soft fork. If miners won't signal, reject their blocks from 1 August 2017 (BIP 148).
Withhold signalling as leverage; activate SegWit only as part of “SegWit2x”, with a 2 MB hard fork about 90 days later.
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).
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.
“As such, soft forks rules are actually always enforced by the nodes, not the miners.”
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.
Ava Chow proposed new editors with the same permissions as Luke Dashjr to clear the backlog and answer authors in a timely manner.
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.
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.
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.
“There's 133 pull requests open in the #Bitcoin Improvement Proposal repository, going back several months.😵”
Sidechains secured by Bitcoin miners: hashrate escrows for the peg (BIP 300) and blind merged mining (BIP 301), by Paul Sztorc and CryptAxe.
Let users opt into new features on sidechains without changing Bitcoin itself; miners earn more fees.
Puts miners in charge of sidechain funds and changes their incentives in ways critics consider unsafe for Bitcoin.
A decade-long argument about whether Bitcoin should host sidechains at the consensus level, waged on podcasts as much as on mailing lists.
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.
“It's unclear to me what the incentive is for miners to do any of this.”
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.
LNHANCE (CTV + CSFS + INTERNALKEY + PAIRCOMMIT) or BIP 448 (TEMPLATEHASH + CSFS + INTERNALKEY): small, analysable opcodes aimed at Lightning, Ark, vaults and DLCs.
OP_CAT and script restoration for maximum flexibility — or no covenants, for fear of complexity and recursive covenants.
Competing packages target overlapping use cases, and reviewers have not converged on one. Every new proposal splits review attention further.
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.
“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".”
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.
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.
It said it had tested ASICBoost on testnet but never used it on mainnet, demanded proof, and called Maxwell’s maths incorrect.
It tied the SegWit standoff to a patent-protected mining edge, which made a technical fight look like a commercial one.
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.
“Reverse engineering of a particular mining chip has demonstrated conclusively that ASICBOOST has been implemented in hardware.”
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.
Close real attack vectors — a timewarp attacker could drop difficulty to its minimum within 38 days — with minimal side effects.
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.
Low drama by Bitcoin standards, but it is the test of whether Bitcoin can still ship any soft fork at all.
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.
“i believe it's more important to fix the timewarp bug than people usually think;”
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.
Make signalling mandatory at the end so miners cannot veto an upgrade users want (the lesson many drew from 2017).
Never force a chain split: give miners a short, 90% window and try again later if it fails.
Taproot itself was uncontroversial; the activation method became a proxy fight over the lessons of the UASF.
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”.
“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.”
OP_CHECKTEMPLATEVERIFY (BIP 119, Jeremy Rubin): an output can commit to the exact transaction that spends it — vaults, congestion control, channel factories, cheaper DLCs.
Simple, non-recursive, well-understood and reviewed for years. Activate it, or say clearly why not.
Not flexible or generic enough, little real experimentation (Optech's summary of criticisms); worries that activation is being pushed without broad consensus.
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).
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.
“I still do not know exactly what happened and why.”
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”.
“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.”
Arbitrary data distorts incentives; restrict it at the consensus level with a 55% threshold and mandatory signalling.
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.
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”.
“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.”
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.
A BIP documents a standard people use; it is not an endorsement, so being controversial is no reason to refuse a number.
Numbering sats harms fungibility and encourages spam. The standard should live in its own repository, like Lightning’s BOLTs or SatoshiLabs’ SLIPs.
It turned the BIP editors’ merge button into a vote on inscriptions, and the pull request sat open for more than three years.
On 4 March 2026 BIP editor Kanzure rejected the pull request, declined to assign a number and closed it.
“An accepted BIP does not indicate endorsement by the BIP repo maintainers, Bitcoin Core, or the larger Bitcoin community.”
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).
Phase A stops payments to quantum-vulnerable addresses; Phase B restricts ECDSA/Schnorr spending, with a rescue protocol, to prevent mass theft.
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.
It touches the most sensitive question in Bitcoin — whether anyone's coins can ever be made unspendable — on a timeline nobody can predict.
All Draft; no activation mechanism. 2026 brought SHRINCS, QSAVE drafts and a steady stream of PQ output-type debate on Delving Bitcoin.
“It turns quantum security into a private incentive: fail to upgrade and you will certainly lose access to your funds”
BIP 94 starts a new test network, testnet4, that fixes the difficulty-reset rule testnet3 abused to produce “block storms”.
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.
Attacking a shared test network mainly wasted builders’ time. Francis Pouliot likened it to fouling a jacuzzi to make people move spas.
A well-known developer deliberately disrupted a public test network to win an argument, and some application builders had to halt their testing.
Bitcoin Core 28.0 added testnet4 as specified in BIP 94, which is now Deployed.
“TBTC is being actively bought and sold; one could argue that the fundamental principle of testnet coins having no value has been broken.”
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.
Decimals confuse newcomers, and calling the smallest unit a bitcoin matches how the protocol actually counts.
“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.
It changes no code but does change the most-quoted number in Bitcoin, so everyone had an opinion.
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,”
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.
Specification complete, implementation in review, broad support — but no activation parameters yet.
Unlocks: Removes the timewarp attack, caps worst-case validation time, kills the 64-byte transaction Merkle trick and duplicate coinbases.
Blockers: The 64-byte transaction rule is still the most contested; no activation method chosen. Riard (personal view): consider activation in H2 2027.
Working code and serious backers, but rival designs compete for the same soft-fork slot.
Unlocks: Rebindable signatures and next-transaction commitments in Tapscript: LN-Symmetry, non-interactive Ark receives, simpler vaults and DLCs.
Blockers: BIP 448 says activation is “left to be determined at a later date”; competes with LNHANCE/CTV.
Unlocks: Vaults, congestion control, channel factories; with CSFS, LN-Symmetry-style channels.
Blockers: Essentially no miner signalling; no Bitcoin Core release carries it; reviewers split between CTV- and TEMPLATEHASH-based bundles.
Unlocks: Concatenation in Tapscript; enables many covenant and verification constructions (including recursive ones).
Blockers: No activation parameters; generality (recursive covenants) is exactly what sceptics fear.
Promising or necessary, but years of design and review remain — or the community is split on whether to do it at all.
Unlocks: A path off quantum-vulnerable signatures before a capable quantum computer exists.
Blockers: No agreement on whether to freeze vulnerable coins, which signature scheme, or when.
Unlocks: Smaller multi-input transactions — cheaper coinjoins, payjoins and consolidations.
Blockers: New witness version needed; interacts with the quantum output-type debate.
Unlocks: Re-enable opcodes disabled in 2010 (arithmetic, string ops) under a runtime budget.
Blockers: Large surface area; needs extensive benchmarking and review.
Unlocks: APO for LN-Symmetry; CCV (MATT) for vaults and fraud proofs; TXHASH as a general template opcode.
Blockers: Overlap with the 448/LNHANCE bundles.
Unlocks: Miner-secured sidechains.
Blockers: Long-standing opposition on miner-incentive grounds.
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.
| BIP | Title · what it does | Layer | Year | Status | Adoption | |
|---|---|---|---|---|---|---|
| 1 | BIP 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 layer | 2011 | Closed | ||
| 2 | BIP 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 layer | 2016 | Closed | ||
| 3 | Updated 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 layer | 2025 | Deployed | Deployed (ecosystem) | |
| 8 | Version 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 layer | 2017 | Complete | Complete, awaiting adoption | |
| 9 | Version 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 layer | 2015 | Deployed | In Bitcoin Core | |
| 10 | Multi-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… | Applications | 2011 | Closed | ||
| 11 | M-of-N Standard Transactions Made M-of-N multisig outputs standard, so shared custody became possible on-chain. | Applications | 2011 | Deployed | In Bitcoin Core | |
| 12 | OP_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) | 2011 | Closed | ||
| 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. | Applications | 2011 | Deployed | In Bitcoin Core | |
| 14 | Protocol Version and User Agent Defined the user agent string nodes use to identify their software to peers. | Peer Services | 2011 | Deployed | In Bitcoin Core | |
| 15 | Aliases Aliases. | Applications | 2011 | Closed | ||
| 16 | Pay 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) | 2012 | Deployed | Activated soft fork | |
| 17 | OP_CHECKHASHVERIFY (CHV)The P2SH War OP_CHECKHASHVERIFY, Luke Dashjr's rival to P2SH. Lost the 2012 miner vote and is Closed. | Consensus (soft fork) | 2012 | Closed | ||
| 18 | hashScriptCheckThe P2SH War hashScriptCheck, a compromise variant of the P2SH idea from the same 2012 fight. | Consensus (soft fork) | 2012 | Complete | Complete, awaiting adoption | |
| 19 | M-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. | Applications | 2012 | Closed | ||
| 20 | URI Scheme This BIP proposes a URI scheme for making Bitcoin payments. | Applications | 2011 | Closed | ||
| 21 | URI Scheme The bitcoin: URI scheme behind every clickable or QR-code payment request. | Applications | 2012 | Closed | ||
| 22 | getblocktemplate - Fundamentals getblocktemplate: lets miners and pools build their own block templates instead of blindly trusting a pool server. | API/RPC | 2012 | Deployed | In Bitcoin Core | |
| 23 | getblocktemplate - Pooled Mining This BIP describes extensions to the getblocktemplate JSON-RPC call to enhance pooled mining. | API/RPC | 2012 | Deployed | In Bitcoin Core | |
| 30 | Duplicate 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) | 2012 | Deployed | Activated soft fork | |
| 31 | Pong message This document describes a trivial protocol extension that makes it easier for clients to detect dead peer connections. | Peer Services | 2012 | Deployed | In Bitcoin Core | |
| 32 | Hierarchical Deterministic Wallets HD wallets: one master seed deterministically produces an entire tree of keys. Practically every modern wallet is built on this. | Applications | 2012 | Deployed | In Bitcoin Core | |
| 33 | Stratized 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 Services | 2012 | Closed | ||
| 34 | Block v2, Height in Coinbase Blocks must include their height in the coinbase; introduced the version-number supermajority upgrade method. | Consensus (soft fork) | 2012 | Deployed | Activated soft fork | |
| 35 | mempool message The mempool P2P message, letting a peer ask what unconfirmed transactions you have. | Peer Services | 2012 | Deployed | In Bitcoin Core | |
| 36 | Custom 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 Services | 2012 | Closed | ||
| 37 | Connection 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 Services | 2012 | Deployed | In Bitcoin Core | |
| 38 | Passphrase-protected private key Passphrase-encrypted private keys (the “6P…” paper-wallet format). | Applications | 2012 | Deployed | Deployed (ecosystem) | |
| 39 | Mnemonic 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. | Applications | 2013 | Deployed | Deployed (ecosystem) | |
| 42 | A 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) | 2014 | Deployed | In Bitcoin Core | |
| 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. | Applications | 2014 | Deployed | In Bitcoin Core | |
| 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. | Applications | 2014 | Deployed | In Bitcoin Core | |
| 45 | Structure 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… | Applications | 2014 | Complete | Complete, awaiting adoption | |
| 46 | Address 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… | Applications | 2022 | Draft | ||
| 47 | Reusable Payment Codes for Hierarchical Deterministic Wallets Reusable payment codes (PayNyms): a static code you can publish without address reuse. | Applications | 2015 | Deployed | Deployed (ecosystem) | |
| 48 | Multi-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),… | Applications | 2020 | Deployed | Deployed (ecosystem) | |
| 49 | Derivation scheme for P2WPKH-nested-in-P2SH based accounts Derivation paths for wrapped SegWit (“3…” P2SH-P2WPKH) accounts. | Applications | 2016 | Deployed | In Bitcoin Core | |
| 50 | March 2013 Chain Fork Post-Mortem The post-mortem of the March 2013 chain split between versions 0.7 and 0.8. | Process / no layer | 2013 | Deployed | Deployed (ecosystem) | |
| 52 | Durable, 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) | 2021 | Closed | ||
| 53 | Disallow 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) | 2025 | Draft | ||
| 54 | Consensus 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) | 2025 | Complete | Complete, awaiting adoption | |
| 60 | Fixed 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 Services | 2013 | Closed | ||
| 61 | Reject P2P message The reject P2P message, telling a peer why its transaction or block was refused. Removed from Bitcoin Core in v0.20. | Peer Services | 2014 | Deployed | In Bitcoin Core | |
| 62 | Dealing 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) | 2014 | Closed | ||
| 64 | getutxo message This document describes a small P2P protocol extension that performs UTXO lookups given a set of outpoints. | Peer Services | 2014 | Closed | ||
| 65 | OP_CHECKLOCKTIMEVERIFY OP_CHECKLOCKTIMEVERIFY: lock coins until a date or block height. | Consensus (soft fork) | 2014 | Deployed | Activated soft fork | |
| 66 | Strict DER signatures Strict DER signature encoding, removing reliance on OpenSSL's parsing for consensus. | Consensus (soft fork) | 2015 | Deployed | Activated soft fork | |
| 67 | Deterministic 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… | Applications | 2015 | Complete | Complete, awaiting adoption | |
| 68 | Relative 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) | 2015 | Deployed | Activated soft fork | |
| 69 | Lexicographical 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… | Applications | 2015 | Complete | Complete, awaiting adoption | |
| 70 | Payment 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. | Applications | 2013 | Deployed | In Bitcoin Core | |
| 71 | Payment Protocol MIME types This BIP defines a MIME (RFC 2046) Media Type for Bitcoin payment request messages. | Applications | 2013 | Deployed | In Bitcoin Core | |
| 72 | bitcoin: uri extensions for Payment Protocol This BIP describes an extension to the bitcoin: URI scheme (BIP 21) to support the payment protocol (BIP 70). | Applications | 2013 | Deployed | In Bitcoin Core | |
| 73 | Use "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… | Applications | 2013 | Deployed | Deployed (ecosystem) | |
| 74 | Allow zero value OP_RETURN in Payment Protocol This BIP alters the Payment Protocol to allow for zero value OP_RETURN outputs in serialized PaymentRequests. | Applications | 2016 | Closed | ||
| 75 | Out 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",… | Applications | 2015 | Deployed | Deployed (ecosystem) | |
| 77 | Async Payjoin Async Payjoin: lets sender and receiver build a privacy-improving payjoin without both being online at once. | Applications | 2023 | Draft | ||
| 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. | Applications | 2019 | Deployed | Deployed (ecosystem) | |
| 79 | Bustapay :: 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… | Applications | 2018 | Closed | ||
| 80 | Hierarchy 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 layer | 2014 | Closed | ||
| 81 | Hierarchy 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 layer | 2014 | Closed | ||
| 83 | Dynamic 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. | Applications | 2015 | Closed | ||
| 84 | Derivation scheme for P2WPKH based accounts Derivation paths for native SegWit (bc1q…) single-sig wallets. | Applications | 2017 | Deployed | In Bitcoin Core | |
| 85 | Deterministic Entropy From BIP32 Keychains Derive child seeds and passwords deterministically from one master key (BIP-85 “child seeds”). | Applications | 2020 | Deployed | Deployed (ecosystem) | |
| 86 | Key Derivation for Single Key P2TR Outputs Derivation paths for single-key Taproot (bc1p…) wallets. | Applications | 2021 | Deployed | In Bitcoin Core | |
| 87 | Hierarchy 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… | Applications | 2020 | Complete | Complete, awaiting adoption | |
| 88 | Hierarchical 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… | Applications | 2020 | Complete | Complete, awaiting adoption | |
| 89 | Chain 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… | Applications | 2025 | Deployed | Deployed (ecosystem) | |
| 90 | Buried Deployments Buried deployments: hard-codes the activation heights of BIPs 34, 65 and 66 instead of counting versions. | Process / no layer | 2016 | Deployed | In Bitcoin Core | |
| 91 | Reduced 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) | 2017 | Deployed | Deployed (ecosystem) | |
| 93 | codex32: 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… | Applications | 2023 | Draft | ||
| 94 | Testnet 4Testnet3 block storms and the testnet4 reset Testnet4, the replacement for the broken testnet3 (Bitcoin Core v28). | Applications | 2024 | Deployed | In Bitcoin Core | |
| 95 | Testnet 5 Testnet5, the proposed replacement for testnet4, with BIP 54 rules active from block 1. | Applications | 2026 | Deployed | Deployed (ecosystem) | |
| 98 | Fast 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) | 2017 | Draft | ||
| 99 | Motivation 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 layer | 2015 | Closed | ||
| 100 | Dynamic maximum block size by miner voteThe Block Size War Jeff Garzik's miner-vote dynamic block size. Closed. | Consensus (hard fork) | 2015 | Closed | ||
| 101 | Increase 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) | 2015 | Closed | ||
| 102 | Block size increase to 2MBThe Block Size War A simple one-time hard fork to 2 MB blocks. Closed. | Consensus (hard fork) | 2015 | Closed | ||
| 103 | Block size following technological growthThe Block Size War Pieter Wuille's slow-growth block size schedule (+17.7% per year). Closed. | Consensus (hard fork) | 2015 | Closed | ||
| 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) | 2017 | Closed | ||
| 105 | Consensus 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) | 2015 | Closed | ||
| 106 | Dynamically 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) | 2015 | Closed | ||
| 107 | Dynamic 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) | 2015 | Closed | ||
| 109 | Two 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) | 2016 | Closed | ||
| 110 | Reduced 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) | 2025 | Closed | ||
| 111 | NODE_BLOOM service bit The NODE_BLOOM service bit, so nodes could advertise (or stop offering) bloom filter service. | Peer Services | 2015 | Deployed | In Bitcoin Core | |
| 112 | CHECKSEQUENCEVERIFY OP_CHECKSEQUENCEVERIFY: scripts can enforce relative timelocks. A core ingredient of Lightning. | Consensus (soft fork) | 2015 | Deployed | Activated soft fork | |
| 113 | Median time-past as endpoint for lock-time calculations Lock times measured against median-time-past instead of a miner-chosen timestamp. | Consensus (soft fork) | 2015 | Deployed | Activated soft fork | |
| 114 | Merkelized Abstract Syntax Tree Merkelized Abstract Syntax Trees — an early design for hiding unused script branches, eventually realised in Taproot. | Consensus (soft fork) | 2016 | Closed | ||
| 115 | Generic 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) | 2016 | Closed | ||
| 116 | MERKLEBRANCHVERIFY 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) | 2017 | Draft | ||
| 117 | Tail 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) | 2017 | Draft | ||
| 118 | SIGHASH_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) | 2017 | Draft | ||
| 119 | CHECKTEMPLATEVERIFYCTV 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) | 2020 | Draft | ||
| 120 | Proof 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… | Applications | 2015 | Closed | ||
| 121 | Proof of Payment URI scheme This is a proposal for a URI scheme to be used in the Proof of Payment process. | Applications | 2015 | Closed | ||
| 122 | URI 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. | Applications | 2015 | Draft | ||
| 123 | BIP 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 layer | 2015 | Deployed | Deployed (ecosystem) | |
| 124 | Hierarchical 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… | Applications | 2015 | Closed | ||
| 125 | Opt-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. | Applications | 2015 | Deployed | Deployed (ecosystem) | |
| 126 | Best 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 layer | 2016 | Draft | ||
| 127 | Simple 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… | Applications | 2019 | Complete | Complete, awaiting adoption | |
| 128 | Timelock-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. | Applications | 2026 | Draft | ||
| 129 | Bitcoin Secure Multisig Setup (BSMS) This document proposes a mechanism to set up multisig wallets securely. | Applications | 2020 | Complete | Complete, awaiting adoption | |
| 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". | Peer Services | 2015 | Deployed | In 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) | 2015 | Closed | ||
| 132 | Committee-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 layer | 2015 | Closed | ||
| 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. | Peer Services | 2016 | Deployed | In Bitcoin Core | |
| 134 | Flexible 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) | 2016 | Closed | ||
| 135 | Generalized 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 layer | 2017 | Closed | ||
| 136 | Bech32 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… | Applications | 2017 | Draft | ||
| 137 | Signatures 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… | Applications | 2019 | Deployed | Deployed (ecosystem) | |
| 138 | Compact 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… | Applications | 2026 | Draft | ||
| 139 | Wallet 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… | Applications | 2026 | Draft | ||
| 140 | Normalized 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) | 2015 | Closed | ||
| 141 | Segregated 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) | 2015 | Deployed | Activated soft fork | |
| 142 | Address 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. | Applications | 2015 | Closed | ||
| 143 | Transaction 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) | 2016 | Deployed | Activated soft fork | |
| 144 | Segregated Witness (Peer Services)SegWit, the UASF and SegWit2x How SegWit transactions and blocks are relayed between peers. | Peer Services | 2016 | Deployed | In Bitcoin Core | |
| 145 | getblocktemplate 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/RPC | 2016 | Deployed | In Bitcoin Core | |
| 146 | Dealing 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) | 2016 | Closed | ||
| 147 | Dealing with dummy stack element malleabilitySegWit, the UASF and SegWit2x Fixed the dummy-element malleability in OP_CHECKMULTISIG. | Consensus (soft fork) | 2016 | Deployed | Activated soft fork | |
| 148 | Mandatory 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) | 2017 | Deployed | Deployed (ecosystem) | |
| 149 | Segregated 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) | 2017 | Closed | ||
| 150 | Peer 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 Services | 2016 | Closed | ||
| 151 | Peer-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 Services | 2016 | Closed | ||
| 152 | Compact Block Relay Compact blocks: send a block as short transaction IDs because peers already have most transactions. Blocks propagate far faster. | Peer Services | 2016 | Deployed | In Bitcoin Core | |
| 154 | Rate Limiting via peer specified challenges An anti-DoS system which provides additional service for peers which perform proof of work. | Peer Services | 2017 | Closed | ||
| 155 | addrv2 message addrv2: lets nodes gossip Tor v3, I2P and CJDNS addresses. | Peer Services | 2019 | Deployed | In Bitcoin Core | |
| 156 | Dandelion - 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 Services | 2017 | Closed | ||
| 157 | Client 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 Services | 2017 | Deployed | In Bitcoin Core | |
| 158 | Compact Block Filters for Light Clients The compact block filter format used by BIP 157 light clients. | Peer Services | 2017 | Deployed | In Bitcoin Core | |
| 159 | NODE_NETWORK_LIMITED service bit NODE_NETWORK_LIMITED: pruned nodes can still serve recent blocks. | Peer Services | 2017 | Deployed | In Bitcoin Core | |
| 171 | Currency/exchange rate information API A common interface for requesting currency exchange rate information from a server. | Applications | 2017 | Closed | ||
| 172 | Define 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),… | Applications | 2025 | Draft | ||
| 173 | Base32 address format for native v0-16 witness outputs Bech32 — the bc1q… address format with strong error detection. | Applications | 2017 | Deployed | In Bitcoin Core | |
| 174 | Partially Signed Bitcoin Transaction Format PSBT: a standard file format for passing an unsigned transaction between wallets, hardware signers and coordinators. | Applications | 2017 | Deployed | In Bitcoin Core | |
| 175 | Pay 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… | Applications | 2017 | Closed | ||
| 176 | Bits Denomination “Bits” (100 satoshis) as a display unit. | Process / no layer | 2017 | Complete | In Bitcoin Core | |
| 177 | Redefine 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 layer | 2025 | Draft | ||
| 178 | Version Extended WIF An extension to the Wallet Import Format (WIF) to specify what kind of bitcoin address the private key corresponds to. | Applications | 2018 | Draft | ||
| 179 | Name for payment recipient identifiers This BIP proposes a new term for 'address' | Process / no layer | 2019 | Complete | Complete, awaiting adoption | |
| 180 | Block size/weight fraud proof A fraud proof that enables light clients to detect oversized (or overweight) blocks. | Peer Services | 2017 | Closed | ||
| 197 | Hashed 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… | Applications | 2019 | Draft | ||
| 199 | Hashed Time-Locked Contract transactions This BIP describes a script for generalized off-chain contract negotiation. | Applications | 2017 | Closed | ||
| 300 | Hashrate Escrows (Consensus layer)Drivechains Drivechain hashrate escrows: miners vote over months on sidechain withdrawals. Draft; never activated on Bitcoin. | Consensus (soft fork) | 2017 | Draft | ||
| 301 | Blind 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) | 2019 | Draft | ||
| 310 | Stratum 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… | Applications | 2018 | Draft | ||
| 320 | nVersion 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 layer | 2018 | Draft | ||
| 321 | URI Scheme This BIP proposes a URI scheme for describing Bitcoin payment instructions. | Applications | 2024 | Complete | Complete, awaiting adoption | |
| 322 | Generic Signed Message Format Generic signed messages that work for every address type, not just legacy ones. | Applications | 2018 | Complete | Complete, awaiting adoption | |
| 323 | 24 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 layer | 2026 | Draft | In Bitcoin Core | |
| 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. | Peer Services | 2019 | Deployed | In Bitcoin Core | |
| 325 | Signet Signet: a test network where blocks are signed by a set of keys, giving developers a stable, predictable playground. | Applications | 2019 | Complete | In Bitcoin Core | |
| 326 | Anti-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… | Applications | 2021 | Draft | ||
| 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. | Process / no layer | 2022 | Deployed | In Bitcoin Core | |
| 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… | Applications | 2024 | Complete | In Bitcoin Core | |
| 329 | Wallet 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. | Applications | 2022 | Draft | ||
| 330 | Transaction 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 Services | 2019 | Draft | ||
| 331 | Ancestor 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 Services | 2022 | Draft | ||
| 332 | Stale 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 Services | 2026 | Draft | ||
| 337 | Compressed 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/RPC | 2024 | Draft | ||
| 338 | Disable 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 Services | 2020 | Closed | ||
| 339 | WTXID-based transaction relay Relay transactions by wtxid (including the witness), fixing a class of relay problems after SegWit. | Peer Services | 2020 | Deployed | In Bitcoin Core | |
| 340 | Schnorr Signatures for secp256k1Taproot Schnorr signatures for secp256k1 — provably secure, linear and batch-verifiable. Taproot's signature scheme. | Process / no layer | 2020 | Deployed | Activated soft fork | |
| 341 | Taproot: 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) | 2020 | Deployed | Activated soft fork | |
| 342 | Validation of Taproot ScriptsTaproot Tapscript: the script rules inside Taproot, including OP_SUCCESS upgrade hooks for future opcodes. | Consensus (soft fork) | 2020 | Deployed | Activated soft fork | |
| 343 | Mandatory 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) | 2021 | Closed | ||
| 345 | OP_VAULTThe Covenant Zoo OP_VAULT: purpose-built vaults with a delay and recovery path. Closed. | Consensus (soft fork) | 2023 | Closed | ||
| 346 | OP_TXHASHThe Covenant Zoo OP_TXHASH: flexible hashing of parts of the spending transaction, a generalised CTV. Draft. | Consensus (soft fork) | 2024 | Draft | ||
| 347 | OP_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) | 2023 | Complete | Complete, awaiting adoption | |
| 348 | CHECKSIGFROMSTACKThe 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) | 2024 | Draft | ||
| 349 | OP_INTERNALKEYThe Covenant Zoo OP_INTERNALKEY: push the Taproot internal key onto the stack, saving bytes in covenant scripts. | Consensus (soft fork) | 2024 | Draft | ||
| 350 | Bech32m format for v1+ witness addresses Bech32m — the bc1p… address format for Taproot and future witness versions, fixing a Bech32 weakness. | Applications | 2020 | Deployed | In Bitcoin Core | |
| 351 | Private 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… | Applications | 2022 | Closed | ||
| 352 | Silent Payments Silent Payments: post one static address; every payment lands on a fresh, unlinkable output, with no interaction and no server. | Applications | 2023 | Complete | Complete, awaiting adoption | |
| 353 | DNS Payment Instructions DNS payment instructions: pay a human-readable name like ₿user@domain using DNSSEC-proved records. | Applications | 2024 | Complete | Complete, awaiting adoption | |
| 360 | Pay-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) | 2024 | Draft | ||
| 361 | Post 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) | 2026 | Draft | ||
| 370 | PSBT Version 2 PSBT version 2: a more flexible PSBT format; created by default by Bitcoin Core's PSBT RPCs from v32. | Applications | 2021 | Deployed | In Bitcoin Core | |
| 371 | Taproot Fields for PSBT Taproot fields for PSBT, so hardware and multisig wallets can sign Taproot. | Applications | 2021 | Deployed | In Bitcoin Core | |
| 372 | Pay-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… | Applications | 2022 | Draft | ||
| 373 | MuSig2 PSBT Fields MuSig2 fields for PSBT. | Applications | 2024 | Complete | In Bitcoin Core | |
| 374 | Discrete 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… | Applications | 2024 | Draft | ||
| 375 | Sending 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. | Applications | 2025 | Draft | ||
| 376 | Spending 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… | Applications | 2026 | Draft | ||
| 379 | Miniscript Miniscript: a structured language for Bitcoin scripts that wallets can analyse, compose and sign generically. | Applications | 2023 | Deployed | In Bitcoin Core | |
| 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. | Applications | 2021 | Deployed | In Bitcoin Core | |
| 381 | Non-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… | Applications | 2021 | Deployed | In Bitcoin Core | |
| 382 | Segwit 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… | Applications | 2021 | Deployed | In Bitcoin Core | |
| 383 | Multisig 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… | Applications | 2021 | Deployed | In Bitcoin Core | |
| 384 | combo() 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. | Applications | 2021 | Deployed | In Bitcoin Core | |
| 385 | raw() 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. | Applications | 2021 | Deployed | In Bitcoin Core | |
| 386 | tr() Output Script Descriptors tr() descriptors for Taproot outputs. | Applications | 2021 | Deployed | In Bitcoin Core | |
| 387 | Tapscript 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… | Applications | 2024 | Deployed | In Bitcoin Core | |
| 388 | Wallet Policies for Descriptor Wallets Wallet policies: a descriptor variant designed for hardware wallets to register and display multisig policies. | Applications | 2023 | Complete | Complete, awaiting adoption | |
| 389 | Multipath 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… | Applications | 2022 | Draft | ||
| 390 | musig() Descriptor Key Expression musig() descriptor key expressions (Bitcoin Core v30 parsing, v31 signing). | Applications | 2024 | Draft | In Bitcoin Core | |
| 391 | Binary 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… | Applications | 2026 | Closed | ||
| 392 | Silent 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… | Applications | 2026 | Draft | ||
| 393 | Output 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… | Applications | 2026 | Draft | ||
| 394 | rawtr() 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… | Applications | 2026 | Draft | ||
| 431 | Topology Restrictions for Pinning TRUC (v3) transactions: a topology rule that makes Lightning fee bumping resistant to pinning (Bitcoin Core v28). | Applications | 2024 | Draft | In Bitcoin Core | |
| 433 | Pay to Anchor (P2A) Pay to Anchor (P2A): a keyless anchor output anyone can use to bump fees via CPFP (Bitcoin Core v28). | Applications | 2025 | Draft | In Bitcoin Core | |
| 434 | Peer Feature Negotiation Peer feature negotiation for the P2P protocol (Bitcoin Core v32). | Peer Services | 2026 | Complete | In Bitcoin Core | |
| 440 | Varops Budget For Script Runtime Constraint A varops budget limiting script runtime, prerequisite for restoring disabled opcodes safely. Draft. | Consensus (soft fork) | 2026 | Draft | ||
| 441 | Restoration 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) | 2026 | Draft | ||
| 442 | OP_PAIRCOMMITThe Covenant Zoo OP_PAIRCOMMIT: commit to two stack items at once; part of LNHANCE. Draft. | Consensus (soft fork) | 2024 | Draft | ||
| 443 | OP_CHECKCONTRACTVERIFYThe Covenant Zoo OP_CHECKCONTRACTVERIFY (MATT): carry state into the next output, enabling vaults and fraud-proof protocols. Draft. | Consensus (soft fork) | 2025 | Draft | ||
| 446 | OP_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) | 2026 | Draft | ||
| 448 | Taproot-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) | 2026 | Draft | ||
| 449 | OP_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) | 2026 | Draft | ||
| 450 | Formosa—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… | Applications | 2026 | Draft | ||
| 451 | Dust 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.… | Applications | 2026 | Draft | ||
| 458 | Half-Aggregation of BIP 340 Signatures Half-aggregation of Schnorr signatures: n signatures in 32×(n+1) bytes instead of 64×n. | Applications | 2026 | Draft | ||
| 459 | DahLIAS fully aggregated signatures for secp256k1 DahLIAS: fully aggregate signatures across keys and messages into one 64-byte signature. | Applications | 2026 | Draft | ||
| 460 | CISA 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) | 2026 | Draft | ||
| 461 | Deterministic 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… | Applications | 2026 | Draft | In Bitcoin Core |
tools/parse_bips.py to refresh.171 sources cited on this page.