📅 Original date posted:2017-09-05
📝 Original message:BIP32 extended public/private keys have version bytes that result in the
user visible xpub/xprv prefix. The BIP's recommendation is to use
different version bytes for other networks (such as tpub/tprv for testnet)
I would like to use additional version bytes to indicate the type of
output script used with the public keys.
I believe the change should be user visible, because users are exposed
to master public keys. I propose the following prefixes:
========== =========== ===================================
Version Prefix Description
========== =========== ===================================
0x0488ade4 xprv P2PKH or P2SH
0x0488b21e xpub P2PKH or P2SH
0x049d7878 yprv (P2WPKH or P2WSH) nested in P2SH
0x049d7cb2 ypub (P2WPKH or P2WSH) nested in P2SH
0x04b2430c zprv P2WPKH or P2WSH
0x04b24746 zpub P2WPKH or P2WSH
========== =========== ===================================
(source: http://docs.electrum.org/en/latest/seedphrase.html)
I have heard the argument that xpub/xprv serialization is a format for
keys, and that it should not be used to encode how these keys are used.
However, the very existence of version bytes, and the fact that they are
used to signal whether keys will be used on testnet or mainnet goes
against that argument.
If we do not signal the script type in the version bytes, I believe
wallet developers are going to use dirtier tricks, such as the bip32
child number field in combination with bip43/bip44/bip49.
Thomas
Thomas Voegtlin [ARCHIVE] /
npub10f…7ej47
2023-06-07 18:05:21
in reply to nevent1q…ugne
Author Public Key
npub10f96gqrsu4qpygfgvuvzce47aavjvql703egfde0l2hua8dzpszs67ej47Published at
2023-06-07 18:05:21Event JSON
{
"id": "9ce33d5831b172bae477b4137ecf53dd5aac5d8fd91c321ffb612241eb7d1f8b",
"pubkey": "7a4ba40070e54012212867182c66beef592603fe7c7284b72ffaafce9da20c05",
"created_at": 1686161121,
"kind": 1,
"tags": [
[
"e",
"a923bf1bc525f39bcc8b2d79f1a19c60437c6f409ee33c9b06b9485d2e732c67",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2017-09-05\n📝 Original message:BIP32 extended public/private keys have version bytes that result in the\nuser visible xpub/xprv prefix. The BIP's recommendation is to use\ndifferent version bytes for other networks (such as tpub/tprv for testnet)\n\nI would like to use additional version bytes to indicate the type of\noutput script used with the public keys.\n\nI believe the change should be user visible, because users are exposed\nto master public keys. I propose the following prefixes:\n\n========== =========== ===================================\nVersion Prefix Description\n========== =========== ===================================\n0x0488ade4 xprv P2PKH or P2SH\n0x0488b21e xpub P2PKH or P2SH\n0x049d7878 yprv (P2WPKH or P2WSH) nested in P2SH\n0x049d7cb2 ypub (P2WPKH or P2WSH) nested in P2SH\n0x04b2430c zprv P2WPKH or P2WSH\n0x04b24746 zpub P2WPKH or P2WSH\n========== =========== ===================================\n(source: http://docs.electrum.org/en/latest/seedphrase.html)\n\nI have heard the argument that xpub/xprv serialization is a format for\nkeys, and that it should not be used to encode how these keys are used.\nHowever, the very existence of version bytes, and the fact that they are\nused to signal whether keys will be used on testnet or mainnet goes\nagainst that argument.\n\nIf we do not signal the script type in the version bytes, I believe\nwallet developers are going to use dirtier tricks, such as the bip32\nchild number field in combination with bip43/bip44/bip49.\n\n\nThomas",
"sig": "a28f7355642db2e39fbeefb583cd9e8062d009e12ca7c659236fc78d0c59d540f3839e3bc2aa123b1442374add8367fde1650f071559cd40cdc353d7fa940ff1"
}