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
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <g.rowe.froot@gmail.com>) id 1WNmLE-0004QF-9F
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Mar 2014 16:49:16 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.173 as permitted sender)
client-ip=209.85.128.173; envelope-from=g.rowe.froot@gmail.com;
helo=mail-ve0-f173.google.com;
Received: from mail-ve0-f173.google.com ([209.85.128.173])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNmLC-0004sj-Lo
for bitcoin-development@lists.sourceforge.net;
Wed, 12 Mar 2014 16:49:16 +0000
Received: by mail-ve0-f173.google.com with SMTP id oy12so10321442veb.18
for <bitcoin-development@lists.sourceforge.net>;
Wed, 12 Mar 2014 09:49:09 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.52.108.228 with SMTP id hn4mr727715vdb.43.1394642949119;
Wed, 12 Mar 2014 09:49:09 -0700 (PDT)
Sender: g.rowe.froot@gmail.com
Received: by 10.220.251.65 with HTTP; Wed, 12 Mar 2014 09:49:09 -0700 (PDT)
In-Reply-To: <53208356.7010209@gk2.sk>
References: <CANEZrP37a=EH+1P47opH0E-1TG9ozgw_1NzecJpRRJsMaZRLOw@mail.gmail.com>
<81f77484-3ca9-40a7-a999-884260b26be5@me.com>
<CAAS2fgSyegH8y1dYcijCSPLsC54mxeSNsN+3FQVDo5R9tWwAwQ@mail.gmail.com>
<BF62F0D0-1D13-4F19-A8F6-F588F3060A64@me.com>
<682B9F30-7DDC-4A9D-886E-5454D5F45665@me.com>
<A6F382CD-01F7-47DF-84F4-20F81BB64259@me.com>
<53205D1E.1000100@gk2.sk>
<E3C05DB6-D182-43B1-A6F6-128734D933F9@me.com>
<53208356.7010209@gk2.sk>
Date: Wed, 12 Mar 2014 16:49:09 +0000
X-Google-Sender-Auth: v_ktJi0zTm4YAfDLriof5Mxy-5o
Message-ID: <CAKm8k+3bbhN=Kf2thvtakA7EGcTHDn1ssQm-+Fwf3hAAQmndTQ@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=bcaec548a8e99240d004f46b9d30
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(g.rowe.froot[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WNmLC-0004sj-Lo
Subject: Re: [Bitcoin-development] [RFC] Proposal: Base58 encoded HD Wallet
root key 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: Wed, 12 Mar 2014 16:49:16 -0000
--bcaec548a8e99240d004f46b9d30
Content-Type: text/plain; charset=UTF-8
Jean-Paul, it may be worth noting that the BIP39 word list is integrated
into Bitcoinj so will likely become the de facto standard for Android,
Trezor web and several desktop wallets. Anyone deviating from that word
list would likely find themselves in an isolated pocket.
Regarding the timestamp, MultiBit HD uses a simple timestamp of "number of
days since midnight of Bitcoin genesis block in UTC with modulo 97 checksum
appended". Thus a new seed generated on 27 January 2014 would have
"1850/01" as its checksum. When creating a new wallet the users are tested
that they have written the timestamp down along with the associated
12/18/24 words.
Modulo 97 was chosen since it catches about 99% of errors.
On 12 March 2014 15:55, Pavol Rusnak <stick@gk2.sk> wrote:
> On 03/12/2014 04:45 PM, Jean-Paul Kogelman wrote:
> > Yes I am. There are some differences between BIP 39 and my proposal
> though.
> >
> > - BIP 39 offers an easy list of words, no gnarly string of case
> sensitive letters and numbers.
>
> Which is better IMO. I can't imagine anyone writing down a long Base58
> encoded string.
>
> > - BIP 39 only offers one fixed length of entropy, always 12 words, no
> option to increase or decrease the length.
>
> Not true, BIP39 supports 12/18/24 words (= 128/192/256 bits of entropy).
>
> > - BIP 39 doesn't have a genesis date field, so no optimization during
> blockchain rescan.
>
> This is nice addition, indeed. But we needed to limit the data as
> possible in order not to increase the number of words needed to be noted
> down.
>
> > - BIP 39 doesn't have password typo detection. No easy way to recover a
> password if you know most of it.
>
> It has a detection. Not correction though.
>
> > - BIP 39 does not have a user selectable KDF, only 2048 round
> PBKDF2-HMAC-SHA512.
> > - BIP 39 can't outsource the KDF computation to a 3rd party.
>
> True, but having one or two solid options are better than having
> gazillions of possible options.
>
> > - BIP 39 wallet implementors can use their own word lists, breaking
> cross wallet compatibility.
>
> True, but they are encouraged to use the list provided. Possibility to
> outsource KDF outside of your "standard" breaks much more compatibility
> than this.
>
> --
> Best Regards / S pozdravom,
>
> Pavol Rusnak <stick@gk2.sk>
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--bcaec548a8e99240d004f46b9d30
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Jean-Paul, it may be worth noting that the BIP39 word list=
is integrated into Bitcoinj so will likely become the de facto standard fo=
r Android, Trezor web and several desktop wallets. Anyone deviating from th=
at word list would likely find themselves in an isolated pocket.<div>
<br></div><div>Regarding the timestamp, MultiBit HD uses a simple timestamp=
of "number of days since midnight of Bitcoin genesis block in UTC wit=
h modulo 97 checksum appended". Thus a new seed generated on 27 Januar=
y 2014 would have "1850/01" as its checksum. When creating a new =
wallet the users are tested that they have written the timestamp down along=
with the associated 12/18/24 words.</div>
<div><br></div><div>Modulo 97 was chosen since it catches about 99% of erro=
rs.</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote=
">On 12 March 2014 15:55, Pavol Rusnak <span dir=3D"ltr"><<a href=3D"mai=
lto:stick@gk2.sk" target=3D"_blank">stick@gk2.sk</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On 03/12/2014 04:45 PM, Jean=
-Paul Kogelman wrote:<br>
> Yes I am. There are some differences between BIP 39 and my proposal th=
ough.<br>
><br>
> - BIP 39 offers an easy list of words, no gnarly string of case sensit=
ive letters and numbers.<br>
<br>
</div>Which is better IMO. I can't imagine anyone writing down a long B=
ase58<br>
encoded string.<br>
<div class=3D""><br>
> - BIP 39 only offers one fixed length of entropy, always 12 words, no =
option to increase or decrease the length.<br>
<br>
</div>Not true, BIP39 supports 12/18/24 words (=3D 128/192/256 bits of entr=
opy).<br>
<div class=3D""><br>
> - BIP 39 doesn't have a genesis date field, so no optimization dur=
ing blockchain rescan.<br>
<br>
</div>This is nice addition, indeed. But we needed to limit the data as<br>
possible in order not to increase the number of words needed to be noted<br=
>
down.<br>
<div class=3D""><br>
> - BIP 39 doesn't have password typo detection. No easy way to reco=
ver a password if you know most of it.<br>
<br>
</div>It has a detection. Not correction though.<br>
<div class=3D""><br>
> - BIP 39 does not have a user selectable KDF, only 2048 round PBKDF2-H=
MAC-SHA512.<br>
> - BIP 39 can't outsource the KDF computation to a 3rd party.<br>
<br>
</div>True, but having one or two solid options are better than having<br>
gazillions of possible options.<br>
<div class=3D""><br>
> - BIP 39 wallet implementors can use their own word lists, breaking cr=
oss wallet compatibility.<br>
<br>
</div>True, but they are encouraged to use the list provided. Possibility t=
o<br>
outsource KDF outside of your "standard" breaks much more compati=
bility<br>
than this.<br>
<br>
--<br>
Best Regards / S pozdravom,<br>
<br>
Pavol Rusnak <<a href=3D"mailto:stick@gk2.sk">stick@gk2.sk</a>><br>
<br>
---------------------------------------------------------------------------=
---<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</blockquote></div><br></div>
--bcaec548a8e99240d004f46b9d30--
|
