1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <pieter.wuille@gmail.com>) id 1W7Mey-0003IP-QH
for bitcoin-development@lists.sourceforge.net;
Sun, 26 Jan 2014 10:09:48 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.180 as permitted sender)
client-ip=209.85.223.180; envelope-from=pieter.wuille@gmail.com;
helo=mail-ie0-f180.google.com;
Received: from mail-ie0-f180.google.com ([209.85.223.180])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W7Mey-00030J-2N
for bitcoin-development@lists.sourceforge.net;
Sun, 26 Jan 2014 10:09:48 +0000
Received: by mail-ie0-f180.google.com with SMTP id at1so4649040iec.39
for <bitcoin-development@lists.sourceforge.net>;
Sun, 26 Jan 2014 02:09:42 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.43.61.196 with SMTP id wx4mr17795931icb.6.1390730982761;
Sun, 26 Jan 2014 02:09:42 -0800 (PST)
Received: by 10.50.100.10 with HTTP; Sun, 26 Jan 2014 02:09:42 -0800 (PST)
Date: Sun, 26 Jan 2014 11:09:42 +0100
Message-ID: <CAPg+sBgnW08NWBH0D39qSZRZDn8W4USS6w76MtRNeH1zwfwvkg@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(pieter.wuille[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1W7Mey-00030J-2N
Subject: [Bitcoin-development] BIP 32 proposed changes
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 10:09:49 -0000
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
|
