From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org,
Kabuto Samourai <kabuto@samouraiwallet•com>
Subject: Re: [bitcoin-dev] Proposal: bip32 version bytes for segwit scripts
Date: Thu, 7 Sep 2017 15:02:17 -0400 [thread overview]
Message-ID: <201709071502.19413.luke@dashjr.org> (raw)
In-Reply-To: <CA+_kfXJPfbGD6cDiPZ+7Z_rwUVS6JQNW8Vb-YsgD2wsPhHoBjw@mail.gmail.com>
On Tuesday 05 September 2017 15:00:04 Kabuto Samourai via bitcoin-dev wrote:
> I think Luke and Thomas may be talking past one another. When exporting a
> root master HD seed, encoding the {x,y,z}{pub,prv} distinctions makes no
> sense, as the root seed should derive all paths for all coins. Wallets may
> need additional code to discover which paths have been used when importing
> a root seed. But when exporting / importing an account-level seed for
> watch-only and receive address generation, changing the serialization
> version bytes is appropriate and (in our view) essential to avoid loss of
> funds.
In that case, I think we should go back to the proposal I started with in
March...
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-March/013726.html
This handles not only simple HD seeds, but also multisig HD and such.
Luke
next prev parent reply other threads:[~2017-09-07 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 19:00 Kabuto Samourai
2017-09-06 9:26 ` Thomas Voegtlin
2017-09-06 13:47 ` Kabuto Samourai
2017-09-07 19:02 ` Luke Dashjr [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-05 10:25 Thomas Voegtlin
2017-09-05 15:44 ` Pavol Rusnak
2017-09-05 17:03 ` Luke Dashjr
2017-09-05 18:09 ` Thomas Voegtlin
2017-09-06 17:02 ` Pavol Rusnak
2017-09-05 22:13 ` Andreas Schildbach
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=201709071502.19413.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=kabuto@samouraiwallet$(echo .)com \
/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