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
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1WXASz-0005np-P5
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 14:24:05 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.53 as permitted sender)
client-ip=209.85.219.53; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f53.google.com;
Received: from mail-oa0-f53.google.com ([209.85.219.53])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXASy-0005O2-GA
for bitcoin-development@lists.sourceforge.net;
Mon, 07 Apr 2014 14:24:05 +0000
Received: by mail-oa0-f53.google.com with SMTP id j17so6746638oag.12
for <bitcoin-development@lists.sourceforge.net>;
Mon, 07 Apr 2014 07:23:59 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.76.194 with SMTP id m2mr7462043oew.47.1396880639106; Mon,
07 Apr 2014 07:23:59 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.96.180 with HTTP; Mon, 7 Apr 2014 07:23:59 -0700 (PDT)
In-Reply-To: <CAAf19Wrz0u_e5V9Gb=_CAG=mHtE9nA_VETgYZeCXZqwaGeYKuQ@mail.gmail.com>
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>
Date: Mon, 7 Apr 2014 16:23:59 +0200
X-Google-Sender-Auth: gpTq2HkiIqvFdEaDG89xi7MgVe0
Message-ID: <CANEZrP2rqu9yCjmoCRmVMe91mxtkFe4ep5eWHWSrn_PSUa92WA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Eric Martindale <eric@ericmartindale.com>
Content-Type: multipart/alternative; boundary=047d7b33cea649a74d04f6749e28
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: 1WXASy-0005O2-GA
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
Andreas Schildbach <andreas@schildbach.de>
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: Mon, 07 Apr 2014 14:24:05 -0000
--047d7b33cea649a74d04f6749e28
Content-Type: text/plain; charset=UTF-8
Indeed, fully agreed. The only way to really make progress here is to make
the UX of being your own bank not only as good as trusting a third party,
but better.
I've been encouraged by the rise of risk analysis services, but we need to
integrate them into wallets more widely for them to have much impact.
Otherwise people get to pick between a variety of wallets, none of which
have *all* the features they want. And TREZOR is cool, albeit, something
that's going to be for committed users only.
On Mon, Apr 7, 2014 at 4:15 PM, Eric Martindale <eric@ericmartindale.com>wrote:
> We need to make it so mind-numbingly simple to "run Bitcoin correctly"
> that the average user doesn't find reasons to do so in the course of normal
> use. Right now, Coinbase and Bitstamp are winning in the user experience
> battle, which technically endanger the user, and by proxy the Bitcoin
> network.
>
> Multi-sig as a default is a start. It won't succeed unless the user
> experience is simply better than trusted third parties, but we need to
> start the education process with the very basic fundamental: trusting a
> third-party with full access to your Bitcoin is just replacing one
> centralized banking system with another.
>
> Eric Martindale
> Developer Evangelist, BitPay
> +1 (919) 374-2020
> On Apr 7, 2014 7:05 AM, "Mike Hearn" <mike@plan99.net> wrote:
>
>> My guess is that a large number of users have lost interest after they
>>> lost their money in MtGox. The 24th of February coincides with the
>>> "final" shutdown
>>
>>
>> Sigh. It would not be surprising if MtGox has indeed dealt the community
>> a critical blow in this regard. TX traffic is down since then too:
>>
>>
>> https://blockchain.info/charts/n-transactions-excluding-popular?timespan=60days&showDataPoints=false&daysAverageString=1&show_header=true&scale=0&address=
>>
>> Judging from comments and the leaked user db, it seems a lot of well
>> known people lost money there (not me fortunately). I wish I could say
>> people have learned but from the size of the deposit base at Bitstamp they
>> clearly have not. A lot of Bitcoin users don't seem to be ready to be their
>> own bank, yet still want to own some on the assumption everyone else either
>> is or soon will be. So it's really only a matter of time until something
>> goes wrong with some large bitbank again, either Bitstamp or Coinbase.
>>
>> Some days I wonder if Bitcoin will be killed off by people who just
>> refuse to use it properly before it ever gets a chance to shine. The
>> general public doesn't distinguish between "Bitcoin users" who deposit with
>> a third party and the real Bitcoin users who don't.
>>
>>
>> ------------------------------------------------------------------------------
>> Put Bad Developers to Shame
>> Dominate Development with Jenkins Continuous Integration
>> Continuously Automate Build, Test & Deployment
>> Start a new project now. Try Jenkins in the cloud.
>> http://p.sf.net/sfu/13600_Cloudbees_APR
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>>
>>
--047d7b33cea649a74d04f6749e28
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Indeed, fully agreed. The only way to really make progress=
here is to make the UX of being your own bank not only as good as trusting=
a third party, but better.<div><br></div><div>I've been encouraged by =
the rise of risk analysis services, but we need to integrate them into wall=
ets more widely for them to have much impact. Otherwise people get to pick =
between a variety of wallets, none of which have <i>all</i>=C2=A0the featur=
es they want. And TREZOR is cool, albeit, something that's going to be =
for committed users only.</div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Apr 7, 2014 at 4:15 PM, Eric Martindale <span dir=3D"ltr">&=
lt;<a href=3D"mailto:eric@ericmartindale.com" target=3D"_blank">eric@ericma=
rtindale.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"><p dir=3D"ltr">We need to make it so mind-nu=
mbingly simple to "run Bitcoin correctly" that the average user d=
oesn't find reasons to do so in the course of normal use.=C2=A0 Right n=
ow, Coinbase and Bitstamp are winning in the user experience battle, which =
technically endanger the user, and by proxy the Bitcoin network.</p>
<p dir=3D"ltr">Multi-sig as a default is a start.=C2=A0 It won't succee=
d unless the user experience is simply better than trusted third parties, b=
ut we need to start the education process with the very basic fundamental: =
trusting a third-party with full access to your Bitcoin is just replacing o=
ne centralized banking system with another. </p>
<span class=3D"HOEnZb"><font color=3D"#888888">
<p dir=3D"ltr">Eric Martindale <br>
Developer Evangelist, BitPay<br>
<a href=3D"tel:%2B1%20%28919%29%20374-2020" value=3D"+19193742020" target=
=3D"_blank">+1 (919) 374-2020</a></p>
</font></span><div class=3D"gmail_quote"><div><div class=3D"h5">On Apr 7, 2=
014 7:05 AM, "Mike Hearn" <<a href=3D"mailto:mike@plan99.net" =
target=3D"_blank">mike@plan99.net</a>> wrote:<br type=3D"attribution"></=
div></div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div class=3D"h5">
<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">
My guess is that a large number of users have lost interest after they<br>
lost their money in MtGox. The 24th of February coincides with the<br>
"final" shutdown</blockquote><div><br></div><div>Sigh. It would n=
ot be surprising if MtGox has indeed dealt the community a critical blow in=
this regard. TX traffic is down since then too:</div><div><br></div><div>
<a href=3D"https://blockchain.info/charts/n-transactions-excluding-popular?=
timespan=3D60days&showDataPoints=3Dfalse&daysAverageString=3D1&=
show_header=3Dtrue&scale=3D0&address=3D" target=3D"_blank">https://=
blockchain.info/charts/n-transactions-excluding-popular?timespan=3D60days&a=
mp;showDataPoints=3Dfalse&daysAverageString=3D1&show_header=3Dtrue&=
amp;scale=3D0&address=3D</a></div>
<div><br></div><div>Judging from comments and the leaked user db, it seems =
a lot of well known people lost money there =C2=A0 (not me fortunately). I =
wish I could say people have learned but from the size of the deposit base =
at Bitstamp they clearly have not. A lot of Bitcoin users don't seem to=
be ready to be their own bank, yet still want to own some on the assumptio=
n everyone else either is or soon will be. So it's really only a matter=
of time until something goes wrong with some large bitbank again, either B=
itstamp or Coinbase.</div>
<div><br></div><div>Some days I wonder if Bitcoin will be killed off by peo=
ple who just refuse to use it properly before it ever gets a chance to shin=
e. The general public doesn't distinguish between "Bitcoin users&q=
uot; who deposit with a third party and the real Bitcoin users who don'=
t.</div>
</div></div></div>
<br></div></div><div class=3D"">-------------------------------------------=
-----------------------------------<br>
Put Bad Developers to Shame<br>
Dominate Development with Jenkins Continuous Integration<br>
Continuously Automate Build, Test & Deployment<br>
Start a new project now. Try Jenkins in the cloud.<br>
<a href=3D"http://p.sf.net/sfu/13600_Cloudbees_APR" target=3D"_blank">http:=
//p.sf.net/sfu/13600_Cloudbees_APR</a><br>_________________________________=
______________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@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>
<br></div></blockquote></div>
</blockquote></div><br></div>
--047d7b33cea649a74d04f6749e28--
|
