| 1 | BIP Purpose and Guidelines | Process | Closed | None yet |
| 2 | BIP process, revised | Process | Closed | 2 claims- As of block 976,761 (20 November 2026), BIP 2, "BIP process, revised", has Status Closed, and its preamble names BIP 3 as its replacement. BIP 2 had itself replaced BIP 1, the original BIP process document.
- BIP 3 supersedes BIP 2's Standards Track type, used for changes affecting most or all Bitcoin implementations, with the similar Specification type. On BIP 3's activation, Standards Track BIPs and eligible Informational BIPs are assigned the Specification type.
|
| 3 | Updated BIP Process | Process | Deployed | 20 claims- Anyone may submit a BIP: BIP 3, the document that sets out the BIP process, states that BIPs may be submitted by anyone, provided the content is of high quality.
- As of block 976,761 (20 November 2026), BIP 3, "Updated BIP Process", is the process document in force for the bitcoin/bips repository. Its preamble gives Status Deployed and Type Process, and the text says it replaces BIP 2 as the guideline for the BIP process.
- Whether a wallet or node follows a given BIP depends on that software, not on the BIP. Bitcoin Core, for example, keeps a list of the BIPs it implements in doc/bips.md, and as of its master branch on 20 November 2026 that list includes BIP 32 but not BIP 39, the mnemonic seed phrase standard.
- In BIP 3, the Closed status marks BIPs that are only of historical significance. Closed BIPs are not deleted, and if a Draft BIP appears stalled for a year, anyone may propose that its status be changed to Closed.
- Under BIP 3, any community member may request that a Complete BIP advance to Deployed by showing evidence that the BIP is in active use, and a Deployed BIP is considered final.
- BIP Editors, as BIP 3 describes them, check editorial criteria for a new BIP, such as prior discussion on the Bitcoin Development Mailing List and correct Layer and Type headers, then assign a number and merge. BIP 3 states that editors do not evaluate whether a proposal is likely to be adopted.
- BIP 3 cut the number of BIP status values from nine under BIP 2 to four: Draft, Complete, Deployed and Closed. A BIP in Complete status can only move to Deployed or Closed.
- A BIP's Layer header, when present, names the part of Bitcoin the BIP applies to, using the classification in BIP 123: the Consensus layer, the Peer Services layer, the API/RPC layer and the Applications layer.
- BIP 3 asks authors to present a first sketch of a proposal to the Bitcoin Development Mailing List and to avoid opening a pull request in the bitcoin/bips repository with a BIP draft out of the blue.
- According to BIP 3, the document that sets out the BIP process, no formal or informal decision body governs Bitcoin development or decides whether BIPs are adopted.
- BIP 3 states that BIPs do not define what Bitcoin is, that individual BIPs do not represent Bitcoin community consensus, and that a BIP is a personal recommendation by its authors to the Bitcoin community.
- A BIP number does not mean Bitcoin adopted a proposal. The bitcoin/bips README says publishing a BIP there shows it is in scope and met formal criteria, but not that it is a good idea, has community consensus or is about to be adopted.
- Authors do not choose their own BIP numbers. Under BIP 3, only BIP Editors may assign a number, and a number counts as assigned only after a BIP Editor has announced it publicly in the proposal's pull request to the bitcoin/bips repository.
- Process BIPs follow a different rule for becoming Deployed: under BIP 3, a Process BIP moves from Complete to Deployed when it reaches rough consensus on the Bitcoin Development Mailing List, after its advancement has been open to discussion there for at least one month.
- Under BIP 3, the bitcoin/bips repository does not track sentiment about proposals or their adoption beyond whether a BIP is in active use. BIP 3 encourages individual Bitcoin projects to publish lists of the BIPs they implement.
- BIP 3 notes that some BIPs may never be adopted, some may be adopted by one or more Bitcoin clients or related software, and some may end up changing the consensus rules the Bitcoin ecosystem jointly enforces.
- BIP 3 supersedes BIP 2's Standards Track type, used for changes affecting most or all Bitcoin implementations, with the similar Specification type. On BIP 3's activation, Standards Track BIPs and eligible Informational BIPs are assigned the Specification type.
- BIP 3 defines three BIP types: a Specification BIP sets technical rules for a new feature or for interoperability between implementations, an Informational BIP describes a design issue or gives guidelines or information, and a Process BIP describes or changes a process surrounding Bitcoin.
- The bitcoin/bips repository README states that acceptance and adoption of a BIP ultimately rest with Bitcoin users, and BIP 3 says that once a BIP is Complete it is up to the Bitcoin community to evaluate, adopt, ignore or reject it.
- A Bitcoin Improvement Proposal (BIP) is an improvement proposal for Bitcoin. BIP 3, the process document, says most BIPs give a concise, self-contained technical description of one new concept, feature or standard.
|
| 8 | Version bits with lock-in by height | Informational | Complete | 1 claim |
| 9 | Version bits with timeout and delay | Informational | Deployed | 1 claim |
| 10 | Multi-Sig Transaction Distribution | Applications | Closed | None yet |
| 11 | M-of-N Standard Transactions | Applications | Deployed | None yet |
| 12 | OP_EVAL | Consensus (soft fork) | Closed | None yet |
| 13 | Address Format for pay-to-script-hash | Applications | Deployed | None yet |
| 14 | Protocol Version and User Agent | Peer Services | Deployed | None yet |
| 15 | Aliases | Applications | Closed | None yet |
| 16 | Pay to Script Hash | Consensus (soft fork) | Deployed | None yet |
| 17 | OP_CHECKHASHVERIFY (CHV) | Consensus (soft fork) | Closed | None yet |
| 18 | hashScriptCheck | Consensus (soft fork) | Complete | None yet |
| 19 | M-of-N Standard Transactions (Low SigOp) | Applications | Closed | None yet |
| 20 | URI Scheme | Applications | Closed | None yet |
| 21 | URI Scheme | Applications | Closed | None yet |
| 22 | getblocktemplate - Fundamentals | API/RPC | Deployed | None yet |
| 23 | getblocktemplate - Pooled Mining | API/RPC | Deployed | None yet |
| 30 | Duplicate transactions | Consensus (soft fork) | Deployed | 2 claims |
| 31 | Pong message | Peer Services | Deployed | None yet |
| 32 | Hierarchical Deterministic Wallets | Applications | Deployed | None yet |
| 33 | Stratized Nodes | Peer Services | Closed | None yet |
| 34 | Block v2, Height in Coinbase | Consensus (soft fork) | Deployed | 2 claims |
| 35 | mempool message | Peer Services | Deployed | None yet |
| 36 | Custom Services | Peer Services | Closed | None yet |
| 37 | Connection Bloom filtering | Peer Services | Deployed | None yet |
| 38 | Passphrase-protected private key | Applications | Deployed | None yet |
| 39 | Mnemonic code for generating deterministic keys | Applications | Deployed | None yet |
| 40 | Stratum wire protocol | API/RPC | BIP number allocated | None yet |
| 41 | Stratum mining protocol | API/RPC | BIP number allocated | None yet |
| 42 | A finite monetary supply for Bitcoin | Consensus (soft fork) | Deployed | 1 claim |
| 43 | Purpose Field for Deterministic Wallets | Applications | Deployed | None yet |
| 44 | Multi-Account Hierarchy for Deterministic Wallets | Applications | Deployed | None yet |
| 45 | Structure for Deterministic P2SH Multisignature Wallets | Applications | Complete | None yet |
| 46 | Address Scheme for Timelocked Fidelity Bonds | Applications | Draft | None yet |
| 47 | Reusable Payment Codes for Hierarchical Deterministic Wallets | Applications | Deployed | None yet |
| 48 | Multi-Script Hierarchy for Multi-Sig Wallets | Applications | Deployed | None yet |
| 49 | Derivation scheme for P2WPKH-nested-in-P2SH based accounts | Applications | Deployed | None yet |
| 50 | March 2013 Chain Fork Post-Mortem | Informational | Deployed | None yet |
| 52 | Durable, Low Energy Bitcoin PoW | Consensus (hard fork) | Closed | None yet |
| 53 | Disallow 64-byte transactions | Consensus (soft fork) | Draft | None yet |
| 54 | Consensus Cleanup | Consensus (soft fork) | Complete | 3 claims- BIP 34 does not rule out every duplicate coinbase: some early coinbases could be replayed in future blocks, so Bitcoin Core enforces BIP 30 checks again from block 1,983,702 on. BIP 54 (consensus cleanup), a proposed soft fork whose BIP status is Complete as of 20 November 2026, specifies that each coinbase's nLockTime equal the block height minus 1.
- BIP 54 proposes that the first block of each 2,016-block difficulty period (height divisible by 2,016) must have a timestamp no earlier than 7,200 seconds (two hours) before the timestamp of the block immediately preceding it, which the BIP gives as its fix for the timewarp attack.
- BIP 54 (Consensus Cleanup) states that the timewarp bug lets an attacker with a majority of Bitcoin's hashrate arbitrarily lower mining difficulty by manipulating block timestamps, and that in the worst case the attacker can bring difficulty to its minimum within 38 days.
|
| 60 | Fixed Length "version" Message (Relay-Transactions Field) | Peer Services | Closed | None yet |
| 61 | Reject P2P message | Peer Services | Deployed | None yet |
| 62 | Dealing with malleability | Consensus (soft fork) | Closed | None yet |
| 63 | Stealth Addresses | Applications | BIP number allocated | None yet |
| 64 | getutxo message | Peer Services | Closed | None yet |
| 65 | OP_CHECKLOCKTIMEVERIFY | Consensus (soft fork) | Deployed | None yet |
| 66 | Strict DER signatures | Consensus (soft fork) | Deployed | None yet |
| 67 | Deterministic Pay-to-script-hash multi-signature addresses through public key sorting | Applications | Complete | None yet |
| 68 | Relative lock-time using consensus-enforced sequence numbers | Consensus (soft fork) | Deployed | None yet |
| 69 | Lexicographical Indexing of Transaction Inputs and Outputs | Applications | Complete | None yet |
| 70 | Payment Protocol | Applications | Deployed | None yet |
| 71 | Payment Protocol MIME types | Applications | Deployed | None yet |
| 72 | bitcoin: uri extensions for Payment Protocol | Applications | Deployed | None yet |
| 73 | Use "Accept" header for response type negotiation with Payment Request URLs | Applications | Deployed | None yet |
| 74 | Allow zero value OP_RETURN in Payment Protocol | Applications | Closed | None yet |
| 75 | Out of Band Address Exchange using Payment Protocol Encryption | Applications | Deployed | None yet |
| 77 | Async Payjoin | Applications | Draft | None yet |
| 78 | A Simple Payjoin Proposal | Applications | Deployed | None yet |
| 79 | Bustapay :: a practical coinjoin protocol | Applications | Closed | None yet |
| 80 | Hierarchy for Non-Colored Voting Pool Deterministic Multisig Wallets | Informational | Closed | None yet |
| 81 | Hierarchy for Colored Voting Pool Deterministic Multisig Wallets | Informational | Closed | None yet |
| 83 | Dynamic Hierarchical Deterministic Key Trees | Applications | Closed | None yet |
| 84 | Derivation scheme for P2WPKH based accounts | Applications | Deployed | None yet |
| 85 | Deterministic Entropy From BIP32 Keychains | Applications | Deployed | None yet |
| 86 | Key Derivation for Single Key P2TR Outputs | Applications | Deployed | None yet |
| 87 | Hierarchy for Deterministic Multisig Wallets | Applications | Complete | None yet |
| 88 | Hierarchical Deterministic Path Templates | Applications | Complete | None yet |
| 89 | Chain Code Delegation | Applications | Deployed | None yet |
| 90 | Buried Deployments | Informational | Deployed | None yet |
| 91 | Reduced threshold Segwit MASF | Consensus (soft fork) | Deployed | None yet |
| 93 | codex32: Checksummed SSSS-aware BIP32 seeds | Applications | Draft | None yet |
| 94 | Testnet 4 | Applications | Deployed | 1 claim |
| 95 | Testnet 5 | Applications | Deployed | None yet |
| 98 | Fast Merkle Trees | Consensus (soft fork) | Draft | None yet |
| 99 | Motivation and deployment of consensus rule changes ([soft/hard]forks) | Informational | Closed | None yet |
| 100 | Dynamic maximum block size by miner vote | Consensus (hard fork) | Closed | None yet |
| 101 | Increase maximum block size | Consensus (hard fork) | Closed | None yet |
| 102 | Block size increase to 2MB | Consensus (hard fork) | Closed | None yet |
| 103 | Block size following technological growth | Consensus (hard fork) | Closed | None yet |
| 104 | 'Block75' - Max block size like difficulty | Consensus (hard fork) | Closed | None yet |
| 105 | Consensus based block size retargeting algorithm | Consensus (hard fork) | Closed | None yet |
| 106 | Dynamically Controlled Bitcoin Block Size Max Cap | Consensus (hard fork) | Closed | None yet |
| 107 | Dynamic limit on the block size | Consensus (hard fork) | Closed | None yet |
| 109 | Two million byte size limit with sigop and sighash limits | Consensus (hard fork) | Closed | None yet |
| 110 | Reduced Data Temporary Softfork | Consensus (soft fork) | Closed | None yet |
| 111 | NODE_BLOOM service bit | Peer Services | Deployed | None yet |
| 112 | CHECKSEQUENCEVERIFY | Consensus (soft fork) | Deployed | None yet |
| 113 | Median time-past as endpoint for lock-time calculations | Consensus (soft fork) | Deployed | None yet |
| 114 | Merkelized Abstract Syntax Tree | Consensus (soft fork) | Closed | None yet |
| 115 | Generic anti-replay protection using Script | Consensus (soft fork) | Closed | None yet |
| 116 | MERKLEBRANCHVERIFY | Consensus (soft fork) | Draft | None yet |
| 117 | Tail Call Execution Semantics | Consensus (soft fork) | Draft | None yet |
| 118 | SIGHASH_ANYPREVOUT for Taproot Scripts | Consensus (soft fork) | Draft | None yet |
| 119 | CHECKTEMPLATEVERIFY | Consensus (soft fork) | Draft | None yet |
| 120 | Proof of Payment | Applications | Closed | None yet |
| 121 | Proof of Payment URI scheme | Applications | Closed | None yet |
| 122 | URI scheme for Blockchain references / exploration | Applications | Draft | None yet |
| 123 | BIP Classification | Process | Deployed | 1 claim |
| 124 | Hierarchical Deterministic Script Templates | Applications | Closed | None yet |
| 125 | Opt-in Full Replace-by-Fee Signaling | Applications | Deployed | 1 claim |
| 126 | Best Practices for Heterogeneous Input Script Transactions | Informational | Draft | None yet |
| 127 | Simple Proof-of-Reserves Transactions | Applications | Complete | None yet |
| 128 | Timelock-Recovery Storage Format | Applications | Draft | None yet |
| 129 | Bitcoin Secure Multisig Setup (BSMS) | Applications | Complete | None yet |
| 130 | sendheaders message | Peer Services | Deployed | None yet |
| 131 | "Coalescing Transaction" Specification (wildcard inputs) | Consensus (hard fork) | Closed | None yet |
| 132 | Committee-based BIP Acceptance Process | Process | Closed | None yet |
| 133 | feefilter message | Peer Services | Deployed | None yet |
| 134 | Flexible Transactions | Consensus (hard fork) | Closed | None yet |
| 135 | Generalized version bits voting | Informational | Closed | None yet |
| 136 | Bech32 Encoded Tx Position References | Applications | Draft | None yet |
| 137 | Signatures of Messages using Private Keys | Applications | Deployed | None yet |
| 138 | Compact Encryption Scheme for Non-seed Wallet Data | Applications | Draft | None yet |
| 139 | Wallet Metadata Export Format | Applications | Draft | None yet |
| 140 | Normalized TXID | Consensus (soft fork) | Closed | None yet |
| 141 | Segregated Witness (Consensus layer) | Consensus (soft fork) | Deployed | 15 claims- Segregated witness (BIP 141) was deployed with BIP 9 version bits on bit 1, released in Bitcoin Core 0.13.1 with a signaling start of 15 November 2016, and its rules have been active on mainnet since block 481,824.
- Bitcoin fee rates are usually quoted in satoshis per virtual byte (sat/vB). BIP 141 defines a transaction's virtual size as its weight divided by 4, rounded up, so the same fee rate costs a larger transaction more sats in total.
- Bitcoin blocks have limited space: a consensus rule caps each block at 4,000,000 weight units. Because more transactions can be waiting than fit in the next block, users attach fees to compete for inclusion, and transactions paying higher fee rates are generally mined first.
- SegWit was deployed with BIP 9 version bits on bit 1, with a mainnet signaling window from 15 November 2016 to 15 November 2017: if 95% of blocks in a 2,016-block retarget period signaled, it would lock in, and activate 2,016 blocks later.
- Since SegWit, a Bitcoin block's size limit is expressed in weight units: weight is the block's size without witness data times 3 plus its full size, and a valid block may weigh at most 4,000,000 weight units (BIP 141).
- BIP 141 presents SegWit's malleability fix as what allows chains of unconfirmed transactions to be built without trusting the counterparty, a building block it names for payment networks such as the Lightning Network.
- Because a SegWit transaction's signatures sit in the witness, which the txid does not cover, changing how the transaction was signed no longer changes its txid; BIP 141 states this prevents involuntary malleability for any type of script as long as all inputs are signed.
- Under BIP 141 every transaction has two identifiers: the txid, the double SHA-256 of the serialization without witness data (unchanged from before SegWit), and the wtxid, the double SHA-256 of the serialization that includes the witness.
- A version 0 witness program with a 20-byte program is a pay-to-witness-public-key-hash (P2WPKH) output and one with a 32-byte program is a pay-to-witness-script-hash (P2WSH) output; Bitcoin Core checks these sizes in VerifyWitnessProgram in src/script/interpreter.cpp.
- BIP 141 defines a transaction's virtual size, measured in vbytes, as its transaction weight divided by 4 and rounded up to the next integer.
- Segregated Witness (SegWit) is a Bitcoin soft fork, activated in 2017, that moves the signature data of a transaction (its "witness") into a separate structure that blocks commit to apart from the transaction data that the transaction ID covers.
- A SegWit block commits to its witness data through a commitment in an output script of its coinbase transaction; Bitcoin Core verifies it in CheckWitnessMalleation in src/validation.cpp and rejects a mismatching block with the reason "bad-witness-merkle-match".
- In BIP 141, an output script (or P2SH redeem script) made of a 1-byte push opcode from OP_0 to OP_16 followed by a single direct data push of 2 to 40 bytes has a special meaning: the first push is the version byte and the pushed bytes are the witness program.
- BIP 141 reserves witness versions 1 to 16 for future extensions and leaves their programs uninterpreted, so nodes that predate a new version accept its spends; later soft forks can then give a version new rules without breaking older nodes.
- Since segregated witness (BIP 141), the data that unlocks a Bitcoin output can sit in a separate witness structure that the transaction id does not cover; Bitcoin Core stores it with each input as scriptWitness, beside the older scriptSig.
|
| 142 | Address Format for Segregated Witness | Applications | Closed | None yet |
| 143 | Transaction Signature Verification for Version 0 Witness Program | Consensus (soft fork) | Deployed | 2 claims |
| 144 | Segregated Witness (Peer Services) | Peer Services | Deployed | 1 claim |
| 145 | getblocktemplate Updates for Segregated Witness | API/RPC | Deployed | 1 claim |
| 146 | Dealing with signature encoding malleability | Consensus (soft fork) | Closed | None yet |
| 147 | Dealing with dummy stack element malleability | Consensus (soft fork) | Deployed | None yet |
| 148 | Mandatory activation of segwit deployment | Consensus (soft fork) | Deployed | 1 claim |
| 149 | Segregated Witness (second deployment) | Consensus (soft fork) | Closed | None yet |
| 150 | Peer Authentication | Peer Services | Closed | None yet |
| 151 | Peer-to-Peer Communication Encryption | Peer Services | Closed | None yet |
| 152 | Compact Block Relay | Peer Services | Deployed | None yet |
| 154 | Rate Limiting via peer specified challenges | Peer Services | Closed | None yet |
| 155 | addrv2 message | Peer Services | Deployed | None yet |
| 156 | Dandelion - Privacy Enhancing Routing | Peer Services | Closed | None yet |
| 157 | Client Side Block Filtering | Peer Services | Deployed | None yet |
| 158 | Compact Block Filters for Light Clients | Peer Services | Deployed | None yet |
| 159 | NODE_NETWORK_LIMITED service bit | Peer Services | Deployed | None yet |
| 171 | Currency/exchange rate information API | Applications | Closed | None yet |
| 172 | Define Bitcoin Subunits as Satoshis | Applications | Draft | None yet |
| 173 | Base32 address format for native v0-16 witness outputs | Applications | Deployed | 3 claims |
| 174 | Partially Signed Bitcoin Transaction Format | Applications | Deployed | None yet |
| 175 | Pay to Contract Protocol | Applications | Closed | None yet |
| 176 | Bits Denomination | Informational | Complete | None yet |
| 177 | Redefine Bitcoin's Base Unit | Informational | Draft | None yet |
| 178 | Version Extended WIF | Applications | Draft | None yet |
| 179 | Name for payment recipient identifiers | Informational | Complete | None yet |
| 180 | Block size/weight fraud proof | Peer Services | Closed | None yet |
| 197 | Hashed Time-Locked Collateral Contract | Applications | Draft | None yet |
| 199 | Hashed Time-Locked Contract transactions | Applications | Closed | None yet |
| 300 | Hashrate Escrows (Consensus layer) | Consensus (soft fork) | Draft | None yet |
| 301 | Blind Merged Mining (Consensus layer) | Consensus (soft fork) | Draft | None yet |
| 310 | Stratum protocol extensions | Applications | Draft | None yet |
| 320 | nVersion bits for general purpose use | Specification | Draft | None yet |
| 321 | URI Scheme | Applications | Complete | None yet |
| 322 | Generic Signed Message Format | Applications | Complete | None yet |
| 323 | 24 nVersion bits for general purpose use | Specification | Draft | None yet |
| 324 | Version 2 P2P Encrypted Transport Protocol | Peer Services | Deployed | None yet |
| 325 | Signet | Applications | Complete | None yet |
| 326 | Anti-fee-sniping in taproot transactions | Applications | Draft | None yet |
| 327 | MuSig2 for BIP340-compatible Multi-Signatures | Informational | Deployed | 1 claim |
| 328 | Derivation Scheme for MuSig2 Aggregate Keys | Applications | Complete | None yet |
| 329 | Wallet Labels Export Format | Applications | Draft | None yet |
| 330 | Transaction announcements reconciliation | Peer Services | Draft | None yet |
| 331 | Ancestor Package Relay | Peer Services | Draft | None yet |
| 332 | Stale Tip Relay | Peer Services | Draft | None yet |
| 333 | BIP324 One-Byte Message Type ID Alias Assignment | Peer Services | Draft | None yet |
| 337 | Compressed Transactions | API/RPC | Draft | None yet |
| 338 | Disable transaction relay message | Peer Services | Closed | None yet |
| 339 | WTXID-based transaction relay | Peer Services | Deployed | None yet |
| 340 | Schnorr Signatures for secp256k1 | Specification | Deployed | 3 claims |
| 341 | Taproot: SegWit version 1 spending rules | Consensus (soft fork) | Deployed | 14 claims- The Taproot soft fork activated on mainnet at block 709,632 through Speedy Trial, a variation of BIP 9 version bits released in Bitcoin Core 0.21.1, with a lock-in threshold of 1,815 of 2,016 blocks (90%) and a minimum activation height of block 709,632.
- Taproot (BIP 341) defines rules for SegWit witness version 1: a Taproot output is a native SegWit output with witness version 1 and a 32-byte program, which Bitcoin Core checks in VerifyWitnessProgram.
- Taproot activated on Bitcoin mainnet at block 709,632, which was mined on 14 November 2021 with a block timestamp of 05:15:27 UTC.
- In a Taproot script path spend, the last witness element is the control block: 33 bytes plus 32 bytes for each Merkle path node, and Bitcoin Core accepts at most 128 path nodes, which limits a script tree to a depth of 128.
- BIP 341 chooses between the two ways of spending a Taproot output by counting witness elements after removing any annex: exactly one element means a key path spend, and two or more mean a script path spend.
- When a Taproot output is spent with its key path (a signature for the output's public key), the spend does not reveal whether any alternative script conditions existed for that output.
- A Taproot key path spend reveals no script: its witness carries a single Schnorr signature, checked against the 32-byte public key already in the output being spent.
- A Taproot output controlled by several signers through key aggregation, such as MuSig2 (BIP 327), can be spent with one aggregate key and one signature, so on chain it is indistinguishable from a single-signer Taproot output.
- For a Taproot output with a script tree, the output key is an internal public key tweaked with the tree's Merkle root, and Bitcoin Core checks a script path spend in VerifyTaprootCommitment by recomputing that root and verifying the tweak.
- When a Taproot output is spent through one of its committed scripts, only that script is published on chain and the other committed scripts stay hidden, though the spend does show that a script path existed and that the key path was not used.
- Each leaf of a Taproot script tree pairs a script with a leaf version, so later soft forks can introduce new script versions; Tapscript as defined in BIP 342 uses leaf version 0xc0.
- Taproot was activated with Speedy Trial, a variant of BIP 9 version bits signaling: if 90% of blocks (1,815 of 2,016) in a retarget period signaled on bit 2 between 24 April and 11 August 2021, Taproot would lock in and then activate no earlier than block 709,632.
- Taproot is a soft fork upgrade to Bitcoin, active since November 2021, that adds a new kind of output whose coins can be spent either with a single signature or by revealing one of several spending conditions committed to in advance.
- BIP 341, the main Taproot specification, states that its aim is to improve the privacy, efficiency and flexibility of Bitcoin's scripting capabilities.
|
| 342 | Validation of Taproot Scripts | Consensus (soft fork) | Deployed | 4 claims- BIP 342 Tapscript disables OP_CHECKMULTISIG and OP_CHECKMULTISIGVERIFY and adds OP_CHECKSIGADD (opcode 0xba), which checks one signature and adds the result to a running count, so threshold scripts check signatures one at a time.
- BIP 342 renames opcode numbers 80, 98, 126 to 129, 131 to 134, 137, 138, 141, 142, 149 to 153 and 187 to 254 as OP_SUCCESSx: if a Tapscript contains any of them, validation succeeds without applying the other rules, which BIP 342 describes as a mechanism to upgrade the Script system.
- BIP 342 removes two limits of earlier Bitcoin script for Tapscript: the maximum script size of 10,000 bytes and the limit of 201 non-push opcodes per script.
- The Taproot soft fork consists of three BIPs deployed together: BIP 340 for Schnorr signatures, BIP 341 for the spending rules of SegWit version 1 outputs, and BIP 342 for Tapscript, the script language used inside Taproot.
|
| 343 | Mandatory activation of taproot deployment | Consensus (soft fork) | Closed | None yet |
| 345 | OP_VAULT | Consensus (soft fork) | Closed | None yet |
| 346 | OP_TXHASH | Consensus (soft fork) | Draft | None yet |
| 347 | OP_CAT in Tapscript | Consensus (soft fork) | Complete | None yet |
| 348 | CHECKSIGFROMSTACK | Consensus (soft fork) | Draft | None yet |
| 349 | OP_INTERNALKEY | Consensus (soft fork) | Draft | None yet |
| 350 | Bech32m format for v1+ witness addresses | Applications | Deployed | 3 claims |
| 351 | Private Payments | Applications | Closed | None yet |
| 352 | Silent Payments | Applications | Complete | None yet |
| 353 | DNS Payment Instructions | Applications | Complete | None yet |
| 360 | Pay-to-Merkle-Root (P2MR) | Consensus (soft fork) | Draft | None yet |
| 361 | Post Quantum Migration and Legacy Signature Sunset | Consensus (soft fork) | Draft | None yet |
| 370 | PSBT Version 2 | Applications | Deployed | None yet |
| 371 | Taproot Fields for PSBT | Applications | Deployed | None yet |
| 372 | Pay-to-contract tweak fields for PSBT | Applications | Draft | None yet |
| 373 | MuSig2 PSBT Fields | Applications | Complete | None yet |
| 374 | Discrete Log Equality Proofs | Applications | Draft | None yet |
| 375 | Sending Silent Payments with PSBTs | Applications | Draft | None yet |
| 376 | Spending Silent Payment outputs with PSBTs | Applications | Draft | None yet |
| 379 | Miniscript | Applications | Deployed | None yet |
| 380 | Output Script Descriptors General Operation | Applications | Deployed | None yet |
| 381 | Non-Segwit Output Script Descriptors | Applications | Deployed | None yet |
| 382 | Segwit Output Script Descriptors | Applications | Deployed | None yet |
| 383 | Multisig Output Script Descriptors | Applications | Deployed | None yet |
| 384 | combo() Output Script Descriptors | Applications | Deployed | None yet |
| 385 | raw() and addr() Output Script Descriptors | Applications | Deployed | None yet |
| 386 | tr() Output Script Descriptors | Applications | Deployed | None yet |
| 387 | Tapscript Multisig Output Script Descriptors | Applications | Deployed | None yet |
| 388 | Wallet Policies for Descriptor Wallets | Applications | Complete | None yet |
| 389 | Multipath Descriptor Key Expressions | Applications | Draft | None yet |
| 390 | musig() Descriptor Key Expression | Applications | Draft | None yet |
| 391 | Binary Output Descriptors | Applications | Closed | None yet |
| 392 | Silent Payment Output Script Descriptors | Applications | Draft | None yet |
| 393 | Output Script Descriptor Annotations | Applications | Draft | None yet |
| 394 | rawtr() Output Script Descriptors | Applications | Draft | None yet |
| 431 | Topology Restrictions for Pinning | Applications | Draft | 2 claims |
| 433 | Pay to Anchor (P2A) | Applications | Draft | None yet |
| 434 | Peer Feature Negotiation | Peer Services | Complete | None yet |
| 440 | Varops Budget For Script Runtime Constraint | Consensus (soft fork) | Draft | None yet |
| 441 | Restoration of disabled script (Tapleaf 0xC2) | Consensus (soft fork) | Draft | None yet |
| 442 | OP_PAIRCOMMIT | Consensus (soft fork) | Draft | None yet |
| 443 | OP_CHECKCONTRACTVERIFY | Consensus (soft fork) | Draft | None yet |
| 446 | OP_TEMPLATEHASH | Consensus (soft fork) | Draft | None yet |
| 448 | Taproot-native (Re)bindable Transactions | Consensus (soft fork) | Draft | None yet |
| 449 | OP_TWEAKADD - x-only key tweak addition | Consensus (soft fork) | Draft | None yet |
| 450 | Formosa, Seed encoding by themed mnemonic stories | Applications | Draft | None yet |
| 451 | Dust UTXO Disposal Protocol | Applications | Draft | None yet |
| 458 | Half-Aggregation of BIP 340 Signatures | Applications | Draft | None yet |
| 459 | DahLIAS fully aggregated signatures for secp256k1 | Applications | Draft | None yet |
| 460 | CISA for Taproot Key Path Spends in SegWit v2 | Consensus (soft fork) | Draft | None yet |
| 461 | Deterministic ECDSA Signatures | Applications | Draft | None yet |