BIPs — Merged

BIP: 1 Title: BIP Purpose and Guidelines Authors: Amir Taaki <genjix@riseup.net>

BIP: 2 Title: BIP process, revised Authors: Luke Dashjr <luke+bip@dashjr.org>

This _Bitcoin Improvement Proposal (BIP)_ provides information about the preparation of BIPs and policies relating to the publication of BIPs. It replaces [BIP 2](bip-0002.mediawiki) with a streamlined process, and may be amended to address the evolving needs of the BIP process.

BIP: 8 Title: Version bits with lock-in by height Authors: Shaolin Fry <shaolinfry@protonmail.ch>

BIP: 9 Title: Version bits with timeout and delay Authors: Pieter Wuille <pieter.wuille@gmail.com>

BIP: 10 Layer: Applications Title: Multi-Sig Transaction Distribution

BIP: 11 Layer: Applications Title: M-of-N Standard Transactions

BIP: 12 Layer: Consensus (soft fork) Title: OP_EVAL

BIP: 13 Layer: Applications Title: Address Format for pay-to-script-hash

BIP: 14 Layer: Peer Services Title: Protocol Version and User Agent

BIP: 15 Layer: Applications Title: Aliases

BIP: 16 Layer: Consensus (soft fork) Title: Pay to Script Hash

BIP: 17 Layer: Consensus (soft fork) Title: OP_CHECKHASHVERIFY (CHV)

BIP: 18 Layer: Consensus (soft fork) Title: hashScriptCheck

BIP: 19 Layer: Applications Title: M-of-N Standard Transactions (Low SigOp)

This spent several months gathering feedback from the mailing list and from other advisors. This is hopefully polished enough to submit upstream. Let me know if you have any questions or feedback, and of course feel free to submit suggestions. Thank you for your time.

BIP-446 got merged, redirecting to bitcoin/bips repo.

This PR adds version 2 to the "Versions Requiring Inclusion" column (currently empty) for the `PSBT_GLOBAL_VERSION` field. See [BIP-370](https://github.com/theStack/bips/blob/master/bip-0370.mediawiki): https://github.com/bitcoin/bips/blob/2778442c21cef2290ae3e0c843d9f3179aa1cdd0/bip-0370.mediawiki?plain=1#L41

Mailing list thread at https://groups.google.com/g/bitcoindev/c/nOZim6FbuF8 --- Editor note: please post conceptual feedback and meta-commentary on the mailing list [thread](https://groups.google.com/g/bitcoindev/c/nOZim6FbuF8), and focus here on: - expert technical review of the specification - specific, concrete, helpful proposals for the other sections Please refrain from personal or heated commentary, trolling, pedantry, and repeating yourself. As this PR now has many comments, please on

Opening this here for wider discussion and feedback. edit: Probably need to add implementation section: https://github.com/instagibbs/bitcoin/tree/2025-07-op_templatehash

We propose a new BIP for Chain Code Delegation, a collaborative custody technique that involves privileged participants (delegatee) withholding BIP32 chain codes at key setup time from a delegator, and sharing only enough information for non‑privileged participants to provide their signature. For non-blinded signing, the delegatee derives a per‑spend scalar tweak t from the (withheld) chain code, the delegator computes the child key (x+t, P+tG), and produces a standard signature over the transa

The checksum calculation should be consistent in all implementations.

This introduces test vectors for BIP54. There is one set of vectors per each of the 4 mitigations. The vectors were generated using the BIP54 implementation against Bitcoin Inquisition available [here](https://github.com/bitcoin-inquisition/bitcoin/pull/99), as well as a custom miner as a Bitcoin Core unit test available [here](https://github.com/darosior/bitcoin/commits/bip54_miner/). Documentation is provided with more details about each set of test vectors and describing how to use them.