328 - Derivation Scheme for MuSig2 Aggregate Keys
BIP: 328 source Layer: Applications Title: Derivation Scheme for MuSig2 Aggregate Keys Authors: Ava Chow Status: Complete Type: Informational Assigned: 2024-06-04 License: CC0-1.0 Table of ContentsAbstractCopyrightMotivationSpecificationTest VectorsBackwards CompatibilityRationaleReference ImplementationAcknowledgements Abstract This document specifies how BIP 32 extended public keys can be constructed from a BIP 327 MuSig2 aggregate public key and how such keys should be used for key derivation. Copyright This BIP is licensed under the Creative Commons CC0 1.0 Universal license. Motivation Multiple signers can create a single aggregate public key with MuSig2 that is indistinguishable from a random public key. The cosigners need a method for generating additional aggregate pubkeys to follow the best practice of using a new address for every payment. The obvious method is for the cosigners to generate multiple public keys and produce a new aggregate pubkey every time on...
443 - OP_CHECKCONTRACTVERIFY
BIP: 443 source Layer: Consensus (soft fork) Title: OP_CHECKCONTRACTVERIFY Authors: Salvatore Ingala Status: Draft Type: Specification Assigned: 2025-05-08 License: BSD-3-Clause Discussion: 2022-11-08: https://gnusha.org/pi/bitcoindev/CAMhCMoH9uZPeAE_2tWH6rf0RndqV+ypjbNzazpFwFnLUpPsZ7g@mail.gmail.com 2023-07-30: https://gnusha.org/pi/bitcoindev/CAMhCMoFYF+9NL1sqKfn=ma3C_mfQv7mj2fqbqO5WXVwd6vyhLw@mail.gmail.com Table of ContentsAbstractCopyrightMotivationDesignOutput amountsPaying feesSpecificationScript support for OP_CHECKCONTRACTVERIFYTransaction-wide initializationInput initializationOP_CHECKCONTRACTVERIFY evaluationsigops budgetPolicy changesImplementationExamplesApplicationsDeploymentBackwards compatibilityFootnotesAcknowledgements Abstract This BIP proposes to add consensus support for a new tapscript opcode that enables a new type of output restrictions: OP_CHECKCONTRACTVERIFY (OP_CCV). This opcode enables users to create UTXOs that carry a dynami...
388 - Wallet Policies for Descriptor Wallets
BIP: 388 source Layer: Applications Title: Wallet Policies for Descriptor Wallets Authors: Salvatore Ingala Status: Complete Type: Specification Assigned: 2022-11-16 License: BSD-2-Clause Discussion: 2022-05-10: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-May/020423.html Table of ContentsAbstractCopyrightMotivationSecurity, privacy and UX concerns for hardware signing devicesSecurity issuesAvoiding key reuseUX issuesPolicy registration as a solutionAvoiding blowup in descriptor sizeSpecificationFormal definitionWallet descriptor templateKey information vectorAdditional rulesDescriptor derivationImplementation guidelinesOptional derivation pathsExamplesTest VectorsValid policiesInvalid policiesBackwards CompatibilityReference ImplementationChange LogFootnotesAcknowledgments Abstract Software wallets and hardware signing devices typically partition funds into separate "accounts". When signing or visualizing a transaction, aggregate flows of funds of all...