Author: Jonas Schnelli 2018-06-19 09:38:24
Published on: 2018-06-19T09:38:24+00:00
The post discusses various features and concerns related to the Bitcoin Improvement Proposal 174 (BIP174). One of the key topics is the choice between the key-value map model or the set model. The author believes that while all points made by Pieter are valid, changing existing implementations to adopt the k/v set model may not be worth it. Additionally, the post covers the use of Combiners to verify two PSBTs for the same transaction, optional signing, derivation from xpub or fingerprint, generic key offset derivation, and hex encoding.The post also delves into key derivation in multisig and how signers and creators must agree on a key derivation scheme. While BIP32 derivation is commonly used, sharing xpubs may be a concern in non-trust relationships. To address this, the post suggests a more flexible and generic approach to support faster derivation of required keys for signing a particular input.Overall, the author suggests that for practical multisig with hardware wallets, a simple BIP32-child-key-index or BIP32-keypath derivation support field should be sufficient, and a generic "derivation support field" provided from the signer to the creator during address-generation that just "loops" back during the PSBT use-cases is probably overkill.
Updated on: 2023-06-13T03:22:15.412845+00:00