summaryrefslogtreecommitdiff
path: root/7b/73a35b95cae2b0de14901c131c80d068645600
blob: 27fec3b3ce50b05daa913d605df7fc640bb919f7 (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
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
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <harro84@yahoo.com.au>) id 1YVss9-00038r-Fb
	for Bitcoin-development@lists.sourceforge.net;
	Thu, 12 Mar 2015 02:29:17 +0000
Received: from nm35-vm5.bullet.mail.bf1.yahoo.com ([72.30.238.77])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YVss7-0007f6-7a
	for Bitcoin-development@lists.sourceforge.net;
	Thu, 12 Mar 2015 02:29:17 +0000
Received: from [66.196.81.170] by nm35.bullet.mail.bf1.yahoo.com with NNFMP;
	12 Mar 2015 02:16:40 -0000
Received: from [98.139.212.220] by tm16.bullet.mail.bf1.yahoo.com with NNFMP;
	12 Mar 2015 02:16:39 -0000
Received: from [127.0.0.1] by omp1029.mail.bf1.yahoo.com with NNFMP;
	12 Mar 2015 02:16:39 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 966967.23446.bm@omp1029.mail.bf1.yahoo.com
X-YMail-OSG: CQ7KhucVM1mkAmIMGB9C3Wgj0L2Ufy5N7XR1krnP7l97RSFdtk4UNEqilk9bYKD
	P17IlfroeEV1NbknkHSctTiRLTnCWvnmAxb_tEUgD3rb0STUG9WS1ktsYBVMyd7_DxZBq0qmjINb
	8tmF7O3z.EU_NqZS_OllUXdZ1YD42VhS36wG2BgeuoYM2mAju2sn_bpJMAQsRnV.BHgV1iPCC2IT
	iLa4A_ibU3GLk1M9OX49WSiIDglqO.odwUfdgDDf9kBSu6nRQVGwhltqRu1v8sfkyZgSYVP4ORBp
	UOWyfNg0N4_ASJOQNJHnLSwJLlJASkEHKVpEmkqKO4kDGsQjOw8grvpwzvmHCjOQlw3QePOfaB4T
	Gv7E_LWbuCOXl43AE0jOe1mafzfIVFHHMx6nvSp6GLR.jM7iQlRlJk79V0TAgjxOXJ3cx3vKLnLC
	KAqyo6.1QhBC4yIRmeKCwAgRM4ZqMcpPkbDK8vOZakIh3xtfYQeN5IOPlFuWCfu2xfAOMyk.jpGp
	t4Zv85uWLNTVwxz.HNxPF
Received: by 66.196.80.148; Thu, 12 Mar 2015 02:16:39 +0000 
Date: Thu, 12 Mar 2015 02:16:38 +0000 (UTC)
From: Thy Shizzle <thashiznets@yahoo.com.au>
To: "thomasv@electrum.org" <thomasv@electrum.org>
Message-ID: <1301469616.4369014.1426126598899.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <1353069350.4360497.1426126034565.JavaMail.yahoo@mail.yahoo.com>
References: <1353069350.4360497.1426126034565.JavaMail.yahoo@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_4369013_1590000418.1426126598884"
X-Spam-Score: 1.2 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(harro84[at]yahoo.com.au)
	0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
	digit (harro84[at]yahoo.com.au)
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-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
	-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
	no trust [72.30.238.77 listed in list.dnswl.org]
	0.0 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YVss7-0007f6-7a
Cc: "Bitcoin-development@lists.sourceforge.net"
	<Bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Electrum 2.0 has been tagged
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Thy Shizzle <thashiznets@yahoo.com.au>
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: Thu, 12 Mar 2015 02:29:17 -0000

------=_Part_4369013_1590000418.1426126598884
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

That's disappointing the Electrum 2.0 doesn't use BIP39.
From my interpretation of BIP39, wordlists DO NOT=C2=A0REQUIRE to be fixed =
between wallet providers.=C2=A0There is some recommendations regarding the =
wordlists to help with things such as predictive text, so mobile apps can e=
asily predict the word being typed in after a few chars etc. This would see=
m to be the reasoning for the reference word lists. Now there is nothing st=
opping one from implementing a wordlist of say profanities or star wars ter=
ms or whatever and still accepting a mnemonic from another provider. Rememb=
er if you have a mnemonic from a different wordlist, simply Normalization o=
f the words occurs and then the hashing the mnemonic=C2=A0to derive the see=
d bytes. It is not really a restriction at all! BIP39 was designed such tha=
t the mnemonic generation is decoupled from seed derivation, just like what=
 you are saying Electrum 2.0 can do! The wordlist is only needed for mnemon=
ic generation NOT seed derivation, so Electrum DOES NOT need a copy of the =
BIP39 word lists to generate the seed from the phrase, there is really not =
much reason for Electrum not to accept BIP39 mnemonics at the moment! it re=
quires bugger all code! Here is my seed generation code



//literally this is the bulk of the decoupled seed generation code, easy.by=
te[] salt =3D Utilities.MergeByteArrays(UTF8Encoding.UTF8.GetBytes(cSaltHea=
der),_passphraseBytes);return Rfc2898_pbkdf2_hmacsha512.PBKDF2(UTF8Encoding=
.UTF8.GetBytes(Utilities.NormaliseStringNfkd(MnemonicSentence)), salt);

Changing the wordlist in the future has ZERO effect on derived seed, whatev=
er mnemonic you provide will always generate the same seed, BIP39 is not ma=
pping the words back to numbers etc to derive seed.
Version is something that can be dealt with after the fact, hopefully stand=
ardised (curious why didn't you work with the BIP39 to insert version inste=
ad of do something different to BIP39?)
So most of what you are suggesting as problems are not.
As for the common words between languages, I have discussed this with the p=
rovider of the Chinese wordlists as they shared some words between simplifi=
ed and traditional, but I found it easy to look for a word in the mnemonic =
that is unique to that language/wordlist and so straight away you can deter=
mine the language, remembering you get minimum 12 goes at doing that :)
Also then I asked myself, do we really care about detecting the language? P=
robably not because we don't need to use the wordlist ever again after crea=
tion, we literally accept the mnemonic, normalise it then hash it into a se=
ed. From what I'm reading, Electrum 2.0 really should have BIP39, it would =
take almost no effort to put it in and I think you should do that :) I don'=
t have any interest in BIP39 other than it being a standard. I think TREZOR=
 may have an interest in it?
Thomas V:
"Thanks Mike, and sorry to answer a bit late; it has been a busy couple
of weeks.

You are correct, a BIP39 seed phrase will not work in Electrum, and vice
versa. It is indeed unfortunate. However, I believe BIP39 should not be
followed, because it reproduces two mistakes I did when I designed the
older Electrum seed system. Let me explain.

The first problem I have with BIP39 is that the seed phrase does not
include a version number.

Wallet development is still in an exploratory phase, and we should
expect even more innovation in this domain. In this context, it is
unwise to make decisions that prevent future innovation.

However, when we give a seed phrase to users, we have a moral obligation
to keep supporting this seed phrase in future versions. We cannot simply
announce to Electrum users that their old seed phrase is not supported
anymore, because we created a new version of the software that uses a
different derivation. This could lead to financial losses for users who
are unaware of these technicalities. Well, at least, that is how I feel
about it.

BIP39 and Electrum v2 have a very different ways of handling future
innovation. Electrum v2 seed phrases include an explicit version number,
that indicates how the wallet addresses should be derived. In contrast,
BIP39 seed phrases do not include a version number at all. BIP39 is
meant to be combined with BIP43, which stipulates that the wallet
structure should depend on the BIP32 derivation path used for the wallet
(although BIP43 is not followed by all BIP39 compatible wallets). Thus,
innovation in BIP43 is allowed only within the framework of BIP32. In
addition, having to explore the branches of the BIP32 tree in order to
determine the type of wallet attached to a seed might be somewhat
inefficient.

The second problem I see with BIP39 is that it requires a fixed
wordlist. Of course, this forbids innovation in the wordlist itself, but
that's not the main problem. When you write a new standard, it is
important to keep this standard minimal, given the goal you want to
achieve. I believe BIP39 could (and should) have been written without
including the wordlist in the standard.

There are two ways to derive a master key from a mnemonic phrase:
=C2=A01. A bidirectional mapping between words and numbers, as in old
Electrum versions. Pros: bidirectional means that you can do Shamir
secret sharing of your seed. Cons: It requires a fixed wordlist.
=C2=A02. Use a hash of the seed phrase (pbkdf). Pros: a fixed wordlist is n=
ot
required. Cons: the mapping isn't bidirectional.

Electrum v1 uses (1). Electrum v2 uses (2).

Early versions of BIP39 used (1), and later they switched to (2).
However, BIP39 uses (2) only in order to derive the wallet keys, not for
its checksum. The BIP39 checksum uses (1), and it does requires a fixed
wordlist. This is just plainly inconsistent. As a result, you have
neither wordlist flexibility, nor Shamir secret sharing.

Having a fixed wordlist is very unfortunate. First, it means that BIP39
will probably never leave the 'draft' stage, until all languages of the
world have been added. Second, once you add a wordlist for a new
language, you cannot change it anymore, because it will break existing
seed phrases; therefore you have to be extremely careful in the way you
design these wordlists. Third, languages often have words in common.
When you add a new language to the list, you should not use words
already used by existing wordlists, in order to ensure that the language
can be detected. It leads to a first come first served situation, that
might not be sustainable in the future.

In order to support the old Electrum v1 seeds, all future versions of
Electrum will have to include the old wordlist. In addition, when
generating new seed phrases, Electrum now has to avoid collisions with
old seed phrases, because the old ones did not have a version number.
This is painful enough, I will not repeat the same errors twice.

Electrum v2 derives both its private keys and its checksum/version
number using a hash of the seed phrase. This means that wordlists can be
added and modified in the future, without breaking existing seed
phrases. It also means that it will be very easy for other wallets to
support Electrum seedphrases: it requires about 20 lines of code, and no
wordlist is required."


Thomas


Le 02/03/2015 16:37, Mike Hearn a =C3=A9crit :
> Congrats Thomas! Glad to see Electrum 2 finally launch.
>=20
>=20
>> * New seed derivation method (not compatible with BIP39).
>=20
>=20
> Does this mean a "12 words" wallet created by Electrum won't work if
> imported into some other wallet that supports BIP39? Vice versa? This see=
ms
> unfortunate. I guess if seeds are being represented with 12 words
> consistently, people will expect them to work everywhere.
>=20

---------------------------------------------------------------------------=
---
Dive into the World of Parallel Programming The Go Parallel Website, sponso=
red
by Intel and developed in partnership with Slashdot Media, is your hub for =
all
things parallel software development, from weekly thought leadership blogs =
to
news, videos, case studies, tutorials and more. Take a look and join the=20
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
Bitcoin-development --
| =C2=A0 |
| =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 | =C2=A0 |
| Bitcoin-development --To see the collection of prior postings to the list=
, visit the Bitcoin-development Archives. |
|  |
| View on lists.sourceforge.net | Preview by Yahoo |
|  |
| =C2=A0 |

 =C2=A0

=20
   
------=_Part_4369013_1590000418.1426126598884
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lvetica Neue-Light, Helvetica Neue Light, Helvetica Neue, Helvetica, Arial,=
 Lucida Grande, Sans-Serif;font-size:16px"><div><span></span>That's disappo=
inting the Electrum 2.0 doesn't use BIP39.</div><div id=3D"yui_3_16_0_1_142=
6122660566_15770"><br></div><div id=3D"yui_3_16_0_1_1426122660566_15774">Fr=
om my interpretation of BIP39, wordlists DO NOT&nbsp;REQUIRE to be fixed be=
tween wallet providers.&nbsp;There is some recommendations regarding the wo=
rdlists to help with things such as predictive text, so mobile apps can eas=
ily predict the word being typed in after a few chars etc. This would seem =
to be the reasoning for the reference word lists. Now there is nothing stop=
ping one from implementing a wordlist of say profanities or star wars terms=
 or whatever and still accepting a mnemonic from another provider. Remember=
 if you have a mnemonic from a different wordlist, simply Normalization of =
the words occurs and then the hashing the mnemonic&nbsp;to derive the seed =
bytes. It is not really a restriction at all! BIP39 was designed such that =
the mnemonic generation is decoupled from seed derivation, just like what y=
ou are saying Electrum 2.0 can do! The wordlist is only needed for mnemonic=
 generation NOT seed derivation, so Electrum DOES NOT need a copy of the BI=
P39 word lists to generate the seed from the phrase, there is really not mu=
ch reason for Electrum not to accept BIP39 mnemonics at the moment! it requ=
ires bugger all code! Here is my seed generation code</div><div><br></div><=
div class=3D"qtdSeparateBR"><br><br></div><div class=3D"yahoo_quoted" id=3D=
"yui_3_16_0_1_1426122660566_12773" style=3D"display: block;"><div id=3D"yui=
_3_16_0_1_1426122660566_12772" style=3D"font-family: Helvetica Neue-Light, =
Helvetica Neue Light, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans=
-Serif; font-size: 16px;"><div id=3D"yui_3_16_0_1_1426122660566_12771" styl=
e=3D"font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida G=
rande, Sans-Serif; font-size: 16px;"><blockquote id=3D"yui_3_16_0_1_1426122=
660566_12770" style=3D"padding-left: 5px; margin-top: 5px; margin-left: 5px=
; border-left-color: rgb(16, 16, 255); border-left-width: 2px; border-left-=
style: solid;"><div class=3D"y_msg_container" id=3D"yui_3_16_0_1_1426122660=
566_12769"><div id=3D"yiv4337945889"><div id=3D"yui_3_16_0_1_1426122660566_=
12768"><div id=3D"yui_3_16_0_1_1426122660566_12767" style=3D"color: rgb(0, =
0, 0); font-family: Helvetica Neue-Light, Helvetica Neue Light, Helvetica N=
eue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 16px; backgrou=
nd-color: rgb(255, 255, 255);"><div id=3D"yiv4337945889yui_3_16_0_1_1426122=
660566_5715" dir=3D"ltr"><font id=3D"yiv4337945889yui_3_16_0_1_142612266056=
6_5726" color=3D"#57a64a" face=3D"Consolas" size=3D"2">//literally this is =
the bulk of the decoupled seed generation code, easy.</font></div><div id=
=3D"yiv4337945889yui_3_16_0_1_1426122660566_5467"><font id=3D"yiv4337945889=
yui_3_16_0_1_1426122660566_5692" color=3D"#569cd6" face=3D"Consolas" size=
=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5691" color=3D"#=
569cd6" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_=
1426122660566_5690" color=3D"#569cd6" face=3D"Consolas" size=3D"2">byte</fo=
nt></font></font><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5739" =
color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui=
_3_16_0_1_1426122660566_5738" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2=
"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5737" color=3D"#dcdcd=
c" face=3D"Consolas" size=3D"2">[] salt </font></font></font><font color=3D=
"#b4b4b4" face=3D"Consolas" size=3D"2"><font color=3D"#b4b4b4" face=3D"Cons=
olas" size=3D"2"><font color=3D"#b4b4b4" face=3D"Consolas" size=3D"2">=3D</=
font></font></font><font color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><fo=
nt color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font color=3D"#dcdcdc" f=
ace=3D"Consolas" size=3D"2"> </font></font></font><font id=3D"yiv4337945889=
yui_3_16_0_1_1426122660566_5735" color=3D"#4ec9b0" face=3D"Consolas" size=
=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5734" color=3D"#=
4ec9b0" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_=
1426122660566_5733" color=3D"#4ec9b0" face=3D"Consolas" size=3D"2">Utilitie=
s</font></font></font><font color=3D"#b4b4b4" face=3D"Consolas" size=3D"2">=
<font color=3D"#b4b4b4" face=3D"Consolas" size=3D"2"><font color=3D"#b4b4b4=
" face=3D"Consolas" size=3D"2">.</font></font></font><font id=3D"yiv4337945=
889yui_3_16_0_1_1426122660566_5732" color=3D"#dcdcdc" face=3D"Consolas" siz=
e=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5731" color=3D"=
#dcdcdc" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1=
_1426122660566_5730" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2">MergeBy=
teArrays(</font></font></font><font id=3D"yiv4337945889yui_3_16_0_1_1426122=
660566_5729" color=3D"#4ec9b0" face=3D"Consolas" size=3D"2"><font id=3D"yiv=
4337945889yui_3_16_0_1_1426122660566_5728" color=3D"#4ec9b0" face=3D"Consol=
as" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5727" co=
lor=3D"#4ec9b0" face=3D"Consolas" size=3D"2">UTF8Encoding</font></font></fo=
nt><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5749" color=3D"#b4b4=
b4" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426=
122660566_5748" color=3D"#b4b4b4" face=3D"Consolas" size=3D"2"><font id=3D"=
yiv4337945889yui_3_16_0_1_1426122660566_5747" color=3D"#b4b4b4" face=3D"Con=
solas" size=3D"2">.</font></font></font><font id=3D"yiv4337945889yui_3_16_0=
_1_1426122660566_5752" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font=
 id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5751" color=3D"#dcdcdc" face=
=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_142612266056=
6_5750" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2">UTF8</font></font></=
font><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5755" color=3D"#b4=
b4b4" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_14=
26122660566_5754" color=3D"#b4b4b4" face=3D"Consolas" size=3D"2"><font id=
=3D"yiv4337945889yui_3_16_0_1_1426122660566_5753" color=3D"#b4b4b4" face=3D=
"Consolas" size=3D"2">.</font></font></font><font id=3D"yiv4337945889yui_3_=
16_0_1_1426122660566_5466" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><=
font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5465" color=3D"#dcdcdc" =
face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_14261226=
60566_5464" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2">GetBytes(cSaltHe=
ader),_passphraseBytes);</font></font></font></div><div id=3D"yiv4337945889=
yui_3_16_0_1_1426122660566_5472"><font color=3D"#dcdcdc" face=3D"Consolas" =
size=3D"2"><font color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font color=
=3D"#dcdcdc" face=3D"Consolas" size=3D"2"></font></font></font><font id=3D"=
yiv4337945889yui_3_16_0_1_1426122660566_5743" color=3D"#569cd6" face=3D"Con=
solas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5742"=
 color=3D"#569cd6" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yu=
i_3_16_0_1_1426122660566_5741" color=3D"#569cd6" face=3D"Consolas" size=3D"=
2">return</font></font></font><font color=3D"#dcdcdc" face=3D"Consolas" siz=
e=3D"2"><font color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font color=3D=
"#dcdcdc" face=3D"Consolas" size=3D"2"> </font></font></font><font id=3D"yi=
v4337945889yui_3_16_0_1_1426122660566_5478" color=3D"#4ec9b0" face=3D"Conso=
las" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5477" c=
olor=3D"#4ec9b0" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_=
3_16_0_1_1426122660566_5476" color=3D"#4ec9b0" face=3D"Consolas" size=3D"2"=
>Rfc2898_pbkdf2_hmacsha512</font></font></font><font color=3D"#b4b4b4" face=
=3D"Consolas" size=3D"2"><font color=3D"#b4b4b4" face=3D"Consolas" size=3D"=
2"><font color=3D"#b4b4b4" face=3D"Consolas" size=3D"2">.</font></font></fo=
nt><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5771" color=3D"#dcdc=
dc" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426=
122660566_5770" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font id=3D"=
yiv4337945889yui_3_16_0_1_1426122660566_5769" color=3D"#dcdcdc" face=3D"Con=
solas" size=3D"2">PBKDF2(</font></font></font><font id=3D"yiv4337945889yui_=
3_16_0_1_1426122660566_5746" color=3D"#4ec9b0" face=3D"Consolas" size=3D"2"=
><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5745" color=3D"#4ec9b0=
" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_142612=
2660566_5744" color=3D"#4ec9b0" face=3D"Consolas" size=3D"2">UTF8Encoding</=
font></font></font><font color=3D"#b4b4b4" face=3D"Consolas" size=3D"2"><fo=
nt color=3D"#b4b4b4" face=3D"Consolas" size=3D"2"><font color=3D"#b4b4b4" f=
ace=3D"Consolas" size=3D"2">.</font></font></font><font color=3D"#dcdcdc" f=
ace=3D"Consolas" size=3D"2"><font color=3D"#dcdcdc" face=3D"Consolas" size=
=3D"2"><font color=3D"#dcdcdc" face=3D"Consolas" size=3D"2">UTF8</font></fo=
nt></font><font color=3D"#b4b4b4" face=3D"Consolas" size=3D"2"><font color=
=3D"#b4b4b4" face=3D"Consolas" size=3D"2"><font color=3D"#b4b4b4" face=3D"C=
onsolas" size=3D"2">.</font></font></font><font id=3D"yiv4337945889yui_3_16=
_0_1_1426122660566_5725" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><fo=
nt id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5724" color=3D"#dcdcdc" fa=
ce=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660=
566_5723" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2">GetBytes(</font></=
font></font><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5797" color=
=3D"#4ec9b0" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_16=
_0_1_1426122660566_5796" color=3D"#4ec9b0" face=3D"Consolas" size=3D"2"><fo=
nt id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5795" color=3D"#4ec9b0" fa=
ce=3D"Consolas" size=3D"2">Utilities</font></font></font><font color=3D"#b4=
b4b4" face=3D"Consolas" size=3D"2"><font color=3D"#b4b4b4" face=3D"Consolas=
" size=3D"2"><font color=3D"#b4b4b4" face=3D"Consolas" size=3D"2">.</font><=
/font></font><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5475" colo=
r=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337945889yui_3_1=
6_0_1_1426122660566_5474" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><f=
ont id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5473" color=3D"#dcdcdc" f=
ace=3D"Consolas" size=3D"2">NormaliseStringNfkd(MnemonicSentence)), salt);<=
/font></font></font></div><font id=3D"yiv4337945889yui_3_16_0_1_14261226605=
66_5493" color=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><font id=3D"yiv4337=
945889yui_3_16_0_1_1426122660566_5492" color=3D"#dcdcdc" face=3D"Consolas" =
size=3D"2"><font id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5491" color=
=3D"#dcdcdc" face=3D"Consolas" size=3D"2"><div id=3D"yiv4337945889yui_3_16_=
0_1_1426122660566_5620"><br></div></font></font></font><div id=3D"yiv433794=
5889yui_3_16_0_1_1426122660566_5463" dir=3D"ltr"><br></div><div id=3D"yui_3=
_16_0_1_1426122660566_16038" dir=3D"ltr">Changing the wordlist in the futur=
e has ZERO effect on derived seed, whatever mnemonic you provide will alway=
s generate the same seed, BIP39 is not mapping the words back to numbers et=
c to derive seed.</div><div id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5=
783"><br></div><div id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5784">Ver=
sion is something that can be dealt with after the fact, hopefully standard=
ised (curious why didn't you work with the BIP39 to insert version instead =
of do something different to BIP39?)</div><div id=3D"yiv4337945889yui_3_16_=
0_1_1426122660566_5360" dir=3D"ltr"><br></div><div id=3D"yiv4337945889yui_3=
_16_0_1_1426122660566_5831" dir=3D"ltr">So most of what you are suggesting =
as problems are not.</div><div id=3D"yiv4337945889yui_3_16_0_1_142612266056=
6_5832" dir=3D"ltr"><br></div><div id=3D"yiv4337945889yui_3_16_0_1_14261226=
60566_5874" dir=3D"ltr">As for the common words between languages, I have d=
iscussed this with the provider of the Chinese wordlists as they shared som=
e words between simplified and traditional, but I found it easy to look for=
 a word in the mnemonic that is unique to that language/wordlist and so str=
aight away you can determine the language, remembering you get minimum 12 g=
oes at doing that :)</div><div id=3D"yiv4337945889yui_3_16_0_1_142612266056=
6_5873" dir=3D"ltr"><br></div><div id=3D"yiv4337945889yui_3_16_0_1_14261226=
60566_5872" dir=3D"ltr">Also then I asked myself, do we really care about d=
etecting the language? Probably not because we don't need to use the wordli=
st ever again after creation, we literally accept the mnemonic, normalise i=
t then hash it into a seed. From what I'm reading, Electrum 2.0 really shou=
ld have BIP39, it would take almost no effort to put it in and I think you =
should do that :) I don't have any interest in BIP39 other than it being a =
standard. I think TREZOR may have an interest in it?</div><div id=3D"yiv433=
7945889yui_3_16_0_1_1426122660566_5894" dir=3D"ltr"><br></div><div id=3D"yi=
v4337945889yui_3_16_0_1_1426122660566_5168" dir=3D"ltr">Thomas V:</div><div=
 id=3D"yiv4337945889yui_3_16_0_1_1426122660566_5043" dir=3D"ltr"><br></div>=
<div id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4964">"Thanks Mike, and =
sorry to answer a bit late; it has been a busy couple<br id=3D"yiv433794588=
9yui_3_16_0_1_1426122660566_4954">of weeks.<br id=3D"yiv4337945889yui_3_16_=
0_1_1426122660566_4953"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4=
952">You are correct, a BIP39 seed phrase will not work in Electrum, and vi=
ce<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4951">versa. It is inde=
ed unfortunate. However, I believe BIP39 should not be<br id=3D"yiv43379458=
89yui_3_16_0_1_1426122660566_4950">followed, because it reproduces two mist=
akes I did when I designed the<br id=3D"yiv4337945889yui_3_16_0_1_142612266=
0566_4949">older Electrum seed system. Let me explain.<br id=3D"yiv43379458=
89yui_3_16_0_1_1426122660566_4948"><br id=3D"yiv4337945889yui_3_16_0_1_1426=
122660566_4947">The first problem I have with BIP39 is that the seed phrase=
 does not<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4946">include a =
version number.<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4945"><br =
id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4944">Wallet development is s=
till in an exploratory phase, and we should<br id=3D"yiv4337945889yui_3_16_=
0_1_1426122660566_4943">expect even more innovation in this domain. In this=
 context, it is<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4942">unwi=
se to make decisions that prevent future innovation.<br id=3D"yiv4337945889=
yui_3_16_0_1_1426122660566_4941"><br id=3D"yiv4337945889yui_3_16_0_1_142612=
2660566_4940">However, when we give a seed phrase to users, we have a moral=
 obligation<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4939">to keep =
supporting this seed phrase in future versions. We cannot simply<br id=3D"y=
iv4337945889yui_3_16_0_1_1426122660566_4938">announce to Electrum users tha=
t their old seed phrase is not supported<br id=3D"yiv4337945889yui_3_16_0_1=
_1426122660566_4937">anymore, because we created a new version of the softw=
are that uses a<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4936">diff=
erent derivation. This could lead to financial losses for users who<br id=
=3D"yiv4337945889yui_3_16_0_1_1426122660566_4935">are unaware of these tech=
nicalities. Well, at least, that is how I feel<br id=3D"yiv4337945889yui_3_=
16_0_1_1426122660566_4934">about it.<br id=3D"yiv4337945889yui_3_16_0_1_142=
6122660566_4933"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4932">BI=
P39 and Electrum v2 have a very different ways of handling future<br id=3D"=
yiv4337945889yui_3_16_0_1_1426122660566_4931">innovation. Electrum v2 seed =
phrases include an explicit version number,<br id=3D"yiv4337945889yui_3_16_=
0_1_1426122660566_4930">that indicates how the wallet addresses should be d=
erived. In contrast,<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4929"=
>BIP39 seed phrases do not include a version number at all. BIP39 is<br id=
=3D"yiv4337945889yui_3_16_0_1_1426122660566_4928">meant to be combined with=
 BIP43, which stipulates that the wallet<br id=3D"yiv4337945889yui_3_16_0_1=
_1426122660566_4927">structure should depend on the BIP32 derivation path u=
sed for the wallet<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4926">(=
although BIP43 is not followed by all BIP39 compatible wallets). Thus,<br i=
d=3D"yiv4337945889yui_3_16_0_1_1426122660566_4925">innovation in BIP43 is a=
llowed only within the framework of BIP32. In<br id=3D"yiv4337945889yui_3_1=
6_0_1_1426122660566_4924">addition, having to explore the branches of the B=
IP32 tree in order to<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4923=
">determine the type of wallet attached to a seed might be somewhat<br id=
=3D"yiv4337945889yui_3_16_0_1_1426122660566_4922">inefficient.<br id=3D"yiv=
4337945889yui_3_16_0_1_1426122660566_4921"><br id=3D"yiv4337945889yui_3_16_=
0_1_1426122660566_4920">The second problem I see with BIP39 is that it requ=
ires a fixed<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4919">wordlis=
t. Of course, this forbids innovation in the wordlist itself, but<br id=3D"=
yiv4337945889yui_3_16_0_1_1426122660566_4918">that's not the main problem. =
When you write a new standard, it is<br id=3D"yiv4337945889yui_3_16_0_1_142=
6122660566_4917">important to keep this standard minimal, given the goal yo=
u want to<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4916">achieve. I=
 believe BIP39 could (and should) have been written without<br id=3D"yiv433=
7945889yui_3_16_0_1_1426122660566_4915">including the wordlist in the stand=
ard.<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4914"><br id=3D"yiv43=
37945889yui_3_16_0_1_1426122660566_4913">There are two ways to derive a mas=
ter key from a mnemonic phrase:<br id=3D"yiv4337945889yui_3_16_0_1_14261226=
60566_4912">&nbsp;1. A bidirectional mapping between words and numbers, as =
in old<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4911">Electrum vers=
ions. Pros: bidirectional means that you can do Shamir<br id=3D"yiv43379458=
89yui_3_16_0_1_1426122660566_4910">secret sharing of your seed. Cons: It re=
quires a fixed wordlist.<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4=
909">&nbsp;2. Use a hash of the seed phrase (pbkdf). Pros: a fixed wordlist=
 is not<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4908">required. Co=
ns: the mapping isn't bidirectional.<br id=3D"yiv4337945889yui_3_16_0_1_142=
6122660566_4907"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4906">El=
ectrum v1 uses (1). Electrum v2 uses (2).<br id=3D"yiv4337945889yui_3_16_0_=
1_1426122660566_4905"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_490=
4">Early versions of BIP39 used (1), and later they switched to (2).<br id=
=3D"yiv4337945889yui_3_16_0_1_1426122660566_4903">However, BIP39 uses (2) o=
nly in order to derive the wallet keys, not for<br id=3D"yiv4337945889yui_3=
_16_0_1_1426122660566_4902">its checksum. The BIP39 checksum uses (1), and =
it does requires a fixed<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4=
901">wordlist. This is just plainly inconsistent. As a result, you have<br =
id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4900">neither wordlist flexib=
ility, nor Shamir secret sharing.<br id=3D"yiv4337945889yui_3_16_0_1_142612=
2660566_4899"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4898">Havin=
g a fixed wordlist is very unfortunate. First, it means that BIP39<br id=3D=
"yiv4337945889yui_3_16_0_1_1426122660566_4897">will probably never leave th=
e 'draft' stage, until all languages of the<br id=3D"yiv4337945889yui_3_16_=
0_1_1426122660566_4896">world have been added. Second, once you add a wordl=
ist for a new<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4895">langua=
ge, you cannot change it anymore, because it will break existing<br id=3D"y=
iv4337945889yui_3_16_0_1_1426122660566_4894">seed phrases; therefore you ha=
ve to be extremely careful in the way you<br id=3D"yiv4337945889yui_3_16_0_=
1_1426122660566_4893">design these wordlists. Third, languages often have w=
ords in common.<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4892">When=
 you add a new language to the list, you should not use words<br id=3D"yiv4=
337945889yui_3_16_0_1_1426122660566_4891">already used by existing wordlist=
s, in order to ensure that the language<br id=3D"yiv4337945889yui_3_16_0_1_=
1426122660566_4890">can be detected. It leads to a first come first served =
situation, that<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4889">migh=
t not be sustainable in the future.<br id=3D"yiv4337945889yui_3_16_0_1_1426=
122660566_4888"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4887">In =
order to support the old Electrum v1 seeds, all future versions of<br id=3D=
"yiv4337945889yui_3_16_0_1_1426122660566_4886">Electrum will have to includ=
e the old wordlist. In addition, when<br id=3D"yiv4337945889yui_3_16_0_1_14=
26122660566_4885">generating new seed phrases, Electrum now has to avoid co=
llisions with<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4884">old se=
ed phrases, because the old ones did not have a version number.<br id=3D"yi=
v4337945889yui_3_16_0_1_1426122660566_4883">This is painful enough, I will =
not repeat the same errors twice.<br id=3D"yiv4337945889yui_3_16_0_1_142612=
2660566_4882"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4881">Elect=
rum v2 derives both its private keys and its checksum/version<br id=3D"yiv4=
337945889yui_3_16_0_1_1426122660566_4880">number using a hash of the seed p=
hrase. This means that wordlists can be<br id=3D"yiv4337945889yui_3_16_0_1_=
1426122660566_4879">added and modified in the future, without breaking exis=
ting seed<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4878">phrases. I=
t also means that it will be very easy for other wallets to<br id=3D"yiv433=
7945889yui_3_16_0_1_1426122660566_4877">support Electrum seedphrases: it re=
quires about 20 lines of code, and no<br id=3D"yiv4337945889yui_3_16_0_1_14=
26122660566_4876">wordlist is required."<br id=3D"yiv4337945889yui_3_16_0_1=
_1426122660566_4875"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4874=
"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4873">Thomas<br id=3D"y=
iv4337945889yui_3_16_0_1_1426122660566_4872"><br id=3D"yiv4337945889yui_3_1=
6_0_1_1426122660566_4871"><br id=3D"yiv4337945889yui_3_16_0_1_1426122660566=
_4870">Le 02/03/2015 16:37, Mike Hearn a =C3=A9crit :<br id=3D"yiv433794588=
9yui_3_16_0_1_1426122660566_4869">&gt; Congrats Thomas! Glad to see Electru=
m 2 finally launch.<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4868">=
&gt; <br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4867">&gt; <br id=3D=
"yiv4337945889yui_3_16_0_1_1426122660566_4866">&gt;&gt; * New seed derivati=
on method (not compatible with BIP39).<br id=3D"yiv4337945889yui_3_16_0_1_1=
426122660566_4865">&gt; <br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4=
864">&gt; <br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4863">&gt; Does=
 this mean a "12 words" wallet created by Electrum won't work if<br id=3D"y=
iv4337945889yui_3_16_0_1_1426122660566_4862">&gt; imported into some other =
wallet that supports BIP39? Vice versa? This seems<br id=3D"yiv4337945889yu=
i_3_16_0_1_1426122660566_4861">&gt; unfortunate. I guess if seeds are being=
 represented with 12 words<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566=
_4860">&gt; consistently, people will expect them to work everywhere.<br id=
=3D"yiv4337945889yui_3_16_0_1_1426122660566_4859">&gt; <br id=3D"yiv4337945=
889yui_3_16_0_1_1426122660566_4858"><br id=3D"yiv4337945889yui_3_16_0_1_142=
6122660566_4857">----------------------------------------------------------=
--------------------<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4856"=
>Dive into the World of Parallel Programming The Go Parallel Website, spons=
ored<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4855">by Intel and de=
veloped in partnership with Slashdot Media, is your hub for all<br id=3D"yi=
v4337945889yui_3_16_0_1_1426122660566_4854">things parallel software develo=
pment, from weekly thought leadership blogs to<br id=3D"yiv4337945889yui_3_=
16_0_1_1426122660566_4853">news, videos, case studies, tutorials and more. =
Take a look and join the <br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_=
4852">conversation now. http://goparallel.sourceforge.net/<br id=3D"yiv4337=
945889yui_3_16_0_1_1426122660566_4851">____________________________________=
___________<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4850">Bitcoin-=
development mailing list<br id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4=
849">Bitcoin-development@lists.sourceforge.net<br id=3D"yiv4337945889yui_3_=
16_0_1_1426122660566_4848"><a id=3D"yiv4337945889ms__id3682" href=3D"https:=
//lists.sourceforge.net/lists/listinfo/bitcoin-development" target=3D"_blan=
k" rel=3D"nofollow">Bitcoin-development --</a></div><div class=3D"yiv433794=
5889link-enhancr-attachment yiv4337945889link-enhancr-element" id=3D"yiv433=
7945889enhancrCard_0" style=3D'width: 450px; font-family: "Georgia", "Times=
", "Times New Roman", "serif"; margin-top: 5px; margin-bottom: 5px; backgro=
und-color: rgb(255, 255, 255);'><table class=3D"yiv4337945889link-enhancr-e=
lement" id=3D"yui_3_16_0_1_1426122660566_13002" style=3D"width: 450px; heig=
ht: auto; display: block;" border=3D"0" cellspacing=3D"0" cellpadding=3D"0"=
><tbody id=3D"yui_3_16_0_1_1426122660566_13001"><tr class=3D"yiv4337945889l=
ink-enhancr-element"><td class=3D"yiv4337945889link-enhancr-element" style=
=3D"height: 1px; font-size: 1px; border-collapse: collapse; background-colo=
r: rgb(229, 229, 229);" colspan=3D"7"><div class=3D"yiv4337945889link-enhan=
cr-element" style=3D"height: 1px; line-height: 0px; font-size: 1px; backgro=
und-color: rgb(229, 229, 229);">&nbsp;</div></td></tr><tr class=3D"yiv43379=
45889link-enhancr-element" id=3D"yui_3_16_0_1_1426122660566_13004"><td clas=
s=3D"yiv4337945889link-enhancr-element" style=3D"width: 1px; font-size: 1pt=
; border-collapse: collapse; background-color: rgb(229, 229, 229);" rowspan=
=3D"5"><div class=3D"yiv4337945889link-enhancr-element" style=3D"width: 1px=
; font-size: 1pt; background-color: rgb(229, 229, 229);">&nbsp;</div></td><=
td class=3D"yiv4337945889link-enhancr-element" style=3D"width: 14px; font-s=
ize: 0pt; border-collapse: collapse; background-color: rgb(255, 255, 255);"=
 rowspan=3D"5"><div class=3D"yiv4337945889link-enhancr-element" style=3D"wi=
dth: 14px; font-size: 14pt; background-color: rgb(255, 255, 255);">&nbsp;</=
div></td><td class=3D"yiv4337945889link-enhancr-element" id=3D"yui_3_16_0_1=
_1426122660566_13147" style=3D"height: 6px; font-size: 0pt; border-collapse=
: collapse; background-color: rgb(255, 255, 255);" colspan=3D"2"><div class=
=3D"yiv4337945889link-enhancr-element" id=3D"yui_3_16_0_1_1426122660566_131=
46" style=3D"height: 6px; font-size: 6pt; background-color: rgb(255, 255, 2=
55);">&nbsp;</div></td><td class=3D"yiv4337945889link-enhancr-element" id=
=3D"yui_3_16_0_1_1426122660566_13003" style=3D"width: 20px; font-size: 0pt;=
 border-collapse: collapse; background-color: rgb(255, 255, 255);" rowspan=
=3D"5"><div class=3D"yiv4337945889link-enhancr-element" style=3D"width: 20p=
x; font-size: 20pt; background-color: rgb(255, 255, 255);">&nbsp;</div></td=
><td width=3D"1" class=3D"yiv4337945889link-enhancr-element" style=3D"width=
: 1px; font-size: 1pt; border-collapse: collapse; background-color: rgb(229=
, 229, 229);" rowspan=3D"5"><div class=3D"yiv4337945889link-enhancr-element=
" style=3D"width: 1px; font-size: 1pt; background-color: rgb(229, 229, 229)=
;">&nbsp;</div></td></tr><tr id=3D"yui_3_16_0_1_1426122660566_13000"><td cl=
ass=3D"yiv4337945889link-enhancr-element" id=3D"yui_3_16_0_1_1426122660566_=
12999" style=3D'width: 100%; font-family: "Georgia", "Times", "Times New Ro=
man", "serif"; vertical-align: middle;' colspan=3D"2"><div class=3D"yiv4337=
945889link-enhancr-text-part yiv4337945889link-enhancr-element" id=3D"yui_3=
_16_0_1_1426122660566_12998" style=3D"width: 414px; line-height: 16.5px; ba=
ckground-color: rgb(255, 255, 255);"><div class=3D"yiv4337945889link-enhanc=
r-element" id=3D"yui_3_16_0_1_1426122660566_12997"><span class=3D"yiv433794=
5889link-enhancr-element yiv4337945889icon  yiv4337945889icon-shrink yiv433=
7945889link-enhancr-toggle"></span><span class=3D"yiv4337945889link-enhancr=
-element yiv4337945889icon yiv4337945889icon-close yiv4337945889link-enhanc=
r-delete"></span><a class=3D"yiv4337945889link-enhancr-card-urlWrapper yiv4=
337945889link-enhancr-element" id=3D"yui_3_16_0_1_1426122660566_12996" styl=
e=3D"color: rgb(0, 0, 0); line-height: 100%; font-size: 18px; text-decorati=
on: none; display: block;" href=3D"https://lists.sourceforge.net/lists/list=
info/bitcoin-development" target=3D"_blank" rel=3D"nofollow"><span class=3D=
"yiv4337945889link-enhancr-element yiv4337945889link-enhancr-card-title" id=
=3D"yui_3_16_0_1_1426122660566_15515" style=3D"margin: 0px 0px 3px; color: =
rgb(0, 0, 0); line-height: 21px; overflow: hidden; font-size: 18px; font-we=
ight: normal; display: inline-block; max-height: 43px;">Bitcoin-development=
 --</span></a><div class=3D"yiv4337945889link-enhancr-card-description yiv4=
337945889link-enhancr-element" id=3D"yui_3_16_0_1_1426122660566_15477" styl=
e=3D'color: rgb(153, 153, 153); line-height: 20px; overflow: hidden; font-f=
amily: "Georgia", "Times", "Times New Roman", "serif"; font-size: 13px; max=
-height: 81px;'>To see the collection of prior postings to the list, visit =
the Bitcoin-development Archives.</div></div></div></td></tr><tr id=3D"yui_=
3_16_0_1_1426122660566_15514"><td class=3D"yiv4337945889link-enhancr-elemen=
t" id=3D"yui_3_16_0_1_1426122660566_15513" style=3D"height: 6px; font-size:=
 0pt; border-collapse: collapse; background-color: rgb(255, 255, 255);" col=
span=3D"2"><div class=3D"yiv4337945889link-enhancr-element" id=3D"yui_3_16_=
0_1_1426122660566_15512" style=3D"height: 6px; font-size: 6pt; background-c=
olor: rgb(255, 255, 255);"></div></td></tr><tr id=3D"yui_3_16_0_1_142612266=
0566_15476"><td class=3D"yiv4337945889link-enhancr-element" id=3D"yui_3_16_=
0_1_1426122660566_15475" style=3D'font-family: "Arial", "Helvetica Neue", "=
Helvetica", "sans-serif"; vertical-align: middle;'><div class=3D"yiv4337945=
889link-enhancr-element" id=3D"yui_3_16_0_1_1426122660566_15474" style=3D"f=
ont-size: 0pt;"><a class=3D"yiv4337945889link-enhancr-card-url yiv433794588=
9link-enhancr-element" id=3D"yui_3_16_0_1_1426122660566_15473" style=3D"col=
or: black; text-decoration: none; cursor: pointer;" href=3D"https://lists.s=
ourceforge.net/lists/listinfo/bitcoin-development" target=3D"_blank" rel=3D=
"nofollow"><span class=3D"yiv4337945889link-enhancr-element yiv4337945889li=
nk-enhancr-view-on" id=3D"yiv4337945889yui_3_16_0_1_1426122660566_4959" sty=
le=3D"line-height: 11px; overflow: hidden; display: inline-block; max-heigh=
t: 13px; min-width: 254px; max-width: 314px;"><span class=3D"yiv4337945889l=
ink-enhancr-element yiv4337945889link-enhancr-mobile-no-resize" id=3D"yui_3=
_16_0_1_1426122660566_16041" style=3D"color: rgb(153, 153, 153); line-heigh=
t: 11px; font-size: 9px; vertical-align: middle;">View on <span class=3D"yi=
v4337945889link-enhancr-view-on-domain" id=3D"yui_3_16_0_1_1426122660566_16=
040" style=3D"font-weight: bold;">lists.sourceforge.net</span></span></span=
></a></div></td><td class=3D"yiv4337945889link-enhancr-element" style=3D'wi=
dth: 100px; font-family: "Arial", "Helvetica Neue", "Helvetica", "sans-seri=
f"; vertical-align: middle;'><div class=3D"yiv4337945889link-enhancr-elemen=
t yiv4337945889link-enhancr-preview-wrapper" style=3D"text-align: right; li=
ne-height: 11px; overflow: hidden; font-size: 0pt; max-height: 13px; min-wi=
dth: 80px; max-width: 100px;"><span class=3D"yiv4337945889link-enhancr-elem=
ent yiv4337945889link-enhancr-preview-by yiv4337945889link-enhancr-mobile-n=
o-resize" style=3D"color: rgb(153, 153, 153); line-height: 11px; font-size:=
 9px; vertical-align: middle;">Preview by Yahoo</span></div></td></tr><tr><=
td class=3D"yiv4337945889link-enhancr-element" style=3D"height: 9px; font-s=
ize: 0pt; border-collapse: collapse; background-color: rgb(255, 255, 255);"=
 colspan=3D"2"><div class=3D"yiv4337945889link-enhancr-element" style=3D"he=
ight: 9px; font-size: 9pt; background-color: rgb(255, 255, 255);"></div></t=
d></tr><tr class=3D"yiv4337945889link-enhancr-element"><td class=3D"yiv4337=
945889link-enhancr-element" style=3D"height: 1px; font-size: 1px; border-co=
llapse: collapse; background-color: rgb(229, 229, 229);" colspan=3D"7"><div=
 class=3D"yiv4337945889link-enhancr-element" style=3D"height: 1px; line-hei=
ght: 0px; font-size: 1px; background-color: rgb(229, 229, 229);">&nbsp;</di=
v></td></tr></tbody></table></div><div id=3D"yiv4337945889ms__id3682"> &nbs=
p;</div></div></div></div><br><br></div> </blockquote>  </div> </div>   </d=
iv> </div></body></html>
------=_Part_4369013_1590000418.1426126598884--