From: Pavol Rusnak <stick@satoshilabs•com>
To: Pavol Rusnak via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Proposal: Extended serialization format for BIP-32 wallets
Date: Thu, 7 Sep 2017 00:29:23 +0200 [thread overview]
Message-ID: <0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com> (raw)
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
next reply other threads:[~2017-09-06 22:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 22:29 Pavol Rusnak [this message]
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
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=0d405f5d-c0a4-bad7-b6c3-08ba4424bf17@satoshilabs.com \
--to=stick@satoshilabs$(echo .)com \
--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