BIPs bitcoin improvement proposals

325 - Signet

BIP: 325 source Layer: Applications Title: Signet Authors: Karl-Johan Alm Anthony Towns Status: Complete Type: Specification Assigned: 2019-03-20 License: CC0-1.0 Table of ContentsAbstractMotivationSpecificationMinimum DifficultyGenesis Block and Message StartGenesis BlockMessage StartCompatibilityReference implementationReferencesCopyright Abstract A new type of test network where signatures are used in addition to proof of work for block progress, enabling much better coordination and robustness (be reliably unreliable), for persistent, longer-term testing scenarios involving multiple independent parties. Motivation Testnet is a great place to try out new things without risking real money, but it is notoriously unreliable. Huge block reorgs, long gaps in between blocks being mined or sudden bursts of blocks in rapid succession mean that realistic testing of software, especially involving multiple independent parties running software over an extended perio...

434 - Peer Feature Negotiation

BIP: 434 source Layer: Peer Services Title: Peer Feature Negotiation Authors: Anthony Towns Status: Draft Type: Specification Assigned: 2026-01-14 License: BSD-2-Clause Discussion: 2025-12-19: https://gnusha.org/pi/bitcoindev/aUUXLgEUCgGb122o@erisian.com.au/T/#u 2020-08-21: https://gnusha.org/pi/bitcoindev/20200821023647.7eat4goqqrtaqnna@erisian.com.au/ Version: 0.1.0 Abstract This BIP defines a peer-to-peer (P2P) message that can be used for announcements and negotiation related to support of new peer-to-peer features. Motivation Historically, new peer-to-peer protocol changes have been tied to bumping the protocol version, so that nodes know to only attempt feature negotiation with peers that support the feature. Coordinating the protocol version across implementations, when different clients may have different priorities for features to implement, is an unnecessary burden in the upgrade process for P2P features that do not require universal support. A...

118 - SIGHASH_ANYPREVOUT for Taproot Scripts

BIP: 118 source Layer: Consensus (soft fork) Title: SIGHASH_ANYPREVOUT for Taproot Scripts Authors: Christian Decker Anthony Towns Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0118 Status: Draft Type: Specification Assigned: 2017-02-28 License: BSD-3-Clause Requires: 340, 341, 342 Table of ContentsIntroductionAbstractCopyrightMotivationSpecificationRules for signature opcodesPublic keySignature messageSecuritySignature replayMalleabilityPrivacy considerationsRationaleDeploymentBackwards compatibilityRevisionsAcknowledgements Introduction Abstract This BIP describes a new type of public key for tapscript (BIP 342) transactions. It allows signatures for these public keys to not commit to the exact UTXO being spent. This enables dynamic binding of transactions to different UTXOs, provided they have compatible scripts. Copyright This document is licensed under the 3-clause BSD license. Motivation Of...

342 - Validation of Taproot Scripts

BIP: 342 source Layer: Consensus (soft fork) Title: Validation of Taproot Scripts Authors: Pieter Wuille Jonas Nick Anthony Towns Status: Deployed Type: Specification Assigned: 2020-01-19 License: BSD-3-Clause Discussion: 2019-05-06: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-May/016914.html [bitcoin-dev] Taproot proposal Requires: 340, 341 Table of ContentsIntroductionAbstractCopyrightMotivationDesignSpecificationScript executionRules for signature opcodesCommon Signature Message ExtensionSignature validationResource limitsRationaleDeploymentExamplesAcknowledgements Introduction Abstract This document specifies the semantics of the initial scripting system under BIP341. Copyright This document is licensed under the 3-clause BSD license. Motivation BIP341 proposes improvements to just the script structure, but some of its goals are incompatible with the semantics of certain opcodes within the scripting language itself. W...

341 - Taproot

BIP: 341 source Layer: Consensus (soft fork) Title: Taproot: SegWit version 1 spending rules Authors: Pieter Wuille Jonas Nick Anthony Towns Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0341 Status: Deployed Type: Specification Assigned: 2020-01-19 License: BSD-3-Clause Discussion: 2019-05-06: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-May/016914.html [bitcoin-dev] Taproot proposal 2019-10-09: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-October/017378.html [bitcoin-dev] Taproot updates Requires: 340 Table of ContentsIntroductionAbstractCopyrightMotivationDesignSpecificationScript validation rulesSignature validation rulesCommon signature messageTaproot key path spending signature validationConstructing and spending Taproot outputsSecurityTest vectorsRationaleDeploymentBackwards compatibilityAcknowledgements Introduction Abstract This d...