📅 Original date posted:2015-02-02
📝 Original message:On 02/02/2015 03:56 PM, Pavol Rusnak wrote:
> To me it seems more important to describe how addresses should be
> discovered (i.e. to scan xpub/0/i and xpub/1/j chains using gap limit G)
> instead of how the xpub was created/obtained (bip32 vs bip44).
>
> What do you thing about changing ?h=bip32 to something like
>
> ?t=01&g=20
>
> - t=01 meaning that chains 0 and 1 should be scanned (feel free to
> change "01" into any other descriptive string)
> - g=20 meaning that gap 20 should be used
I don't think that parameterizing will work, we can't predict future
BIPs. It's the same as for BIP43, in the end we agreed on just putting
the BIP number.
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:29:26
in reply to nevent1q…u260
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:29:26Event JSON
{
"id": "4242d99ee01a2d743829d505c6ab64523576e061d7e8a5f3b56c8711e6c6c0b0",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686151766,
"kind": 1,
"tags": [
[
"e",
"da5dfa7015ad7eb23fb699400b79b743db94aa85c8d6df42489b5ad471f64cea",
"",
"root"
],
[
"e",
"cb6d408d0670f51a3b5529111091a9db92f457f18c70b3eeb65bd95437fec025",
"",
"reply"
],
[
"p",
"7631397e469f47f3535567311f5f7c17129e0ff2cb253df015e3d92ddfd92c63"
]
],
"content": "📅 Original date posted:2015-02-02\n📝 Original message:On 02/02/2015 03:56 PM, Pavol Rusnak wrote:\n\n\u003e To me it seems more important to describe how addresses should be\n\u003e discovered (i.e. to scan xpub/0/i and xpub/1/j chains using gap limit G)\n\u003e instead of how the xpub was created/obtained (bip32 vs bip44).\n\u003e \n\u003e What do you thing about changing ?h=bip32 to something like\n\u003e \n\u003e ?t=01\u0026g=20\n\u003e \n\u003e - t=01 meaning that chains 0 and 1 should be scanned (feel free to\n\u003e change \"01\" into any other descriptive string)\n\u003e - g=20 meaning that gap 20 should be used\n\nI don't think that parameterizing will work, we can't predict future\nBIPs. It's the same as for BIP43, in the end we agreed on just putting\nthe BIP number.",
"sig": "391626e2c455923774a3eb1c296380936861623e8d8cf17e111c17955c05234569555a9ff57f5690e3f5b61ba5740edad9db6b1e43ef2c3679c6a048789783f5"
}