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
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <elombrozo@gmail.com>) id 1Z5tut-0005Yz-6l
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 10:52:59 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.51 as permitted sender)
client-ip=209.85.220.51; envelope-from=elombrozo@gmail.com;
helo=mail-pa0-f51.google.com;
Received: from mail-pa0-f51.google.com ([209.85.220.51])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5tur-0006Og-NQ
for bitcoin-development@lists.sourceforge.net;
Fri, 19 Jun 2015 10:52:59 +0000
Received: by pabvl15 with SMTP id vl15so36904480pab.1
for <bitcoin-development@lists.sourceforge.net>;
Fri, 19 Jun 2015 03:52:52 -0700 (PDT)
X-Received: by 10.68.136.42 with SMTP id px10mr30936636pbb.19.1434711172029;
Fri, 19 Jun 2015 03:52:52 -0700 (PDT)
Received: from [192.168.1.102] (cpe-76-167-237-202.san.res.rr.com.
[76.167.237.202])
by mx.google.com with ESMTPSA id c3sm10873005pdk.39.2015.06.19.03.52.49
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Fri, 19 Jun 2015 03:52:50 -0700 (PDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed;
boundary="Apple-Mail=_D06283BA-A681-4987-B394-7A713235585C";
protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b6
From: Eric Lombrozo <elombrozo@gmail.com>
In-Reply-To: <CANEZrP33GCiZHK1GV2Qt_R_AHK6SEjybGPtmORjqgvQ9MiYVZQ@mail.gmail.com>
Date: Fri, 19 Jun 2015 03:52:48 -0700
Message-Id: <5E49FE9F-CC70-4DFD-8055-68E9372923DF@gmail.com>
References: <55828737.6000007@riseup.net>
<CABm2gDoa7KxsgvREo3yiNjfd6AeayqAqkjMe2rvX8yyxR_ddcA@mail.gmail.com>
<55831CAB.2080303@jrn.me.uk> <1867667.WXWC1C9quc@crushinator>
<CAOG=w-scXm-46sp2NgR2UUp20R5ujuaAzW-jU_Owh20C4Xc=9A@mail.gmail.com>
<CAJHLa0Mhnma8_ys2ckEA+dLT-EWnqO4j8YKMSaf3Tvv_K14czQ@mail.gmail.com>
<CAOG=w-tf7qz9XSkDg5POKtFLkHWDA==jf2iVxVL8wz1hqcAVOg@mail.gmail.com>
<CANEZrP33GCiZHK1GV2Qt_R_AHK6SEjybGPtmORjqgvQ9MiYVZQ@mail.gmail.com>
To: Mike Hearn <mike@plan99.net>
X-Mailer: Apple Mail (2.2098)
X-Spam-Score: -0.6 (/)
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
(elombrozo[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1Z5tur-0006Og-NQ
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>,
Gavin Andresen <gavin@bitcoinfoundation.org>
Subject: Re: [Bitcoin-development] Concerns Regarding Threats by a Developer
to Remove Commit Access from Other Developers
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: Fri, 19 Jun 2015 10:52:59 -0000
--Apple-Mail=_D06283BA-A681-4987-B394-7A713235585C
Content-Type: multipart/alternative;
boundary="Apple-Mail=_3A6D511D-5907-4232-AB9F-F7095E8F1636"
--Apple-Mail=_3A6D511D-5907-4232-AB9F-F7095E8F1636
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
> On Jun 19, 2015, at 2:37 AM, Mike Hearn <mike@plan99.net> wrote:
>=20
> Or alternatively, fix the reasons why users would have negative =
experiences with full blocks
>=20
> It's impossible, Mark. By definition if Bitcoin does not have =
sufficient capacity for everyone's transactions, some users who were =
using it will be kicked out to make way for the others. Whether that =
happens in some kind of stable organised way or (as with the current =
code) a fairly chaotic way doesn't change the fundamental truth: some =
users will find their bitcoin savings have become uneconomic to spend.
>=20
> Here's a recent user complaint that provides a preview of coming =
attractions:
>=20
> =
https://www.reddit.com/r/Bitcoin/comments/39r3bi/breadwallet_asking_me_to_=
pay_over_10_network_fee/ =
<https://www.reddit.com/r/Bitcoin/comments/39r3bi/breadwallet_asking_me_to=
_pay_over_10_network_fee/>
>=20
> Hello, I'm just trying to send my small Sarutobi-tips stash (12,159 =
bits) onto a paper wallet. When I try to send it, a window pops up =
stating "insufficient funds for bitcoin network fee, reduce payment =
amount by 1,389 bits?" This would be a fee of $0.32 to send my $2.82, =
leaving me with $2.50.
>=20
> These sorts of complaints will get more frequent and more extreme in =
the coming months. I realise that nobody at Blockstream is in the =
position of running an end user facing service, but many of us are .... =
and we will be the ones that face the full anger of ordinary users as =
Bitcoin hits the wall.
Mike,
With all due respect, many of us DO run end user facing services=E2=80=A6a=
nd would rather see a fundamental problem *fixed* rather than merely =
covered up temporarily=E2=80=A6hoping nobody notices.
The user experience of Bitcoin is already horrendous=E2=80=A6unless you =
use a centralized validator web wallet. Even SPV is fundamentally broken =
(and I would have pegged you for being one of the people most directly =
aware of this fact). If we=E2=80=99re going for centralized validation, =
why even use a blockchain in the first place? We already have much =
faster, more efficient technology that can do that kind of stuff at a =
fraction of the cost. If you have well-established entities running =
banking services, we have other mechanisms in place that can help keep =
them honest=E2=80=A6other far more efficient protocols. We=E2=80=99re =
basically defeating the very purpose of this invention.
Then there are a bunch of other =E2=80=9Cinconveniences=E2=80=9D about =
the way Bitcoin currently works. For instance, have you ever received a =
bunch of small payments (i.e. a crowdsale) and then found yourself in =
the position of having to suddenly move a big chunk of that on the =
blockchain=E2=80=A6only to discover all the txouts you were spending =
added up to hundreds of kB or more? Or have you ever had to send a small =
payment but only had one large output in your wallet=E2=80=A6which meant =
that the entirety of those funds were tied up until the first =
transaction got signed and propagated? Yes, the protocol has MANY =
serious issues=E2=80=A6of which the =E2=80=9Csend and forget=E2=80=9D =
fee model as opposed to the =E2=80=9Csend and bid model=E2=80=9D is just =
one.
Bitcoin was designed from the beginning with the idea that sooner or =
later fees would be a significant component of the network. The problem =
was never really fully addressed and solved - I=E2=80=99m glad to see =
that finally some good people in this space are starting to seriously =
think about solutions.
Mike, are you telling us you=E2=80=99d rather avoid user complaints at =
all costs even if that means building something shitty for them that =
doesn=E2=80=99t really serve its stated purpose? If those are your =
standards then no thanks, I don=E2=80=99t want to be part of your fork. =
And I don=E2=80=99t think I=E2=80=99m alone in this sentiment.
- Eric Lombrozo
> =
--------------------------------------------------------------------------=
----
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--Apple-Mail=_3A6D511D-5907-4232-AB9F-F7095E8F1636
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On Jun 19, 2015, at 2:37 AM, Mike Hearn <<a =
href=3D"mailto:mike@plan99.net" class=3D"">mike@plan99.net</a>> =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><blockquote 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;padding-left:1ex"><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"">Or =
alternatively, fix the reasons why users would have negative experiences =
with full blocks</div></div></div></div></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">It's impossible, Mark. <i class=3D"">By =
definition</i> if Bitcoin does not have sufficient capacity for =
everyone's transactions, some users who were using it will be kicked out =
to make way for the others. Whether that happens in some kind of stable =
organised way or (as with the current code) a fairly chaotic way doesn't =
change the fundamental truth: <b class=3D"">some users will find their =
bitcoin savings have become uneconomic to spend</b>.</div><div =
class=3D""><b class=3D""><br class=3D""></b></div><div class=3D"">Here's =
a recent user complaint that provides a preview of coming =
attractions:</div><div class=3D""><br class=3D""></div><div class=3D""><a =
href=3D"https://www.reddit.com/r/Bitcoin/comments/39r3bi/breadwallet_askin=
g_me_to_pay_over_10_network_fee/" =
class=3D"">https://www.reddit.com/r/Bitcoin/comments/39r3bi/breadwallet_as=
king_me_to_pay_over_10_network_fee/</a><br class=3D""></div><div =
class=3D""><br class=3D""></div><blockquote 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;padding-left:1ex"><span =
style=3D"font-family:Verdana,arial,sans-serif;font-size:14px;line-height:1=
8.2000007629395px" class=3D"">Hello, I'm just trying to send my small =
Sarutobi-tips stash (12,159 bits) onto a paper wallet. When I try to =
send it, a window pops up stating "insufficient funds for bitcoin =
network fee, reduce payment amount by 1,389 bits?" This would be a fee =
of $0.32 to send my $2.82, leaving me with =
$2.50.</span></blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">These sorts of complaints will get more frequent and more =
extreme in the coming months. I realise that nobody at Blockstream is =
in the position of running an end user facing service, but many of =
us are .... and we will be the ones that face the full anger of ordinary =
users as Bitcoin hits the =
wall.</div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>Mike,</div><div><br class=3D""></div><div>With all =
due respect, many of us DO run end user facing services=E2=80=A6and =
would rather see a fundamental problem *fixed* rather than merely =
covered up temporarily=E2=80=A6hoping nobody notices.</div><div><br =
class=3D""></div><div>The user experience of Bitcoin is already =
horrendous=E2=80=A6unless you use a centralized validator web wallet. =
Even SPV is fundamentally broken (and I would have pegged you for being =
one of the people most directly aware of this fact). If we=E2=80=99re =
going for centralized validation, why even use a blockchain in the first =
place? We already have much faster, more efficient technology that can =
do that kind of stuff at a fraction of the cost. If you have =
well-established entities running banking services, we have other =
mechanisms in place that can help keep them honest=E2=80=A6other far =
more efficient protocols. We=E2=80=99re basically defeating the very =
purpose of this invention.</div><div><br class=3D""></div><div>Then =
there are a bunch of other =E2=80=9Cinconveniences=E2=80=9D about the =
way Bitcoin currently works. For instance, have you ever received a =
bunch of small payments (i.e. a crowdsale) and then found yourself in =
the position of having to suddenly move a big chunk of that on the =
blockchain=E2=80=A6only to discover all the txouts you were spending =
added up to hundreds of kB or more? Or have you ever had to send a small =
payment but only had one large output in your wallet=E2=80=A6which meant =
that the entirety of those funds were tied up until the first =
transaction got signed and propagated? Yes, the protocol has MANY =
serious issues=E2=80=A6of which the =E2=80=9Csend and forget=E2=80=9D =
fee model as opposed to the =E2=80=9Csend and bid model=E2=80=9D is just =
one.</div><div><br class=3D""></div><div>Bitcoin was designed from the =
beginning with the idea that sooner or later fees would be a significant =
component of the network. The problem was never really fully addressed =
and solved - I=E2=80=99m glad to see that finally some good people in =
this space are starting to seriously think about =
solutions.</div><div><br class=3D""></div><div>Mike, are you telling us =
you=E2=80=99d rather avoid user complaints at all costs even if that =
means building something shitty for them that doesn=E2=80=99t really =
serve its stated purpose? If those are your standards then no thanks, I =
don=E2=80=99t want to be part of your fork. And I don=E2=80=99t think =
I=E2=80=99m alone in this sentiment.</div><div><br =
class=3D""></div><div><br class=3D""></div><div>- Eric =
Lombrozo</div><div><br class=3D""></div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D"">
=
--------------------------------------------------------------------------=
----<br class=3D"">_______________________________________________<br =
class=3D"">Bitcoin-development mailing list<br class=3D""><a =
href=3D"mailto:Bitcoin-development@lists.sourceforge.net" =
class=3D"">Bitcoin-development@lists.sourceforge.net</a><br =
class=3D"">https://lists.sourceforge.net/lists/listinfo/bitcoin-developmen=
t<br class=3D""></div></blockquote></div><div class=3D""><br =
class=3D""></div></body></html>=
--Apple-Mail=_3A6D511D-5907-4232-AB9F-F7095E8F1636--
--Apple-Mail=_D06283BA-A681-4987-B394-7A713235585C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJVg/SAAAoJEJNAI64YFENUq3gP/3QmFityuD5hT08nK8+5GZfz
+MaZtLJi9A7yYDO0NYu9zxLPeq+f6Wr3Q2xxUuOmjXNGDQpTfoA++NeLe4Z9jhWp
ecPPPPdU50kzqxUd+XXTP6kekmThUaswSBXN8+CB3C+2VpOsrjSngSZr4+tVsxOA
xd0rMx/pN9wymW27yqMkZrb+u/VjByfC7WmFrFVh4lDgmptndivJYY4iGhd4A1y2
Y0GLgOIqinWmoQWOAxrTRseNDhQ2cLl4pDea+u696fOP5p8h5Zzyfga3n/adf4Vt
BJEwVj6GxymN53HKWkjn8MaxAlqOZkTY/UVwlBuJWiNLdA2RHJqSzqvfF1DaL+6n
QCFJnzJ2gS2TPkA5ZowONV1RS1iv8LTmq7ZS7PCz4ZB38XzWMLKu9wp7FOouMY3D
RAe0Gw4h/0gjZzpBRd9uMt0TBVzoE1oB3W1beLrQoCS15OI9x8v5rLax3X/w039u
tYIQ77uhwSY8zMcYV7Kws5oJaQ/T5wSRK28tjAtQ9NhWd0xpxi3EoKzFuWv2E16F
0C64y5n7S/9vYAhMErPlIUNb38YDMgyS7ViNzyXeD/1XLmuhlq6FehpUy98q+ueO
99RnRRsvaaIdqB0Y1zR0KsgsBhpmAtuyvNV0FykuuDS3WtNVhDqjKQmx6MH5RnaL
kVkuaRmoyDc7UE9+7iGA
=KtS4
-----END PGP SIGNATURE-----
--Apple-Mail=_D06283BA-A681-4987-B394-7A713235585C--
|