From: Pavol Rusnak <stick@satoshilabs.com>
To: shiva sitamraju <shiva@blockonomics.co>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP49 Derivation scheme changes
Date: Tue, 5 Sep 2017 17:41:37 +0200 [thread overview]
Message-ID: <9da64df3-c6a9-c232-c801-f379a6d65e44@satoshilabs.com> (raw)
In-Reply-To: <CABuOfuiz9U=ZPWRUfVXHgBekZ74B4zkUikg6Svxbr6jrJA5Vyw@mail.gmail.com>
On 05/09/17 09:10, shiva sitamraju via bitcoin-dev wrote:
> 0x042393df , sxpr , segwit mainnet private key
> 0x04239377 , sxpb , segwit mainnet public key
> 0x04222463 , stpb , segwit testnet public key
> 0x042224cc , stpr , segwit testnet private key
I am fine with both your proposal and proposal from Thomas
({x,y,z}{pub,prv}).
Let's just decide ASAP which one we'll use.
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
CTO, SatoshiLabs
next prev parent reply other threads:[~2017-09-05 15:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 7:10 [bitcoin-dev] BIP49 Derivation scheme changes shiva sitamraju
2017-09-05 15:41 ` Pavol Rusnak [this message]
2017-09-05 16:33 ` Thomas Voegtlin
-- strict thread matches above, loose matches on Subject: below --
2017-09-06 5:20 shiva sitamraju
2017-08-30 7:24 shiva sitamraju
2017-09-03 5:19 ` Thomas Voegtlin
2017-09-06 7:19 ` Dan Libby
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=9da64df3-c6a9-c232-c801-f379a6d65e44@satoshilabs.com \
--to=stick@satoshilabs.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=shiva@blockonomics.co \
/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