Author: Stepan Snigirev 2019-05-07 09:23:44
Published on: 2019-05-07T09:23:44+00:00
The proposal suggests sharing xpubs in the global section of the file, with a restriction that they must only include the hardened prefix of the path. The existing bip32 derivation path included in individual inputs and outputs should be merged in as needed. However, it is not necessary to restrict xpubs to have only hardened derivation. People may want to share non-hardened xpubs with co-signers and keep parent xpub on their watch-only wallet. PSBT-signing devices still need to store the xpubs of their co-signers for safe verification of incoming addresses. The proposal suggests keeping hardware wallets stateless and verifying that xpubs in the inputs and in the change output are the same. As PSBT is a binary format, using the extension serialization format without any encodings makes sense. Keeping the prefix that defines if the key is used for testnet or mainnet may also be useful.
Updated on: 2023-06-13T18:25:15.895995+00:00