From: Pavol Rusnak <stick@gk2•sk>
To: Levin Keller <post@levinkeller•de>
Cc: bitcoin-development@lists•sourceforge.net,
Andreas Schildbach <andreas@schildbach•de>
Subject: Re: [Bitcoin-development] Export format for xpub
Date: Tue, 03 Feb 2015 11:10:59 +0100 [thread overview]
Message-ID: <54D09EB3.4080201@gk2.sk> (raw)
In-Reply-To: <CAG86ZOzt2q4eF8YrPjV6POVkawFAC+Co4n_eZ=rQo2BgMtVn8g@mail.gmail.com>
On 03/02/15 10:33, Levin Keller wrote:
> bitcoin-pub-export:xpub[gibberish]?gaplimit=[number]&path=[path in
> derivation tree]&subchains=[numbers]&creationdate=[unixtimestamp]
I cannot come up with an usecase where "path" parameter would be needed.
FWIW childnumber and depth are already expressed in xpub itself.
I like the general idea of "subchains" parameter, but I would like to
further specify it:
a) parameter should contain values described as comma separated
list of values (such as 0,1,2,3,4)
b) consecutive values can be shortened via dash (0,1,2,3 == 0-3)
c) should we allow non-consecutive values (e.g. 0,1,3,8)?
I am not sure. If not the "subchains" param can contain just upper
bound of indexes to scan (e.g. "3")
d) a wallet uses just the first specified chain to generate receiving
addresses, uses the other chains just to add to the balance
OR should a wallet be able to generate receiving address for second,
third, etc. external chain? if yes, we should split "subchains" param
into "external" and "internal" params both containing a list of
numbers. this seems like an overkill to me and I am fine with using
just the first chain as the external one.
> Why not have more descriptive parameters? Saving on data?
Yes. The longer the string, the bigger the QR code.
> I am a big fan of unix timestamps. Would vote for Andreas' format on the
> creation date.
I am not against Unix timestamps, I just said I expected something else
there. Unix timestamps have a lot of advantages. Another option that
might make sense is the block number.
--
Best Regards / S pozdravom,
Pavol Rusnak <stick@gk2•sk>
next prev parent reply other threads:[~2015-02-03 10:11 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
2015-02-03 0:22 ` Pavol Rusnak
2015-02-03 9:33 ` Levin Keller
2015-02-03 10:10 ` Pavol Rusnak [this message]
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=54D09EB3.4080201@gk2.sk \
--to=stick@gk2$(echo .)sk \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=post@levinkeller$(echo .)de \
/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