Author: vv01f 2018-07-24 23:44:35
Published on: 2018-07-24T23:44:35+00:00
A team of developers is working on a walleting application to generate bech32 and P2WPKH-nested-in-P2SH addresses. However, the payee cannot know in advance the technological capabilities of the payer, so a solution could be to encode both bech32 and P2SH addresses in a Bitcoin URI, with legacy wallets only seeing the P2SH address and new wallets able to see and use the bech32 address for transactions. To keep compatibility with BIP21, the 'path' field of the URI can be used for the P2WPKH-nested-in-P2SH address, while a new field (e.g. 'bech32') can be used for the bech32 address. The assumption is that wallets using this scheme will monitor incoming transactions on both addresses. The order of attributes should remain irrelevant, with clients checking all attributes of the same name. It is unclear if there is any precedence for the multiple use of an attribute in URI schemes.
Updated on: 2023-06-13T04:00:10.972769+00:00