📅 Original date posted:2015-02-02
📝 Original message:On 02/02/2015 01:59 PM, Pavol Rusnak wrote:
>> It's h=bip32 for the hierarchy used and
>
> Do I understand this correctly and h=bip32 hierarchy means that both
>
> xpub/0/i and xpub/1/j chains are scanned? (So it applies to BIP44
> generated xpubs as well?)
Yes, except that BIP32-hierarchy and BIP44 differ in some requirements
(e.g. gap limit).
>> c=123456 for the creation date of the wallet (in seconds since epoch).
>
> Uff, I would expect YYYYMMDD there so it's human readable as well.
Those strings are not meant to be read by humans. YYYYMMDD is more
complicated than necessary, given that Bitcoin deals with seconds since
epoch everywhere.
Andreas Schildbach [ARCHIVE] /
npub1xg…adsv7
2023-06-07 15:29:25
in reply to nevent1q…xgzd
Author Public Key
npub1xg2m84malu0cfm4444r0kysx4rgk27e75aj6sz6538kw8fcz627qeadsv7Published at
2023-06-07 15:29:25Event JSON
{
"id": "27b68ba8b66be2895bfdd32094919a67b57e7a5c44858892ba684dc71f1014be",
"pubkey": "3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc",
"created_at": 1686151765,
"kind": 1,
"tags": [
[
"e",
"da5dfa7015ad7eb23fb699400b79b743db94aa85c8d6df42489b5ad471f64cea",
"",
"root"
],
[
"e",
"4bc851a7769e989c98fa96213893973c0df99f51797569a5984c641ddab0a29c",
"",
"reply"
],
[
"p",
"7631397e469f47f3535567311f5f7c17129e0ff2cb253df015e3d92ddfd92c63"
]
],
"content": "📅 Original date posted:2015-02-02\n📝 Original message:On 02/02/2015 01:59 PM, Pavol Rusnak wrote:\n\u003e\u003e It's h=bip32 for the hierarchy used and\n\u003e\n\u003e Do I understand this correctly and h=bip32 hierarchy means that both\n\u003e\n\u003e xpub/0/i and xpub/1/j chains are scanned? (So it applies to BIP44\n\u003e generated xpubs as well?)\n\nYes, except that BIP32-hierarchy and BIP44 differ in some requirements\n(e.g. gap limit).\n\n\u003e\u003e c=123456 for the creation date of the wallet (in seconds since epoch).\n\u003e\n\u003e Uff, I would expect YYYYMMDD there so it's human readable as well.\n\nThose strings are not meant to be read by humans. YYYYMMDD is more\ncomplicated than necessary, given that Bitcoin deals with seconds since\nepoch everywhere.",
"sig": "9b2903c8768c5d498329738a65b61559a04b638d483f6c5abfc1f2bc2ce7ccf7bc0af8233d809fa6f6e947fd712fcc9804c7345ebd5cac922abecc5775e47e7c"
}