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. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
