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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mark@monetize.io>) id 1W5OBK-0002mq-G8
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Jan 2014 23:23:02 +0000
Received: from mail-yh0-f53.google.com ([209.85.213.53])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W5OBJ-0005mn-7P
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Jan 2014 23:23:02 +0000
Received: by mail-yh0-f53.google.com with SMTP id b20so2275820yha.12
for <bitcoin-development@lists.sourceforge.net>;
Mon, 20 Jan 2014 15:22:55 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:organization:user-agent
:mime-version:to:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=fjp8xqMM7jxiQw0LGjaSNdmyk134Ct/P+wuHYz+EaUM=;
b=A4J+4DE+iiU4Gtocy1OBlzsr3ED1pin9a0dZxXUfVH/PMI5//k0KOSu0qCoFdg54CE
ucl1Hzpjvneuzm7iSEDeVz7z6A79Tn0SRng4EGp6Br0jsw/Rfxn5ioVJPgxPHQy3qmO3
gsMv+YGZCoA8u+NSuvvxZQIbwtBPE40mw2ykiMvdTmZANlNX3eX7SrIlzzpJawPI+3XL
MP1QWdJ/+MKoDVMWXjZ8jjeLw1NmsrF8LLB8PtD7K7TURAPJy1usxqmf0VbUQxzuAjP4
qg13gE6Bw5qUY/6K52TK1bmv+fHe/kaauuHgtRXmQ5US3WayTgpOLbgSbabvxuJfD/HM
w2bg==
X-Gm-Message-State: ALoCoQm8XXvyB4lrTEgfcWV/3MsDYaifsQP8fuEcK+6ufurUJ70gq7ZIKzH+r7zWm5hj88Is2shQ
X-Received: by 10.236.228.137 with SMTP id f9mr20045825yhq.44.1390260175760;
Mon, 20 Jan 2014 15:22:55 -0800 (PST)
Received: from [192.168.127.165] (adsl-71-131-179-82.dsl.sntc01.pacbell.net.
[71.131.179.82])
by mx.google.com with ESMTPSA id 9sm6883713yhe.21.2014.01.20.15.22.54
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 20 Jan 2014 15:22:54 -0800 (PST)
Message-ID: <52DDAECC.9010107@monetize.io>
Date: Mon, 20 Jan 2014 15:18:36 -0800
From: Mark Friedenbach <mark@monetize.io>
Organization: Monetize.io Inc.
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <CAJna-HjGHpru6Lpv_tXUkWR2mX-=fobzojtHYvSRJy6+CMesOA@mail.gmail.com> <CANg-TZCrpT-YJ0WV9VY6w-PtCiz2YRMBCMvmjneDz13j2namkw@mail.gmail.com> <20140120223502.GA1055@petertodd.org>
<20140120231441.GA9332@netbook.cypherspace.org>
In-Reply-To: <20140120231441.GA9332@netbook.cypherspace.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1W5OBJ-0005mn-7P
Subject: Re: [Bitcoin-development] BIP0039: Final call
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: Mon, 20 Jan 2014 23:23:02 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Proper Unicode handling is a serious issue however. You don't want
someone to move from one input method / machine to another and
suddenly find that their coins are inaccessible, because of an issue
of decomposed vs. compatibility forms or whatever.
On 01/20/2014 03:14 PM, Adam Back wrote:
> Because the mnemonic is an encoding of a 128-bit random number
> using its hash as a private key (or derived part of one) is not a
> problem, its just an alternate alphabet encoding of the random
> private key.
>
> Not being able to generically understand the checksum. Seems
> tricky to solve other than say brute force eg H(mnemonic||1) mod
> 2^k == 0 where k is the amount of check digit redundancy. But that
> might be expensive for a trezor if k is very big at all. And then
> key = H(mnemonic).
>
> Adam
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJS3a7MAAoJEAdzVfsmodw4/MAP/3Rk4sbQBv5aGqM2iAMBZkjq
CxGNSrzxKKgAYf+aFka6FVrBZJRHU39mEon53H0DR92+3vA2BHns8YEKH18LneQ9
16qJAp4y+ml5jbdCI6TY1JCM4ObmXsZbsPF17lKdVPISkz8DhUMUNLHdOx8cZHkw
Kj5RXuLBFwqFiCcAqYdoIpFmDpfaJfZ3k9OHzPRsto1oyOrXdwc+TK8YZHISWR3M
nzsMcp2z9Uu8M/NeDo4gM0WFpIZ41W9JsYeMeJzdU6xd1HKdmC0CZCyc8EmAre58
XGc2gtc9PjXIwWW+FTkZ5pYJz718WBq4Wja1hir5eaTJZurs1fp+1iJ7jiDkloJH
h/pWp8wcXVaAklaImota3PASr5qnP8zjzaKZALn/0gJEkIKnIJz3N32BLw7QsoEL
k5VaMQ5x7/9zK+Qc5kWvtTjleRO23DnW+XVud0jbAHTM1wfTQH0dJIgEpe3HQZOR
9a09/ZKN8kC+2fj/u6EjkVh5RvwTv0iq+RvBDmsFjaVOfBzRL1LVKgKJvdG+0hix
XyPtnBflC1uNLNg/yjBEP7/cKePJVMcDzVBwjpbnEOo9ZGO2ixSh8qMQ/nn6V96R
hZZv8mVI1bGhWlvQEoMw5X7M4xyP25GboCv4wJrYT/8VQfe56BSKXS+AHfl+hIoa
Jjmcqvm+sfk/0awxj4Ce
=1crJ
-----END PGP SIGNATURE-----
|
