From: Andreas Schildbach <andreas@schildbach•de>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Export format for xpub
Date: Tue, 03 Feb 2015 01:05:06 +0100 [thread overview]
Message-ID: <map3bi$pkf$2@ger.gmane.org> (raw)
In-Reply-To: <54CF9016.5070206@gk2.sk>
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.
next prev parent reply other threads:[~2015-02-03 0:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 8:56 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
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 [this message]
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='map3bi$pkf$2@ger.gmane.org' \
--to=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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