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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1VYnD3-0004yW-7e
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Oct 2013 01:26:05 +0000
X-ACL-Warn:
Received: from mail-vc0-f170.google.com ([209.85.220.170])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VYnD2-0000sw-2N
for bitcoin-development@lists.sourceforge.net;
Wed, 23 Oct 2013 01:26:05 +0000
Received: by mail-vc0-f170.google.com with SMTP id hv10so70931vcb.1
for <bitcoin-development@lists.sourceforge.net>;
Tue, 22 Oct 2013 18:25:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
:date:message-id:subject:cc:content-type;
bh=2+7VnOqvg58dmrDaf3qwW0LWS4MAeFEvFohDC0Ll2l0=;
b=i/ANminygjnDXyw7JRybL+0ZM7eobpGydPlME+R50uM5UxXB+Dgx/+tRzQltNsPurm
bDFloE5voT4yImSka1IJLWayJ+mBy+7FF6URRmUfUDd0T8Oh1lHEELpJo5MsyuMwtRET
h139udQqgSlro9ICYNXz1oa3JQYDxKkXN9XXXoTQ8DWJWbwqC6vbOH9yOscGwAHUhtQ/
1LxiVDqz34j40ZPsn69LyfE7u8MuSHF2G0NXRfiFnQefCNXSdeljzfo2E0F7+LiVJRXD
iOAaBeDRDf0wEP4JmfXzbFYgRSxkWeWjv6D/PgJfLunYqMGZUPJKRsqcLtUmezqxLad+
5SUg==
X-Gm-Message-State: ALoCoQl5Js2ygwJyI6YnsWtfrXyR10v+OnCOmt1qL2OqO3iYkVtDAwNKPagRZki0cQyA+yx9MbNr
X-Received: by 10.58.161.231 with SMTP id xv7mr16226457veb.2.1382489848033;
Tue, 22 Oct 2013 17:57:28 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.59.1.2 with HTTP; Tue, 22 Oct 2013 17:56:57 -0700 (PDT)
In-Reply-To: <87iowuuof9.fsf@gmail.com>
References: <87iowuuof9.fsf@gmail.com>
From: slush <slush@centrum.cz>
Date: Wed, 23 Oct 2013 02:56:57 +0200
X-Google-Sender-Auth: hxBnr3JQNkos5PaAKxkNIm4Kzc8
Message-ID: <CAJna-Hh_MMfW3W4tKHnAL3xd8Pbvkv6MGfOArFfxGzwcjDis1w@mail.gmail.com>
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7b6774724c4a7104e95e004c
X-Spam-Score: 2.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
(slush[at]centrum.cz)
1.2 MISSING_HEADERS Missing To: header
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1VYnD2-0000sw-2N
Subject: Re: [Bitcoin-development] BIP39 word list
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, 23 Oct 2013 01:26:05 -0000
--047d7b6774724c4a7104e95e004c
Content-Type: text/plain; charset=ISO-8859-1
I think this is a good idea; I just pushed new unit test test_similarity()
to github which finds such similar words. Right now it identifies ~90
similar pairs in current wordlist, I'll update wordlist tomorrow to pass
this test.
slush
On Sat, Oct 19, 2013 at 1:52 AM, jan <jan.marecek@gmail.com> wrote:
>
> I think avoiding words that could look similar when written down would
> be a good idea aswell. I searched for words that only differ by the
> letters c & e, g & y, u & v and found the following:
>
> car ear
> cat eat
> gear year
> value valve
>
> Other combinations could potentially be problematic depending on the
> handwriting style: ft, ao, ij, vy, possibly even lt and il?
>
>
--047d7b6774724c4a7104e95e004c
Content-Type: text/html; charset=ISO-8859-1
<div dir="ltr">I think this is a good idea; I just pushed new unit test test_similarity() to github which finds such similar words. Right now it identifies ~90 similar pairs in current wordlist, I'll update wordlist tomorrow to pass this test.<div>
<br></div><div>slush<div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 19, 2013 at 1:52 AM, jan <span dir="ltr"><<a href="mailto:jan.marecek@gmail.com" target="_blank">jan.marecek@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
I think avoiding words that could look similar when written down would<br>
be a good idea aswell. I searched for words that only differ by the<br>
letters c & e, g & y, u & v and found the following:<br>
<br>
car ear<br>
cat eat<br>
gear year<br>
value valve<br>
<br>
Other combinations could potentially be problematic depending on the<br>
handwriting style: ft, ao, ij, vy, possibly even lt and il?<br>
<br></blockquote></div></div></div></div>
--047d7b6774724c4a7104e95e004c--
|
