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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1W5Mht-0007OH-Gt
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Jan 2014 21:48:33 +0000
X-ACL-Warn:
Received: from mail-vb0-f50.google.com ([209.85.212.50])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W5Mhs-0000n6-GP
for bitcoin-development@lists.sourceforge.net;
Mon, 20 Jan 2014 21:48:33 +0000
Received: by mail-vb0-f50.google.com with SMTP id w8so3180090vbj.9
for <bitcoin-development@lists.sourceforge.net>;
Mon, 20 Jan 2014 13:48:27 -0800 (PST)
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:to:cc:content-type;
bh=zIcBU2SFX+YBJ3Dvu6Cy5vYmdFjFVyAf1gih5wAgRKc=;
b=mzu7Drrg1p07TGNxTl1A4JxxAqSwKFZQS0u/Jznxnz/QU/V1Js0/LP3qZAVNFlWvpX
ZAJB7XZ8GnoABxRTFZnReUhFe+U2bwyKvXg3HT0RESS3BId0ONyfLdD6V2pP01yGuwtJ
6RPgzJq1pa0vr0t/MUUthwECNjBnjlx2dcRkNRykt1uELH9vB4WdmjnzJBI3ntAohJq7
bET9hKNw+VRgLlx8GLJwtXLGZiooIoCH/mQLE9u2xyFgEV9OgJC/Cpb7zdhInnd7z9nc
XRTmJJ7J42R1fJ7K1cmn7cOnPLkVCyBpTDOK5wlVJhAU4uOkdhh+dcWrZJ6CgxDC93SJ
SoGw==
X-Gm-Message-State: ALoCoQmRCdciwZ35KrxU/KnGpWqvEdLZ6wuVm4tjHRLbmU9+O4EwiLO6VXLjgD08AkZ6Mi836eCZ
X-Received: by 10.52.237.228 with SMTP id vf4mr9943845vdc.3.1390254507014;
Mon, 20 Jan 2014 13:48:27 -0800 (PST)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.58.57.234 with HTTP; Mon, 20 Jan 2014 13:47:56 -0800 (PST)
In-Reply-To: <201401202002.28141.luke@dashjr.org>
References: <CAJna-HjGHpru6Lpv_tXUkWR2mX-=fobzojtHYvSRJy6+CMesOA@mail.gmail.com>
<201401202002.28141.luke@dashjr.org>
From: slush <slush@centrum.cz>
Date: Mon, 20 Jan 2014 22:47:56 +0100
X-Google-Sender-Auth: v1eT-2YVQAW9tiyH0xVE5cTqMzw
Message-ID: <CAJna-HhgiYe-GRUBdJfchZ2tVLDBnn_6WtNrefrbtYJsG05GXQ@mail.gmail.com>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=089e0122f6aa09d4d804f06ddac0
X-Spam-Score: 1.0 (+)
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.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1W5Mhs-0000n6-GP
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
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 21:48:33 -0000
--089e0122f6aa09d4d804f06ddac0
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Jan 20, 2014 at 9:02 PM, Luke-Jr <luke@dashjr.org> wrote:
>
> How are they compatible if they could be using entirely different word
> lists??
>
>
Wordlist is necessary for the step [seed]->[mnemonic]. Step
[mnemonic]->[bip32 root] doesn't need any wordlist, there's just hashing
involved.
For this reason client can generate whatever mnemonic and unless all
clients use the same process [mnemonic]->[bip32 root], the result is the
same.
> Maybe I'm missing something, but shouldn't this be a client-side thing, not
> implemented in the Trezor firmware at all?? O.o;;
>
>
Trezor generates the seed and transforms it to mnemonic (which is then
shown on internal display). Generating the mnemonic outside the client-side
(computer) is one of main functionality of Trezor.
slush
--089e0122f6aa09d4d804f06ddac0
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Jan 20, 2014 at 9:02 PM, Luke-Jr <span dir=3D"ltr"><<a href=3D"m=
ailto:luke@dashjr.org" target=3D"_blank">luke@dashjr.org</a>></span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">
<div class=3D"im"><br>
</div>How are they compatible if they could be using entirely different wor=
d lists??<br>
<div class=3D"im"><br></div></blockquote><div><br></div><div>Wordlist is ne=
cessary for the step [seed]->[mnemonic]. Step [mnemonic]->[bip32 root=
] doesn't need any wordlist, there's just hashing involved.</div>
<div>For this reason client can generate whatever mnemonic and unless all c=
lients use the same process [mnemonic]->[bip32 root], the result is the =
same.</div><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe I'm missing something, but shouldn't this be a client-side th=
ing, not<br>
implemented in the Trezor firmware at all?? O.o;;<br>
<br></blockquote><div><br></div><div>Trezor generates the seed and transfor=
ms it to mnemonic (which is then shown on internal display). Generating the=
mnemonic outside the client-side (computer) is one of main functionality o=
f Trezor.</div>
<div><br></div><div>slush</div></div></div></div>
--089e0122f6aa09d4d804f06ddac0--
|
