Author: Pieter Wuille 2018-06-27 15:06:39
Published on: 2018-06-27T15:06:39+00:00
The email conversation is about the PSBT file format. Pieter Wuille explains that the Combiner role is important to ensure forward compatibility with new script types and to combine inputs from different outputs with different script types. The Combiner does not need to understand the contents of the fields, and deduplication can be done through whole-record uniqueness or specified-length uniqueness. However, a key-value model allows dumb combiners to pick one of the keys in case of duplication and remove the necessity of dealing with duplication from all other implementations. A record-based model forces all implementations to deal with multiple partial signatures for a single key. The question arises as to why it is important that an agent which doesn't understand a particular field structure can still make decisions about its inclusion or omission from the result (based on a repeated prefix). This is because otherwise, you may need a separate Combiner for each type of script involved. In addition, the conversation also talks about BIP32 derivation and how computing pubkeys can be expensive.
Updated on: 2023-05-20T17:06:38.029683+00:00