Published on: 2017-09-07T20:39:17+00:00
In a discussion on the bitcoin-dev mailing list, Pavol Rusnak proposed adding an additional byte field called OutputType for wallets that do not follow BIP43. The field would have three options: P2PKH output type, P2WPKH-in-P2SH output type, and native Segwit output type. However, Thomas Voegtlin raised concerns about the visibility of this field for users. Voegtlin argued that the flag for segwit xpub/xprv in Electrum should be user visible to ensure all cosigners agree on the script type used to derive addresses. Andreas Schildbach and Pavol Rusnak discussed the issue of exported public key depth in Bitcoin Wallet. They agreed that the path should always be present if a chain is limited to a certain script type. However, there may be cases where script types are mixed on one chain, and in such cases, the field should be omitted, and the wallet needs to scan for all known types.In another discussion, Jonas Schnelli and Pavol Rusnak explored the possibility of reducing the resolution for a field in order to save space. They considered using week-level or month-level resolution, which would allow them to use just 16 bits for the field. Schnelli also questioned whether it would make sense to have special depth bytes that directly imply it's a BIP44 master key. However, Rusnak didn't see any good reason to do this unless they wanted to save some bytes. The email exchange focused on finding ways to optimize space usage while maintaining privacy and ease of use for wallets.The discussion on the bitcoin-dev mailing list revolved around using a block height or a timestamp for XPUB. It was pointed out that block height depends on the chain, while XPUB is not tied to any particular chain/coin. Some cryptocurrencies use directed acyclic graph (DAG) instead of blockchain for storing transactions, making it unclear what number to use as a block height. However, all blockchains contain timestamps in their blocks, which can be used for XPUB. The author expressed interest in hearing about a blockchain that does not occupy our spacetime continuum.Pavol Rusnak proposed a change to BIP32 version bytes for SegWit wallets. The proposal suggests using 13 or 16 bits to represent the birthday of private keys and rounding down to the beginning of the week when the key was created. It also proposes creating special depth bytes that directly imply it's a BIP44 master key and adding a version bit for future extensions. Jonas Schnelli suggested reducing the resolution for the field if necessary for privacy reasons. The email exchange focused on optimizing space usage while maintaining privacy and ease of use for wallets.The discussion on the bitcoin-dev mailing list raised the issue of including a birthday field in the blockchain. SPV wallet developers have been wanting this for years as it helps with the initial scan by only downloading blocks after the birthday. Test vectors were requested to be added for the inclusion of the birthday field. Minor grammar and spelling errors were also noted, which will be addressed at a later stage.The inclusion of a birthday field in SPV wallets was discussed between Kabuto Samourai and Pavol Rusnak. This development would aid with initial scans, allowing an SPV wallet to only download blocks from the blockchain after its birthday. Test vectors were requested and minor grammar and spelling errors were pointed out, which will be addressed later.Thomas Voegtlin proposed adding another byte field called OutputType for wallets that do not follow BIP43. The field would include options for P2PKH output type, P2WPKH-in-P2SH output type, and native Segwit output type. Concerns were raised about the visibility of this field for users, and suggestions were made to improve user visibility. Pavol Rusnak proposed a change to bip32 version bytes for SegWit, which was shared on GitHub. The proposal aims to extend BIP32 and improve it further. Feedback and comments are welcome.
Updated on: 2023-08-01T21:46:12.451769+00:00