public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Kabuto Samourai <kabuto@samouraiwallet.com>
To: Pavol Rusnak <stick@satoshilabs.com>,
	 Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets
Date: Wed, 6 Sep 2017 22:52:57 -0500	[thread overview]
Message-ID: <CA+_kfXLvTKwkuYmtt94OPUEPPwsEzhRoryy7srKMbLxYDxnmFA@mail.gmail.com> (raw)
In-Reply-To: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com>

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

Thanks for the proposal. Aside from potential privacy implications of
revealing the derivation path for non BIP-44, 45, 49 HD nodes, this scheme
is superior to the alternate {x,y,z}pub idea. Since coin_type is part of
the path, the 'xpub' prefix may be shared across all coins if they so
choose. This format provides lock-in for BIP-49 going forward and opens the
door for a parallel native-SegWit BIP.

The birthday field is interesting. Could you provide some motivation for
its inclusion?

Could you also add some test vectors?

There are a few minor grammar / spelling errors, but we can nitpick those
after this goes to the pull request stage on bitcoin/bips.

On Wed, Sep 6, 2017 at 5:29 PM, Pavol Rusnak via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> The discussion about changing bip32 version bytes for SegWit got me
> thinking and I ended up with what I think is the best proposal:
>
> https://github.com/satoshilabs/slips/blob/master/slip-0032.md
>
> (It is hosted in SL repo for now, but if there is will, I would love to
> have this added to BIP repo as an extension to BIP32)
>
> Feel free to comment.
>
> --
> Best Regards / S pozdravom,
>
> Pavol "stick" Rusnak
> CTO, SatoshiLabs
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>



-Kabuto

PGP Fingerprint: 1A83 4A96 EDE7 E286 2C5A  B065 320F B934 A79B 6A99

[-- Attachment #2: Type: text/html, Size: 2530 bytes --]

  reply	other threads:[~2017-09-07  3:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06 22:29 [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets Pavol Rusnak
2017-09-07  3:52 ` Kabuto Samourai [this message]
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
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=CA+_kfXLvTKwkuYmtt94OPUEPPwsEzhRoryy7srKMbLxYDxnmFA@mail.gmail.com \
    --to=kabuto@samouraiwallet.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=stick@satoshilabs.com \
    /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