326 - Anti-fee-sniping in taproot transactions
BIP: 326 source Layer: Applications Title: Anti-fee-sniping in taproot transactions Author: Chris Belcher Status: Draft Type: Informational Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0326 Created: 2021-06-10 License: CC0-1.0 Post-History: 2021-6-10: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-June/019048.html Table of ContentsAbstractMotivationBackgroundFee snipingAbsolute vs relative locktimeTransaction pinningSpecificationsPseudocodeCompatibilityAcknowledgementsCopyrightReferences Abstract 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 of point-time-locked contracts (PTLCs) such as CoinSwap, Lightning and Discrete Log Contracts. Motivation With taproot recently added to bitcoin, and wallet software about to implement taproot wallets, we are in a unique position to impro...
46 - Address Scheme for Timelocked Fidelity Bonds
BIP: 46 source Layer: Applications Title: Address Scheme for Timelocked Fidelity Bonds Author: Chris Belcher Thebora Kompanioni Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0046 Status: Draft Type: Standards Track Created: 2022-04-01 License: CC0-1.0 Post-History: 2022-05-01: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-May/020389.html Table of ContentsAbstractCopyrightMotivationBackwards CompatibilityBackgroundFidelity bondsFidelity bonds in cold storageRationaleSpecificationsPublic key derivationTimelock derivationAddress derivationMessage signingTest vectorsReference Abstract 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 how to use fidelity bonds to sign over messages, such as certificates, which are needed when using fidelity bonds that are stored offline. Copyright This document is licensed under...
179 - Name for payment recipient identifiers
BIP: 179 source Title: Name for payment recipient identifiers Author: Emil Engler Luke Dashjr Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0179 Status: Draft Type: Informational Created: 2019-10-17 License: CC0-1.0 Table of ContentsAbstractSpecificationMotivationRationaleBackwards CompatibilityAcknowledgementsCopyright Abstract This BIP proposes a new term for 'address' Specification The new term is: Bitcoin Invoice Address The Bitcoin and Address parts are optional. The address suffix should only be used as a transitional step. A Bitcoin Invoice Address is a string of characters that can be used to indicate the intended recipient and purpose of a transaction. Motivation Bitcoin addresses are intended to be only used once and you should generate a new one for every new incoming payment. The term 'address' however indicates consistency because nearly everything on the internet or the offline world with the t...