Author: Ferdinando M. Ametrano 2020-11-16 23:01:34
Published on: 2020-11-16T23:01:34+00:00
The author of the btclib library has been implementing PSBT support but has failed to understand the rationale for the proprietary and proof-of-reserves types. These types have nothing to do with the intrinsic operations required to finalize a valid transaction from PSBT manipulation. Whatever information content they can provide for non-standard PSBT manipulation, that content could stay in the unknown field without any loss of generality. As long as BIP174 prescribes that unknown data must be kept during PSBT manipulation, that should suffice. The author stresses that he has a project where they include proprietary information in the PSBT. Any PSBT software supporting unknown data keeps the proprietary information and the proprietary software retrieves that data from serialized PSBT with no problem. There is no need for a PSBT implementation to provide explicit support for proprietary and proof-of-reserves types. The author's conclusion is reinforced by the evidence of all PSBT implementations he knows of, including bitcoin core and HWI, not implementing proprietary and proof-of-reserve types. There is a high probability that part of BIP174 would be ignored.
Updated on: 2023-06-14T16:19:58.257866+00:00