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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <marek@palatinus.cz>) id 1VaAmQ-0007ds-Dd
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Oct 2013 20:48:18 +0000
X-ACL-Warn:
Received: from mail-vb0-f47.google.com ([209.85.212.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VaAmP-0007tF-1N
for bitcoin-development@lists.sourceforge.net;
Sat, 26 Oct 2013 20:48:18 +0000
Received: by mail-vb0-f47.google.com with SMTP id m10so3556498vbh.34
for <bitcoin-development@lists.sourceforge.net>;
Sat, 26 Oct 2013 13:48:11 -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:to:cc:content-type;
bh=gFDChL4iTVPGeREo70PVOpO4RugL1Q1AGZOWETv35xY=;
b=kknWcaZ+5y+z1i1l0w+6J3uCXOl9HgnFqR4d1r00IR/XmUExHMXLFWmjY3Oq55xJT5
6oE7oeRiVMKYzAioPUvaewA7iBU9t/8nZMCvLrEjeK3IoTpjxHmlfQtYd4BhrGZfjqCl
iIsUeL9jcV+98s7146ZBR1CDPrlxNU1kUgdXLfMAw+y876mD4Yx0+uBHnSj8J4ONqq2U
RL8lWQGzZQDC9caVa4W38EWkbudir/2Dl2xs4OeMWmsyaCEs18GpLqfHDwwHakNBNthY
BhUHHq3QbGAzimuKMybDcq/2zxJ++sVu2O54TVfhUHGN8J6jm1d30d1LDRLh/LqpdUez
bilA==
X-Gm-Message-State: ALoCoQlWrFZ8L+E19aKGI65dMJdPKMFAf9bEOZXSQbEu5R8pn5djrVRtE3Q59zl7U/sXYi32CyJH
X-Received: by 10.58.19.195 with SMTP id h3mr3085vee.48.1382820491343; Sat, 26
Oct 2013 13:48:11 -0700 (PDT)
MIME-Version: 1.0
Sender: marek@palatinus.cz
Received: by 10.59.1.2 with HTTP; Sat, 26 Oct 2013 13:47:41 -0700 (PDT)
In-Reply-To: <526BDEC2.2090709@gmx.de>
References: <trinity-ba3941a0-f758-4372-b431-c64e9b44328a-1382635758149@3capp-gmx-bs09>
<CAJna-HjgpRhLdVGh+prx54VezHaH1vXGpPotW1Xkz2tiAiWrbg@mail.gmail.com>
<526BDEC2.2090709@gmx.de>
From: slush <slush@centrum.cz>
Date: Sat, 26 Oct 2013 22:47:41 +0200
X-Google-Sender-Auth: Bo9GtXjn7xYqE_aBntuKGMreVy4
Message-ID: <CAJna-HgH1g8iiSvxXrJuga808SQJ6DKo4AYw4fxpwTRCsL+EyQ@mail.gmail.com>
To: Thomas Voegtlin <thomasv1@gmx.de>
Content-Type: multipart/alternative; boundary=047d7b86c81e2cecf404e9aafc04
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 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: doubleclick.net]
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: 1VaAmP-0007tF-1N
Cc: "bitcoin-development@lists.sourceforge.net"
<bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal to replace BIP0039
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: Sat, 26 Oct 2013 20:48:18 -0000
--047d7b86c81e2cecf404e9aafc04
Content-Type: text/plain; charset=ISO-8859-1
Hi Thomas,
can you more elaborate on that "version" bits? What is exact meaning of it?
I still think this is more an implementation problem. What stops Electrum
to do the same algorithm for searching branches as it is now for used
addresses?
These "version bits" need to be covered by the specification as well,
because if any client will use them differently (or won't use them at all),
it will break cross-compatibility between clients, which was another goal
of bip39.
Marek
On Sat, Oct 26, 2013 at 5:24 PM, Thomas Voegtlin <thomasv1@gmx.de> wrote:
> here is a simple implementation, with some ideas on how to format the
> metadata:
> https://en.bitcoin.it/wiki/Talk:BIP_0039
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7b86c81e2cecf404e9aafc04
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hi Thomas,<div><br></div><div>can you more elaborate on th=
at "version" bits? What is exact meaning of it? I still think thi=
s is more an implementation problem. What stops Electrum to do the same alg=
orithm for searching branches as it is now for used addresses?</div>
<div><br></div><div style>These "version bits" need to be covered=
by the specification as well, because if any client will use them differen=
tly (or won't use them at all), it will break cross-compatibility betwe=
en clients, which was another goal of bip39.</div>
<div style><br></div><div style>Marek</div><div><br></div><div><br></div></=
div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sat, O=
ct 26, 2013 at 5:24 PM, Thomas Voegtlin <span dir=3D"ltr"><<a href=3D"ma=
ilto:thomasv1@gmx.de" target=3D"_blank">thomasv1@gmx.de</a>></span> wrot=
e:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">here is a simple implementation, with some i=
deas on how to format the<br>
metadata:<br>
<a href=3D"https://en.bitcoin.it/wiki/Talk:BIP_0039" target=3D"_blank">http=
s://en.bitcoin.it/wiki/Talk:BIP_0039</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
---------------------------------------------------------------------------=
---<br>
October Webinars: Code for Performance<br>
Free Intel webinars can help you accelerate application performance.<br>
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr=
om<br>
the latest Intel processors and coprocessors. See abstracts and register &g=
t;<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60135991&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D60135991&iu=3D/4140/ostg.clktrk</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div>
--047d7b86c81e2cecf404e9aafc04--
|
