summaryrefslogtreecommitdiff
path: root/9b/cb8513f64fde96c94344b50ef9351f37b29332
blob: 9bd711b654008e14ace640230700658efe2c82e2 (plain)
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
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jeanpaulkogelman@me.com>) id 1VhWGF-0008R5-BM
	for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Nov 2013 03:09:27 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of me.com
	designates 17.172.220.240 as permitted sender)
	client-ip=17.172.220.240; envelope-from=jeanpaulkogelman@me.com;
	helo=st11p02mm-asmtp005.mac.com; 
Received: from st11p02mm-asmtpout005.mac.com ([17.172.220.240]
	helo=st11p02mm-asmtp005.mac.com)
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1VhWGE-0003uv-15 for bitcoin-development@lists.sourceforge.net;
	Sat, 16 Nov 2013 03:09:27 +0000
Received: from [10.0.1.20] ([216.19.182.8]) by st11p02mm-asmtp005.mac.com
	(Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit
	(built Aug
	22 2013)) with ESMTPSA id <0MWC00MT8638R170@st11p02mm-asmtp005.mac.com>
	for bitcoin-development@lists.sourceforge.net; Sat,
	16 Nov 2013 03:09:09 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure
	engine=2.50.10432:5.10.8794,1.0.14,0.0.0000
	definitions=2013-11-15_07:2013-11-15, 2013-11-15,
	1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0
	suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam
	adjust=0
	reason=mlx scancount=1 engine=7.0.1-1308280000
	definitions=main-1311150242
Content-type: multipart/signed;
	boundary="Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E";
	protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
In-reply-to: <CAAS2fgSyegH8y1dYcijCSPLsC54mxeSNsN+3FQVDo5R9tWwAwQ@mail.gmail.com>
Date: Fri, 15 Nov 2013 19:09:07 -0800
Message-id: <BF62F0D0-1D13-4F19-A8F6-F588F3060A64@me.com>
References: <CANEZrP37a=EH+1P47opH0E-1TG9ozgw_1NzecJpRRJsMaZRLOw@mail.gmail.com>
	<81f77484-3ca9-40a7-a999-884260b26be5@me.com>
	<CAAS2fgSyegH8y1dYcijCSPLsC54mxeSNsN+3FQVDo5R9tWwAwQ@mail.gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Spam-Score: -0.5 (/)
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 SPF_PASS               SPF: sender matches SPF record
	0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
	See
	http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
	for more information. [URIs: bitcointalk.org]
	1.0 HTML_MESSAGE           BODY: HTML included in message
X-Headers-End: 1VhWGE-0003uv-15
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet
 master seed with optional encryption
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: Sat, 16 Nov 2013 03:09:27 -0000


--Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF"


--Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


I've made no changes since the last time I've mentioned it here on the =
list (when the BIP procedures were being discussed).

The last changes are:

01-10-2013 - Expanded the salt to be prefix + date + checksum and =
renamed 'master seed' to 'root key'.
24-07-2013 - Added user selectable KDF + parameters, encoded in the =
prefix.
22-07-2013 - Added 2 byte creation date field, as a result, the prefix =
is expanded to 3 bytes.

The biggest difference between this proposal and BIP38 is that BIP38 =
allows a 3rd party to generate the encrypted private key + confirmation =
code from a passphrase code. Since this proposal is about encrypting a =
random value that's fed into HMAC-SHA512 and the presence of a partial =
hash of the root address, that's not possible.




>> https://bitcointalk.org/index.php?topic=3D258678
>=20
> Greetings.  Any recent progress on this?
>=20
> Do we believe this proposal can replace BIP38?  If not, what are the
> limitations that would prevent it from doing so?


--Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><br></div><div>I've made no changes since the =
last time I've mentioned it here on the list (when the BIP procedures =
were being discussed).</div><div><br></div><div>The last changes =
are:</div><div><br></div><div>01-10-2013 - Expanded the salt to be =
prefix + date + checksum and renamed 'master seed' to 'root =
key'.</div><div>24-07-2013 - Added user selectable KDF + parameters, =
encoded in the prefix.</div><div>22-07-2013 - Added 2 byte creation date =
field, as a result, the prefix is expanded to 3 =
bytes.</div><div><br></div><div>The biggest difference between this =
proposal and BIP38 is that BIP38 allows a 3rd party to generate the =
encrypted private key + confirmation code from a passphrase code. Since =
this proposal is about encrypting a random value that's fed into =
HMAC-SHA512 and the presence of a partial hash of the root address, =
that's not =
possible.</div><div><br></div><div><br></div><div><br></div><div><br></div=
><div><blockquote type=3D"cite"><blockquote type=3D"cite"><a =
href=3D"https://bitcointalk.org/index.php?topic=3D258678">https://bitcoint=
alk.org/index.php?topic=3D258678</a></blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">Greetings. =
&nbsp;Any recent progress on this?<br><br>Do we believe this proposal =
can replace BIP38? &nbsp;If not, what are the<br>limitations that would =
prevent it from doing so?<br></blockquote></div><br></body></html>=

--Apple-Mail=_A995914C-4047-4CD9-8AFC-104CEE1E35EF--

--Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJShuHTAAoJEG93Vo4Z7tpFMCUQALxtU61LKbTDS+pu3/fNaO6t
jmplwBh0oLAPRdD/GtNJa3LZG6W19dxKxm8g/jwHF+xIEwmpMk9dpXXqeDBmh9W+
05Gfu7RniIZrk8PNBiDUAUp6XorS/wYHAsdM5PkAv2CZ07lz+yzczPiHDoaW0JjJ
5wol6ORUqQHE9iC/maq6iHWux6CXAdJ6XxdFo/Pnd43lEecZ+ErFWwTEKXPBWOV6
ZD5KYv/JoR7YjPYwmWnwYdCvZOMu0d5PSFXup4l1PsZqWwSyWs3iu7m+CPXdUhMe
Tft+Zl0mGKDxqkDUj5xPK7NjGVLmTEXG9+nNrT+Y0mmRu+R8O+Od7m8bhFEWtcin
FW+mn45RNbJfVjQo1jX+dhFyLUEdqTWY37WRY2i1wHQALZJ3hzYg8aB2vcOo+nA8
r1CB7ANcgaFCsid+yV4RPOW8NMrLacrFNfaInsNCf6GFrYeJwm1rKCF8AZEqBB9B
pyBHJdIX9HI6Nb/ZWmXvmP9H/Z414+gEhJLUPNkFR9t4rd8gaWwxvROsmh+2QM01
k0Cn5iFrPZJIDbe3nJV3ONgZLr1qfdJEEakq/ezM2Oi7qDnY2uR11OvER1pEZ70r
x2IXXSXMmBpeaCaAyvTvWWpBcAnemIUMREIvZbktIPfdT3YMQOhXpJPM6y7SOqOj
Tgj4gKG3/SIYdeWUhfUw
=J8NA
-----END PGP SIGNATURE-----

--Apple-Mail=_6468106F-7B10-4AB8-821A-965DCCD1AC9E--