Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.176 as permitted sender)
	client-ip=209.85.214.176; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f176.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <53436977.4030808@jerviss.org>
References: <CANEZrP2rgiQHpekEpFviJ22QsiV+s-F2pqosaZOA5WrRtJx5pg@mail.gmail.com>
	<CALC81CMc7BridL7600b7bij3dJHzeQWgTv=iqVeW--n-we+1Yw@mail.gmail.com>
	<lhua2p$lp5$1@ger.gmane.org>
	<CANEZrP3F+UQ1amVAK4a9_UCsXia7Yfv0RO4pWK7NTde0GvH-0A@mail.gmail.com>
	<CAAf19Wrz0u_e5V9Gb=_CAG=mHtE9nA_VETgYZeCXZqwaGeYKuQ@mail.gmail.com>
	<53436977.4030808@jerviss.org>
Date: Tue, 8 Apr 2014 09:50:31 +0200
Message-ID: <CANEZrP2-h80jP2U2ONWEhpjkBP-X8=sjburRq80U40eJsQi-VQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: kjj <bitcoin-devel@jerviss.org>
Content-Type: multipart/alternative; boundary=001a11c309da02074404f6833dfc
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
Precedence: list

--001a11c309da02074404f6833dfc
Content-Type: text/plain; charset=UTF-8

>
> Multi-sig requires infrastructure.  It isn't a magic wand that we can
> wave to make everyone secure.  The protocols and techniques necessary
> don't exist yet, and apparently no one has much of an incentive to
> create them.


It is starting to happen. If you're OK with using a specific web wallet
there's BitGo and greenaddress.it already, though I think their risk
analysis is just sending you an SMS code. I wrote up an integration plan
for bitcoinj a few days ago:

 https://groups.google.com/forum/#!topic/bitcoinj/Uxl-z40OLuQ

but guess what? It's quite complicated. As with all these features.

--001a11c309da02074404f6833dfc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">
Multi-sig requires infrastructure. =C2=A0It isn&#39;t a magic wand that we =
can<br>
wave to make everyone secure. =C2=A0The protocols and techniques necessary<=
br>
don&#39;t exist yet, and apparently no one has much of an incentive to<br>
create them.</blockquote><div><br></div><div>It is starting to happen. If y=
ou&#39;re OK with using a specific web wallet there&#39;s BitGo and <a href=
=3D"http://greenaddress.it">greenaddress.it</a> already, though I think the=
ir risk analysis is just sending you an SMS code. I wrote up an integration=
 plan for bitcoinj a few days ago:</div>
<div><br></div><div>=C2=A0<a href=3D"https://groups.google.com/forum/#!topi=
c/bitcoinj/Uxl-z40OLuQ">https://groups.google.com/forum/#!topic/bitcoinj/Ux=
l-z40OLuQ</a></div><div><br></div><div>but guess what? It&#39;s quite compl=
icated. As with all these features.</div>
</div></div></div>

--001a11c309da02074404f6833dfc--