public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andreas Schildbach <andreas@schildbach.de>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Export format for xpub
Date: Mon, 02 Feb 2015 15:17:41 +0100	[thread overview]
Message-ID: <mao0u5$gbu$1@ger.gmane.org> (raw)
In-Reply-To: <54CF74A5.3050304@gk2.sk>

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.





  reply	other threads:[~2015-02-02 14:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02  8:56 [Bitcoin-development] Export format for xpub Levin Keller
2015-02-02 11:33 ` Mike Hearn
2015-02-02 12:38   ` Andreas Schildbach
2015-02-02 12:59     ` Pavol Rusnak
2015-02-02 14:17       ` Andreas Schildbach [this message]
2015-02-02 14:47         ` vv01f
2015-02-03  0:02           ` Andreas Schildbach
2015-02-02 14:56         ` Pavol Rusnak
2015-02-03  0:05           ` Andreas Schildbach
2015-02-03  0:22             ` Pavol Rusnak
2015-02-03  9:33               ` Levin Keller
2015-02-03 10:10                 ` Pavol Rusnak
2015-02-03 10:37                   ` Andreas Schildbach
2015-02-03 10:44                     ` Pavol Rusnak
2015-02-03 10:35                 ` Andreas Schildbach
2015-02-03 10:34               ` Andreas Schildbach
2015-02-02 12:57   ` Pavol Rusnak
2015-02-02 11:38 ` Wladimir

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='mao0u5$gbu$1@ger.gmane.org' \
    --to=andreas@schildbach.de \
    --cc=bitcoin-development@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox