summaryrefslogtreecommitdiff
path: root/28/5eeef7c1e5ac6e99047ee5766bd851266c273e
blob: e8cf310b33faa6e74c5470afffc07e387bbdb009 (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
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
Return-Path: <vitteaymeric@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id B57A0F74
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  8 Jan 2018 16:02:05 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f175.google.com (mail-wr0-f175.google.com
	[209.85.128.175])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D1530573
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon,  8 Jan 2018 16:02:03 +0000 (UTC)
Received: by mail-wr0-f175.google.com with SMTP id b76so11268610wrd.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 08 Jan 2018 08:02:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to:content-language;
	bh=W7Jkj7ULos7xgvoeHYqynjAUOqzshIATfZ0JWVmR614=;
	b=H4o/UxZTKxwuxCzDs0hmkg/MXQ7/vSEEpB1csLv5th0mM5IRqllpPaZBkOzVcbz+mS
	Nj7u88wWeDmQMo5ICZA6Zjv5GSz94kfap202cbhm9S196mazIXZGc9yfzWKZteXAeOcD
	7D/TZvK5btdhzqvvNbNWay60kIN9FndqMbpoLjr+QIDv1gHV+CnD1N5ugUw0dDZSZG0r
	f8V8HMoUrvc1Ee/fT72rwr7451eeiHGMq30/0yQNEMVWKhdT/t55Gy99ybzKk367tO/j
	XrNbUxlmI4LOJtc/EmnFnzK4da6oZntK08dEYF11mYBs+KNketeWeet2pi3siWjI158x
	IlYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-language;
	bh=W7Jkj7ULos7xgvoeHYqynjAUOqzshIATfZ0JWVmR614=;
	b=gzkNUk4hj/YDDq4UkG0nrIuZ/LpC/EDFAJdiYt6ovFDjWgc1n6EaCIJqhyGGyJa4EZ
	5aPE8Lh5CTsrSsNhk4dv0pSQgQPZBOiWMpnOJpjY1M1nA1En/HqdpLOnN0oyfyT/qwns
	D++yydfUgNxfLXidAFfC0F/08o16YCgt1eGu/LbTkkfCOHZDblv3Yn+exylhriSr6CCf
	CyLgytBXK6YK7Fkm1nd9e3BOamWQuzHnUIOOwn7MaNcDMC6CwftMnxvWn0qvTsaIyAj2
	HNKZNpPgBhCtxVtC9cg5rEe9GX5QP92086IAlobqmHGHymdEKnLlBcvnBQsfNusgOhTJ
	MqJQ==
X-Gm-Message-State: AKGB3mKk3Z4nhsCFTTpSdJbeapYyLoMJZagWv6ORPRAJ67N0TwcfmikP
	y8IUiszLeVbCYHyxRbFjCQA=
X-Google-Smtp-Source: ACJfBov2rcLmi9dYMVMU3oWy2vMgc6eONujIWhcbfaMEayagfUt20sAqfsTyZocZFvtMlEm0X+qpIQ==
X-Received: by 10.223.177.134 with SMTP id q6mr10489577wra.13.1515427322329;
	Mon, 08 Jan 2018 08:02:02 -0800 (PST)
Received: from ?IPv6:2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17?
	([2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17])
	by smtp.googlemail.com with ESMTPSA id
	m70sm10490715wma.36.2018.01.08.08.02.00
	(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Mon, 08 Jan 2018 08:02:01 -0800 (PST)
To: Greg Sanders <gsanders87@gmail.com>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	Matias Alejo Garcia <ematiu@gmail.com>
References: <57f5fcd8644c6f6472cd6a91144a6152@nym.zone>
	<d05bfa26-4f3d-77d1-5801-9ad59497f334@satoshilabs.com>
	<CACvEmnGcN+VtgK0MeRPBevRoMkyJrMOBQKLZP4NnLBc5+q8Cyg@mail.gmail.com>
	<eb643e5734bceeb918d116fb75c0d4b3@nym.zone>
	<CAB3F3DvcjSRHLYv16SsSb22TxyfdMrsKW-Z4pChEiuTmhG3KYQ@mail.gmail.com>
	<CA+vKqYfo-G4oS4jZpL1_7sx9aTVKcje9NdjCs3Pu9JwW5-GTMQ@mail.gmail.com>
	<CAB3F3DsifkaCVE1xFvvn8+b-ixpq-NqmGd1vAS8V8niB9YLQsA@mail.gmail.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <a1572b86-a7ea-8c4e-21ec-f31c25614cde@gmail.com>
Date: Mon, 8 Jan 2018 17:02:02 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101
	Thunderbird/52.5.2
MIME-Version: 1.0
In-Reply-To: <CAB3F3DsifkaCVE1xFvvn8+b-ixpq-NqmGd1vAS8V8niB9YLQsA@mail.gmail.com>
Content-Type: multipart/alternative;
	boundary="------------8A44DB2DCD16BA50C40B2789"
Content-Language: fr
X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLY,HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE,URIBL_BLACK autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] BIP 39: Add language identifier strings for
 wordlists
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Jan 2018 16:02:05 -0000

This is a multi-part message in MIME format.
--------------8A44DB2DCD16BA50C40B2789
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

That's the point indeed and the scope is wider than XYZIP-39, even if
what I mean is the very contrary of your point (really bitcoin is
reserved to an elite understanding english/ascii letters?)

This proposal is tailor made for Trezor and does not simplify anything
for people, that's the contrary again

As I suggested in another response to this thread (which was moderated
due probably to some uninteresting parts of the discussion) it's time to
take a break and really make a survey worldwide of what people need,
what they understand and what they need to secure their coins, nobody
has any feedback about this (and maybe does not even care)

Wallets created a big mess implementing non standard things (or things
they thought standard but that are not), or things not intended for the
final use, or things that people can't understand, it's time to correct
this, unless wallets want to keep people tied forever to them (when I
read Trezor or other wallets docs, it's quite misleading, "sending coins
to your wallet", what does it mean? Nothing, and people think it means
something, this should stop now)

And again, I don't see the point of wordlist (in addition in a language
that they don't understand) compared to backing up a 32B hex string
(that you can encrypt different ways at different places), assuming that
the hex format can be made available in all languages

"yet I would not advise users to use a wordlist that might not have
support across multiple wallet implementations, resulting in lock-in or
worse"--> this single sentence shows how the whole model is wrong and
how you think that you can lock people

Le 08/01/2018 à 15:54, Greg Sanders via bitcoin-dev a écrit :
> Let me re-phrase: Is it a known thing for users to actually use it?
>
> On Mon, Jan 8, 2018 at 9:52 AM, Matias Alejo Garcia <ematiu@gmail.com
> <mailto:ematiu@gmail.com>> wrote:
>
>
>
>     On Mon, Jan 8, 2018 at 11:34 AM, Greg Sanders via bitcoin-dev
>     <bitcoin-dev@lists.linuxfoundation.org
>     <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>
>         Has anyone actually used the multilingual support in bip39?
>
>
>
>     Copay (and all its clones) use it. 
>
>
>
>      
>
>
>         If a feature of the standard has not been(widely?) used in
>         years, and isn't supported in any major wallet(?), it seems
>         indicative it was a mistake to add it in the first place,
>         since it's a footgun in the making for some poor sap who can't
>         even read English letters when almost all documentation is
>         written in English.
>
>         On Mon, Jan 8, 2018 at 6:13 AM, nullius via bitcoin-dev
>         <bitcoin-dev@lists.linuxfoundation.org
>         <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>
>             On 2018-01-08 at 07:35:52 +0000, 木ノ下じょな
>             <kinoshitajona@gmail.com <mailto:kinoshitajona@gmail.com>>
>             wrote:
>
>                 This is very sad.
>
>                 The number one problem in Japan with BIP39 seeds is
>                 with English words.
>
>                 I have seen a 60 year old Japanese man writing down
>                 his phrase (because he kept on failing recovery), and
>                 watched him write down "aneter" for "amateur"...
>
>                 [...]
>
>                 If you understand English and can spell, you read a
>                 word, your brain processes the word, and you can spell
>                 it on your own when writing down.  Not many Japanese
>                 people can do that, so they need to copy letter for
>                 letter, taking a long time, and still messing up on
>                 occasion.
>
>                 [...]
>
>                 Defining "everyone should only use English, because
>                 ASCII is easier to plan for" is not a good way to move
>                 forward as a currency.
>
>
>             Well said.  Thank you for telling of these experiences. 
>             Now please, let’s put the shoe on the other foot.
>
>             I ask everybody who wants an English-only mnemonic
>             standard to entrust *their own money* to their abilities
>             to very, very carefully write this down—then later, type
>             it back in:
>
>             すさん たんろ りゆう しもん ていおん しとう
>             とこや はやい おうさま ほくろ けちゃっふ たもつ
>
>             (Approximate translation:  “Whatever would you do if
>             Bitcoin had been invented by somebody named Satoshi
>             Nakamoto?”)
>
>             No, wait:  That is only a 12-word mnemonic.  We are
>             probably talking about a Trezor; so now, hey you there,
>             stake the backup of your life’s savings on your ability to
>             handwrite *this*:
>
>             にあう しひょう にんすう ひえる かいこう いのる ねんし はあさん ひこく
>             とうく きもためし そなた こなこな にさんかたんそ ろんき めいあん みわく
>             へこむ すひょう おやゆひ ふせく けさき めいきょく こんまけ
>
>             Ready to bet your money on *that* as a backup phrase in
>             your own hands?  No?  Then please, stop demanding that
>             others risk *their* money on the inverse case.
>
>             ----
>
>             If you cheat here by having studied Japanese, then
>             remember that many Japanese people know English and other
>             European languages, too.  Then think of how much money
>             would be lost by your non-Japanese-literate family and
>             friends—if BIP 39 had only Japanese wordlists, and your
>             folks needed to wrestle with the above phrases as their
>             “mnemonics”.
>
>             In such cases, the phrases cannot be called “mnemonics” at
>             all.  A “mnemonic” implies aid to memory.  Gibberish in a
>             wholly alien writing system is much worse even than
>             transcribing pseudorandom hex strings.  The Japanese man
>             in the quoted story, who wrote “aneter” for “amateur”, was
>             not dealing with a *mnemonic*:  He was using the world’s
>             most inefficient means of making cryptic bitstrings *less*
>             userfriendly.
>
>             ----
>
>             I began this thread with a quite simple request:  Is “日本語”
>             an appropriate string for identifying the Japanese
>             language to Japanese users?  And what of the other strings
>             I posted for other languages?
>
>             I asked this as an implementer working on my own instance
>             of the greatest guard against vendor lock-in and stale
>             software:  Independent implementations.  —  I asked,
>             because obviously, I myself do not speak all these
>             different languages; and I want to implement them all.  *All.*
>
>             Some replies have been interesting in their own right; but
>             thus far, nobody has squarely addressed the substance of
>             my question.
>
>             Most worrisome is that much of the discussion has veered
>             into criticism of multi-language support.  I opened with a
>             question about other languages, and I am getting replies
>             which raise a hue and cry of “English only!”
>
>             Though I am fluent and literate in English, I am
>             uninterested in ever implementing any standard of this
>             nature which is artificially restricted to English.  I am
>             fortunate; for as of this moment, we have a standard
>             called “BIP 39” which has seven non-English wordlists, and
>             four more pending in open pull requests (#432, #442, #493,
>             #621).
>
>             I request discussion of language identification strings
>             appropriate for use with that standard.
>
>             (P.S., I hope that my system did not mangle anything in
>             the foregoing.  I have seen weird copypaste behaviour mess
>             up decomposed characters.  I thought of this after I
>             searched for and collected some visually fascinating
>             phrases; so I tried to normalize these to NFC...  It
>             should go without saying, easyseed output the Japanese
>             perfectly!)
>
>
>             -- 
>             nullius@nym.zone | PGP ECC:
>             0xC2E91CD74A4C57A105F6C21B5A00591B2F307E0C
>             Bitcoin: bc1qcash96s5jqppzsp8hy8swkggf7f6agex98an7h |
>             (Segwit nested:
>             3NULL3ZCUXr7RDLxXeLPDMZDZYxuaYkCnG)  (PGP RSA:
>             0x36EBB4AB699A10EE)
>             “‘If you’re not doing anything wrong, you have nothing to
>             hide.’
>             No!  Because I do nothing wrong, I have nothing to show.”
>             — nullius
>
>             _______________________________________________
>             bitcoin-dev mailing list
>             bitcoin-dev@lists.linuxfoundation.org
>             <mailto:bitcoin-dev@lists.linuxfoundation.org>
>             https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>             <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
>
>
>
>         _______________________________________________
>         bitcoin-dev mailing list
>         bitcoin-dev@lists.linuxfoundation.org
>         <mailto:bitcoin-dev@lists.linuxfoundation.org>
>         https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>         <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>
>
>
>
>
>     -- 
>     Matías Alejo Garcia
>     @ematiu
>     Roads? Where we're going, we don't need roads!
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

-- 
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms


--------------8A44DB2DCD16BA50C40B2789
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>That's the point indeed and the scope is wider than XYZIP-39,
      even if what I mean is the very contrary of your point (really
      bitcoin is reserved to an elite understanding english/ascii
      letters?)<br>
    </p>
    <p>This proposal is tailor made for Trezor and does not simplify
      anything for people, that's the contrary again<br>
    </p>
    <p>As I suggested in another response to this thread (which was
      moderated due probably to some uninteresting parts of the
      discussion) it's time to take a break and really make a survey
      worldwide of what people need, what they understand and what they
      need to secure their coins, nobody has any feedback about this
      (and maybe does not even care)<br>
    </p>
    <p>Wallets created a big mess implementing non standard things (or
      things they thought standard but that are not), or things not
      intended for the final use, or things that people can't
      understand, it's time to correct this, unless wallets want to keep
      people tied forever to them (when I read Trezor or other wallets
      docs, it's quite misleading, "sending coins to your wallet", what
      does it mean? Nothing, and people think it means something, this
      should stop now)</p>
    <p>And again, I don't see the point of wordlist (in addition in a
      language that they don't understand) compared to backing up a 32B
      hex string (that you can encrypt different ways at different
      places), assuming that the hex format can be made available in all
      languages</p>
    <p>"yet I would not advise users to use a wordlist that might not
      have support across multiple wallet implementations, resulting in
      lock-in or worse"--&gt; this single sentence shows how the whole
      model is wrong and how you think that you can lock people<span
        style="font-size:12.8px"></span></p>
    <div class="moz-cite-prefix">Le 08/01/2018 à 15:54, Greg Sanders via
      bitcoin-dev a écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAB3F3DsifkaCVE1xFvvn8+b-ixpq-NqmGd1vAS8V8niB9YLQsA@mail.gmail.com">
      <div dir="ltr">Let me re-phrase: Is it a known thing for users to
        actually use it?</div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Jan 8, 2018 at 9:52 AM, Matias
          Alejo Garcia <span dir="ltr">&lt;<a
              href="mailto:ematiu@gmail.com" target="_blank"
              moz-do-not-send="true">ematiu@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr"><br>
              <div class="gmail_extra"><br>
                <div class="gmail_quote"><span class="">On Mon, Jan 8,
                    2018 at 11:34 AM, Greg Sanders via bitcoin-dev <span
                      dir="ltr">&lt;<a
                        href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                        target="_blank" moz-do-not-send="true">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>&gt;</span>
                    wrote:<br>
                  </span><span class="">
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex">
                      <div dir="ltr">
                        <div>Has anyone actually used the multilingual
                          support in bip39?<br>
                        </div>
                      </div>
                    </blockquote>
                    <div><br>
                    </div>
                    <div><br>
                    </div>
                  </span>
                  <div>Copay (and all its clones) use it. </div>
                  <div>
                    <div class="h5">
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div> </div>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">
                        <div dir="ltr">
                          <div><br>
                          </div>
                          <div>If a feature of the standard has not
                            been(widely?) used in years, and isn't
                            supported in any major wallet(?), it seems
                            indicative it was a mistake to add it in the
                            first place, since it's a footgun in the
                            making for some poor sap who can't even read
                            English letters when almost all
                            documentation is written in English.</div>
                        </div>
                        <div class="gmail_extra"><br>
                          <div class="gmail_quote">
                            <div>
                              <div class="m_7015119369442535395h5">On
                                Mon, Jan 8, 2018 at 6:13 AM, nullius via
                                bitcoin-dev <span dir="ltr">&lt;<a
                                    href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                                    target="_blank"
                                    moz-do-not-send="true">bitcoin-dev@lists.linuxfounda<wbr>tion.org</a>&gt;</span>
                                wrote:<br>
                              </div>
                            </div>
                            <blockquote class="gmail_quote"
                              style="margin:0 0 0 .8ex;border-left:1px
                              #ccc solid;padding-left:1ex">
                              <div>
                                <div class="m_7015119369442535395h5"><span>On
                                    2018-01-08 at 07:35:52 +0000, 木ノ下じょな
                                    &lt;<a
                                      href="mailto:kinoshitajona@gmail.com"
                                      target="_blank"
                                      moz-do-not-send="true">kinoshitajona@gmail.com</a>&gt;
                                    wrote:<br>
                                  </span>
                                  <blockquote class="gmail_quote"
                                    style="margin:0 0 0
                                    .8ex;border-left:1px #ccc
                                    solid;padding-left:1ex"><span>
                                      This is very sad.<br>
                                      <br>
                                      The number one problem in Japan
                                      with BIP39 seeds is with English
                                      words.<br>
                                      <br>
                                      I have seen a 60 year old Japanese
                                      man writing down his phrase
                                      (because he kept on failing
                                      recovery), and watched him write
                                      down "aneter" for "amateur"...<br>
                                      <br>
                                    </span>
                                    [...]<span><br>
                                      <br>
                                      If you understand English and can
                                      spell, you read a word, your brain
                                      processes the word, and you can
                                      spell it on your own when writing
                                      down.  Not many Japanese people
                                      can do that, so they need to copy
                                      letter for letter, taking a long
                                      time, and still messing up on
                                      occasion.<br>
                                      <br>
                                    </span>
                                    [...]<span><br>
                                      <br>
                                      Defining "everyone should only use
                                      English, because ASCII is easier
                                      to plan for" is not a good way to
                                      move forward as a currency.<br>
                                    </span></blockquote>
                                  <br>
                                  Well said.  Thank you for telling of
                                  these experiences.  Now please, let’s
                                  put the shoe on the other foot.<br>
                                  <br>
                                  I ask everybody who wants an
                                  English-only mnemonic standard to
                                  entrust *their own money* to their
                                  abilities to very, very carefully
                                  write this down—then later, type it
                                  back in:<br>
                                  <br>
                                  すさん たんろ りゆう しもん ていおん しとう<br>
                                  とこや はやい おうさま ほくろ けちゃっふ たもつ<br>
                                  <br>
                                  (Approximate translation:  “Whatever
                                  would you do if Bitcoin had been
                                  invented by somebody named Satoshi
                                  Nakamoto?”)<br>
                                  <br>
                                  No, wait:  That is only a 12-word
                                  mnemonic.  We are probably talking
                                  about a Trezor; so now, hey you there,
                                  stake the backup of your life’s
                                  savings on your ability to handwrite
                                  *this*:<br>
                                  <br>
にあう しひょう にんすう ひえる かいこう いのる ねんし はあさん ひこく<br>
とうく きもためし そなた こなこな にさんかたんそ ろんき めいあん みわく<br>
                                  へこむ すひょう おやゆひ ふせく けさき めいきょく こんまけ<br>
                                  <br>
                                  Ready to bet your money on *that* as a
                                  backup phrase in your own hands?  No? 
                                  Then please, stop demanding that
                                  others risk *their* money on the
                                  inverse case.<br>
                                  <br>
                                  ----<br>
                                  <br>
                                  If you cheat here by having studied
                                  Japanese, then remember that many
                                  Japanese people know English and other
                                  European languages, too.  Then think
                                  of how much money would be lost by
                                  your non-Japanese-literate family and
                                  friends—if BIP 39 had only Japanese
                                  wordlists, and your folks needed to
                                  wrestle with the above phrases as
                                  their “mnemonics”.<br>
                                  <br>
                                  In such cases, the phrases cannot be
                                  called “mnemonics” at all.  A
                                  “mnemonic” implies aid to memory. 
                                  Gibberish in a wholly alien writing
                                  system is much worse even than
                                  transcribing pseudorandom hex
                                  strings.  The Japanese man in the
                                  quoted story, who wrote “aneter” for
                                  “amateur”, was not dealing with a
                                  *mnemonic*:  He was using the world’s
                                  most inefficient means of making
                                  cryptic bitstrings *less*
                                  userfriendly.<br>
                                  <br>
                                  ----<br>
                                  <br>
                                  I began this thread with a quite
                                  simple request:  Is “日本語” an
                                  appropriate string for identifying the
                                  Japanese language to Japanese users? 
                                  And what of the other strings I posted
                                  for other languages?<br>
                                  <br>
                                  I asked this as an implementer working
                                  on my own instance of the greatest
                                  guard against vendor lock-in and stale
                                  software:  Independent
                                  implementations.  —  I asked, because
                                  obviously, I myself do not speak all
                                  these different languages; and I want
                                  to implement them all.  *All.*<br>
                                  <br>
                                  Some replies have been interesting in
                                  their own right; but thus far, nobody
                                  has squarely addressed the substance
                                  of my question.<br>
                                  <br>
                                  Most worrisome is that much of the
                                  discussion has veered into criticism
                                  of multi-language support.  I opened
                                  with a question about other languages,
                                  and I am getting replies which raise a
                                  hue and cry of “English only!”<br>
                                  <br>
                                  Though I am fluent and literate in
                                  English, I am uninterested in ever
                                  implementing any standard of this
                                  nature which is artificially
                                  restricted to English.  I am
                                  fortunate; for as of this moment, we
                                  have a standard called “BIP 39” which
                                  has seven non-English wordlists, and
                                  four more pending in open pull
                                  requests (#432, #442, #493, #621).<br>
                                  <br>
                                  I request discussion of language
                                  identification strings appropriate for
                                  use with that standard.<br>
                                  <br>
                                  (P.S., I hope that my system did not
                                  mangle anything in the foregoing.  I
                                  have seen weird copypaste behaviour
                                  mess up decomposed characters.  I
                                  thought of this after I searched for
                                  and collected some visually
                                  fascinating phrases; so I tried to
                                  normalize these to NFC...  It should
                                  go without saying, easyseed output the
                                  Japanese perfectly!)
                                  <div
                                    class="m_7015119369442535395m_-6034384190307218273HOEnZb">
                                    <div
                                      class="m_7015119369442535395m_-6034384190307218273h5"><br>
                                      <br>
                                      -- <br>
                                      <a class="moz-txt-link-abbreviated" href="mailto:nullius@nym.zone">nullius@nym.zone</a> | PGP ECC:
                                      0xC2E91CD74A4C57A105F6C21B5A00<wbr>591B2F307E0C<br>
                                      Bitcoin:
                                      bc1qcash96s5jqppzsp8hy8swkggf7<wbr>f6agex98an7h
                                      | (Segwit nested:<br>
                                      3NULL3ZCUXr7RDLxXeLPDMZDZYxuaY<wbr>kCnG) 
                                      (PGP RSA: 0x36EBB4AB699A10EE)<br>
                                      “‘If you’re not doing anything
                                      wrong, you have nothing to hide.’<br>
                                      No!  Because I do nothing wrong, I
                                      have nothing to show.” — nullius<br>
                                    </div>
                                  </div>
                                  <br>
                                </div>
                              </div>
                              <span>______________________________<wbr>_________________<br>
                                bitcoin-dev mailing list<br>
                                <a
                                  href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                                  target="_blank" moz-do-not-send="true">bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
                                <a
                                  href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"
                                  rel="noreferrer" target="_blank"
                                  moz-do-not-send="true">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
                                <br>
                              </span></blockquote>
                          </div>
                          <br>
                        </div>
                        <br>
                        ______________________________<wbr>_________________<br>
                        bitcoin-dev mailing list<br>
                        <a
                          href="mailto:bitcoin-dev@lists.linuxfoundation.org"
                          target="_blank" moz-do-not-send="true">bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
                        <a
                          href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"
                          rel="noreferrer" target="_blank"
                          moz-do-not-send="true">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
                        <br>
                      </blockquote>
                    </div>
                  </div>
                </div>
                <span class="HOEnZb"><font color="#888888"><br>
                    <br clear="all">
                    <div><br>
                    </div>
                    -- <br>
                    <div class="m_7015119369442535395gmail_signature"
                      data-smartmail="gmail_signature">
                      <div dir="ltr">Matías Alejo Garcia<br>
                        @ematiu<br>
                        Roads? Where we're going, we don't need roads!</div>
                    </div>
                  </font></span></div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Bitcoin transactions made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-transactions">https://github.com/Ayms/bitcoin-transactions</a>
Zcash wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/zcash-wallets">https://github.com/Ayms/zcash-wallets</a>
Bitcoin wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-wallets">https://github.com/Ayms/bitcoin-wallets</a>
Get the torrent dynamic blocklist: <a class="moz-txt-link-freetext" href="http://peersm.com/getblocklist">http://peersm.com/getblocklist</a>
Check the 10 M passwords list: <a class="moz-txt-link-freetext" href="http://peersm.com/findmyass">http://peersm.com/findmyass</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.org">http://torrent-live.org</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a></pre>
  </body>
</html>

--------------8A44DB2DCD16BA50C40B2789--