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
|
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 <g.rowe.froot@gmail.com>) id 1WNO3v-0004ex-Ae
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:53:47 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.128.169 as permitted sender)
client-ip=209.85.128.169; envelope-from=g.rowe.froot@gmail.com;
helo=mail-ve0-f169.google.com;
Received: from mail-ve0-f169.google.com ([209.85.128.169])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNO3s-0004hf-Qg
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:53:47 +0000
Received: by mail-ve0-f169.google.com with SMTP id pa12so9024509veb.28
for <bitcoin-development@lists.sourceforge.net>;
Tue, 11 Mar 2014 07:53:39 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.52.27.9 with SMTP id p9mr7371379vdg.28.1394549619300; Tue,
11 Mar 2014 07:53:39 -0700 (PDT)
Sender: g.rowe.froot@gmail.com
Received: by 10.220.251.65 with HTTP; Tue, 11 Mar 2014 07:53:39 -0700 (PDT)
In-Reply-To: <CAJHLa0NHKWqXMd23Fr46adGinQmjcLRxyBB-Ra9tJwu4Ein7GA@mail.gmail.com>
References: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
<CABsx9T0SMi6Gp4JY=CpHxLEu5pVkvDmnug7PsY7m_dvtT7khzg@mail.gmail.com>
<531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org>
<531E5454.1030601@gmail.com>
<CAJHLa0NZkzQQvMxgCJAJGT=Yn6vrVNK8Bg7RAfAjctpnrfg5zA@mail.gmail.com>
<CABsx9T3eViYDsEmLm7ceimJNwci3mCOxWoVnVZHrqp7pDmm0+g@mail.gmail.com>
<CANAnSg2kzPF0886PsQW8chzsWi6Urp+=-x+9bbv8Mv6hmpvBPw@mail.gmail.com>
<CAJHLa0Mu2kiv3CCme7BPwzWtT++PNLQ2aAKdLyA8LFTtXEg9fg@mail.gmail.com>
<CABsx9T0Lvg84qFVRbc7Ef4vZEQj9eO7Jhup5PTRLLeuJFvXi-w@mail.gmail.com>
<CAJHLa0Mn2_OKDH_XUXfz49hPWGdCN0gs6S3wbtc=qHkg+sJ2Xw@mail.gmail.com>
<CABsx9T3fKBCFd7d-yP-0WgN2TBwN8Es=hZqxPBnThESKz1jLvA@mail.gmail.com>
<CAJHLa0NHKWqXMd23Fr46adGinQmjcLRxyBB-Ra9tJwu4Ein7GA@mail.gmail.com>
Date: Tue, 11 Mar 2014 14:53:39 +0000
X-Google-Sender-Auth: lFHqLJXYBbNXwQapGZyzHo8gQS4
Message-ID: <CAKm8k+3Eohr9OtA+tSp9nXuQpxfiAwC6R61zZWSB3WMAxCZ=Vw@mail.gmail.com>
From: Gary Rowe <g.rowe@froot.co.uk>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=20cf307d0104ae22d004f455e260
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(g.rowe.froot[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WNO3s-0004hf-Qg
Subject: Re: [Bitcoin-development] Multisign payment protocol?
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: Tue, 11 Mar 2014 14:53:47 -0000
--20cf307d0104ae22d004f455e260
Content-Type: text/plain; charset=UTF-8
Speaking from the MultiBit perspective, all future protocol development
(with the exception of critical security and network compatibility fixes)
will be put into a HD wallet. Over time we want to see "MultiBit Classic"
gracefully retire and be fully superseded.
Right now, HD is not out there but there is a lot of work going on between
wallet developers to harmonise on HD implementation through BIP32/39. The
result of that work should see a significant migration away from random
private keys.
Thus it would appear likely that by the time this protocol sees widespread
use the presence of HD is likely to be rising fast or possibly dominant.
At MultiBit we anticipate a release of HD code within 2 months, with
private beta occurring within weeks. Trezor and Electrum may be earlier
than this. As far as I am aware both Hive and Haskoin are committed to HD.
If anyone wants early access to the alpha code, let me know and I'll make
the arrangements.
On 11 March 2014 14:44, Jeff Garzik <jgarzik@bitpay.com> wrote:
> (#include <rant.h>)
>
> Right now, HD is hot air. Let us end the pie-in-the-sky assumptions
> about how HD will save the day, with zero code to back it up. Bitcoin
> Wallet purportedly fails to rotate addresses, a privacy ugly, because
> of this Waiting For Godot situation. An attempt to add a simple,
> stateless RPC stalled because we are all Waiting For Godot, also:
> https://github.com/bitcoin/bitcoin/pull/3520
>
> Until the major user wallets and bitcoind have -basic- HD support, it
> is premature to build anything on top of HD. We really have no clue
> at this juncture how difficult will be the HD rollout.
>
> --
> Jeff Garzik
> Bitcoin core developer and open source evangelist
> BitPay, Inc. https://bitpay.com/
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--20cf307d0104ae22d004f455e260
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Speaking from the MultiBit perspective, all future protoco=
l development (with the exception of critical security and network compatib=
ility fixes) will be put into a HD wallet. Over time we want to see "M=
ultiBit Classic" gracefully retire and be fully superseded.<div>
<br></div><div>Right now, HD is not out there but there is a lot of work go=
ing on between wallet developers to harmonise on HD implementation through =
BIP32/39. The result of that work should see a significant migration away f=
rom random private keys.=C2=A0</div>
<div><br></div><div><div>Thus it would appear likely that by the time this =
protocol sees widespread use the presence of HD is likely to be rising fast=
or possibly dominant.=C2=A0</div></div><div><br></div><div>At MultiBit we =
anticipate a release of HD code within 2 months, with private beta occurrin=
g within weeks. Trezor and Electrum may be earlier than this. As far as I a=
m aware both Hive and Haskoin are committed to HD.</div>
<div><br></div><div>If anyone wants early access to the alpha code, let me =
know and I'll make the arrangements.</div></div><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote">On 11 March 2014 14:44, Jeff Garzik =
<span dir=3D"ltr"><<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blan=
k">jgarzik@bitpay.com</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">(#include <rant.h>)<br>
<br>
Right now, HD is hot air. =C2=A0Let us end the pie-in-the-sky assumptions<b=
r>
about how HD will save the day, with zero code to back it up. =C2=A0Bitcoin=
<br>
Wallet purportedly fails to rotate addresses, a privacy ugly, because<br>
of this Waiting For Godot situation. =C2=A0An attempt to add a simple,<br>
stateless RPC stalled because we are all Waiting For Godot, also:<br>
<a href=3D"https://github.com/bitcoin/bitcoin/pull/3520" target=3D"_blank">=
https://github.com/bitcoin/bitcoin/pull/3520</a><br>
<br>
Until the major user wallets and bitcoind have -basic- HD support, it<br>
is premature to build anything on top of HD. =C2=A0We really have no clue<b=
r>
at this juncture how difficult will be the HD rollout.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
--<br>
Jeff Garzik<br>
Bitcoin core developer and open source evangelist<br>
BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"=
_blank">https://bitpay.com/</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Learn Graph Databases - Download FREE O'Reilly Book<br>
"Graph Databases" is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</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>
--20cf307d0104ae22d004f455e260--
|
