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; 
MIME-Version: 1.0
Sender: g.rowe.froot@gmail.com
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
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
Subject: Re: [Bitcoin-development] Multisign payment protocol?
Precedence: list

--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 &quot;M=
ultiBit Classic&quot; 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&#39;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">&lt;<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blan=
k">jgarzik@bitpay.com</a>&gt;</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 &lt;rant.h&gt;)<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&#39;Reilly Book<br>
&quot;Graph Databases&quot; 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--