From: Pieter Wuille <pieter.wuille@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] BIP 32 proposed changes
Date: Sun, 26 Jan 2014 11:09:42 +0100 [thread overview]
Message-ID: <CAPg+sBgnW08NWBH0D39qSZRZDn8W4USS6w76MtRNeH1zwfwvkg@mail.gmail.com> (raw)
Hello all,
based on some feedback, I've created a pull request with a rewritten
version of BIP 32, hopefully making it more readable:
* Don't reuse the terminology 'public' vs 'private' for the alternate
derivation scheme which doesn't allow computing child public keys from
parent public keys, but call them "hardened".
* Add explicit type conversion functions.
* Don't use the ' suffix to mean "alternate" in two very different
meanings (use the 'h' suffix to mean hardened, and use CKDpriv and
CKDpub for the derivation functions that operate on private and public
keys).
* Several smaller changes.
These are just documentation changes, the semantics are unchanged.
Comments are welcome, see https://github.com/bitcoin/bips/pull/12.
--
Pieter
reply other threads:[~2014-01-26 10:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAPg+sBgnW08NWBH0D39qSZRZDn8W4USS6w76MtRNeH1zwfwvkg@mail.gmail.com \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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