From: Pavol Rusnak <stick@satoshilabs•com>
To: Andreas Schildbach <andreas@schildbach•de>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets
Date: Thu, 7 Sep 2017 22:00:05 +0200 [thread overview]
Message-ID: <40ed03a1-915c-33b0-c4ac-e898c8c733ba@satoshilabs.com> (raw)
In-Reply-To: <oos72e$rjp$1@blaine.gmane.org>
On 07/09/17 21:35, Andreas Schildbach via bitcoin-dev wrote:
> In case of Bitcoin Wallet, the depth is not null (m/0'/[0,1]) and still
> we need this field.
But the depth of exported public key will be null. It does not make
sense to export xpub for m or m/0' for your particular case.
> I think it should always be present if a chain is
> limited to a certain script type.
I am fine with having the path there all the time.
> There is however the case where even on one chain, script types are
> mixed. In this case the field should be omitted and the wallet needs to
> scan for all (known) types. Afaik Bitcoin Core is taking this path.
Is that really the case? Why come up with a hierarchy and then don't use it?
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
CTO, SatoshiLabs
next prev parent reply other threads:[~2017-09-07 20:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 22:29 Pavol Rusnak
2017-09-07 3:52 ` Kabuto Samourai
2017-09-07 16:25 ` Pavol Rusnak
2017-09-07 16:30 ` Kabuto Samourai
2017-09-07 16:37 ` Pavol Rusnak
2017-09-07 18:02 ` Peter Todd
2017-09-07 4:29 ` Thomas Voegtlin
2017-09-07 16:23 ` Pavol Rusnak
2017-09-07 16:33 ` Kabuto Samourai
2017-09-07 19:35 ` Andreas Schildbach
2017-09-07 20:00 ` Pavol Rusnak [this message]
2017-09-07 20:39 ` Thomas Voegtlin
2017-09-07 16:47 ` Jonas Schnelli
2017-09-07 18:09 ` Peter Todd
2017-09-07 18:38 ` Pavol Rusnak
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=40ed03a1-915c-33b0-c4ac-e898c8c733ba@satoshilabs.com \
--to=stick@satoshilabs$(echo .)com \
--cc=andreas@schildbach$(echo .)de \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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