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
|
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 <mh.in.england@gmail.com>) id 1WXQnl-0004cF-SK
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 07:50:37 +0000
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;
Received: from mail-ob0-f176.google.com ([209.85.214.176])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXQnk-0000WD-TJ
for bitcoin-development@lists.sourceforge.net;
Tue, 08 Apr 2014 07:50:37 +0000
Received: by mail-ob0-f176.google.com with SMTP id wp18so592000obc.21
for <bitcoin-development@lists.sourceforge.net>;
Tue, 08 Apr 2014 00:50:31 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.50.163 with SMTP id d3mr1922210oeo.51.1396943431531; Tue,
08 Apr 2014 00:50:31 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Tue, 8 Apr 2014 00:50:31 -0700 (PDT)
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
X-Google-Sender-Auth: Eeo-btNbfPBjVq9CoKl68f8Lv6g
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
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
(mh.in.england[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: 1WXQnk-0000WD-TJ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Why are we bleeding nodes?
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, 08 Apr 2014 07:50:38 -0000
--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't a magic wand that we =
can<br>
wave to make everyone secure. =C2=A0The protocols and techniques necessary<=
br>
don'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're OK with using a specific web wallet there'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's quite compl=
icated. As with all these features.</div>
</div></div></div>
--001a11c309da02074404f6833dfc--
|
