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
|
Return-Path: <morcos@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D5C9D26C
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 Aug 2015 14:24:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com
[209.85.213.169])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AC5BB1BC
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 Aug 2015 14:24:19 +0000 (UTC)
Received: by igbpg9 with SMTP id pg9so70118350igb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 Aug 2015 07:24:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=6DCqTZdkXyZ5cJQMUK+FsHWkOGYb5nhAcYFR10ro1y8=;
b=tHItmpNtSwkJm9kYZyNLirgB69XgYAYgFOTpHmTyACdnAfemyjZxfsUCyQlVF17qL+
ejc1vlh9sLgy6lLMpjNlGC4xGnCsFW7HMrr2kvNeyS8kqfI0JsGu+rP0ZlJNozyykwRo
Hkk/4x4KfBuJvWWXdRC0rm2f9CCWs1Tf7n7dSCtdYRuT4qWxiVV3ROamIT2qRzA9GoKG
XQbAzp0hN4NzIJlMBb6rltEAepmaxfEi0F7tXahUkjfosX1bZynvfv0b4SHHmx9emJ1g
XvGPFN+y0UBZ5sEnku72KPLltDHw5VOdOulKHXZ7IYuxO8+NtMXiNhU7ZUF3isF0RB/1
XQdA==
MIME-Version: 1.0
X-Received: by 10.50.78.161 with SMTP id c1mr11631805igx.35.1439216658685;
Mon, 10 Aug 2015 07:24:18 -0700 (PDT)
Received: by 10.64.241.137 with HTTP; Mon, 10 Aug 2015 07:24:18 -0700 (PDT)
In-Reply-To: <CABsx9T2aZHe5382_fC7bEG2OFPadS3p0jjaAD8FW7p36XS7tcA@mail.gmail.com>
References: <CABsx9T16fH+56isq95m4+QWsKwP==tf75ep8ghnEcBoV4OtZJA@mail.gmail.com>
<CAPg+sBgOt=qhQVZv5P-4mcD75=L4PKgOfRqhyB6FZdSYQajrwQ@mail.gmail.com>
<CABsx9T10y6-=c7Qg6jysnf38wRX3NA3wWozxGfE+mEYJvPeqWA@mail.gmail.com>
<CABm2gDpwMQzju+Gsoe3qMi60MPr7OAiSuigy3RdA1xh-SwFzbw@mail.gmail.com>
<CABsx9T2aZHe5382_fC7bEG2OFPadS3p0jjaAD8FW7p36XS7tcA@mail.gmail.com>
Date: Mon, 10 Aug 2015 10:24:18 -0400
Message-ID: <CAPWm=eV2VB+0X8RJ-ti7B4FX3=d_VL7ye+PxLisMez2UTRzc7A@mail.gmail.com>
From: Alex Morcos <morcos@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=089e0111e07ab22a15051cf5bdb2
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Fees and the block-finding process
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Aug 2015 14:24:20 -0000
--089e0111e07ab22a15051cf5bdb2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Gavin,
They are not analogous.
Increasing performance and making other changes that will help allow
scaling can be done while at small scale or large scale.
Dealing with full blocks and the resultant feedback effects is something
that can only be done when blocks are full. It's just too complicated a
problem to solve without seeing the effects first hand, and unlike the
block size/scaling concerns, its binary, you're either in the situation
where demands outgrows supply or you aren't.
Fee estimation is one example, I tried very hard to make fee estimation
work well when blocks started filling up but it was impossible to truly
test and in the small sample of full blocks we've gotten since the code
went live, many improvements made themselves obvious. Expanding mempools
is another issue that doesn't exist at all if supply > demand. Turns out
to also be a difficult problem to solve.
Nevertheless, I mostly agree that these arguments shouldn't be the reason
not to expand block size, I think they are more just an example of how
immature all of this technology is, and we should be concentrating on
improving it before we're trying to scale it to world acceptance levels.
The saddest thing about this whole debate is how fundamental improvements
to the science of cryptocurrencies (things like segregated witness and
confidential transactions) are just getting lost in the circus debate
around trying to cram a few more users into the existing system sooner
rather than later.
On Mon, Aug 10, 2015 at 10:12 AM, Gavin Andresen via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Fri, Aug 7, 2015 at 1:33 PM, Jorge Tim=C3=B3n <jtimon@jtimon.cc> wrote=
:
>
>>
>> On Aug 7, 2015 5:55 PM, "Gavin Andresen" <gavinandresen@gmail.com> wrote=
:
>> >
>> > I think there are multiple reasons to raise the maximum block size, an=
d
>> yes, fear of Bad Things Happening as we run up against the 1MB limit is =
one
>> of the reasons.
>>
>> What are the other reasons?
>>
>> > I take the opinion of smart engineers who actually do resource plannin=
g
>> and have seen what happens when networks run out of capacity very seriou=
sly.
>>
>> When "the network runs out of capacity" (when we hit the limit) do we
>> expect anything to happen apart from minimum market fees rising (above
>> zero)?
>> Obviously any consequences of fees rising are included in this concern.
>>
> It is frustrating to answer questions that we answered months ago,
> especially when I linked to these in response to your recent "increase
> advocates say that not increasing the max block size will KILL BITCOIN"
> false claim:
> http://gavinandresen.ninja/why-increasing-the-max-block-size-is-urgent
> https://medium.com/@octskyward/crash-landing-f5cc19908e32
>
> Executive summary: when networks get over-saturated, they become
> unreliable. Unreliable is bad.
>
> Unreliable and expensive is extra bad, and that's where we're headed
> without an increase to the max block size.
>
> RE: the recent thread about "better deal with that type of thing now
> rather than later" : exactly the same argument can be made about changes
> needed to support a larger block size-- "better to do that now than to do
> that later." I don't think either of those arguments are very convincing=
.
>
>
> --
> --
> Gavin Andresen
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--089e0111e07ab22a15051cf5bdb2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Gavin,<div>They are not analogous.</div><div><br></div><di=
v>Increasing performance and making other changes that will help allow scal=
ing can be done while at small scale or large scale.</div><div>Dealing with=
full blocks and the resultant feedback effects is something that can only =
be done when blocks are full.=C2=A0 It's just too complicated a problem=
to solve without seeing the effects first hand, and unlike the block size/=
scaling concerns, its binary, you're either in the situation where dema=
nds outgrows supply or you aren't. =C2=A0</div><div><br></div><div>Fee =
estimation is one example, I tried very hard to make fee estimation work we=
ll when blocks started filling up but it was impossible to truly test and i=
n the small sample of full blocks we've gotten since the code went live=
, many improvements made themselves obvious.=C2=A0 Expanding mempools is an=
other issue that doesn't exist at all if supply > demand. =C2=A0 Tur=
ns out to also be a difficult problem to solve.</div><div><br></div><div>Ne=
vertheless, I mostly agree that these arguments shouldn't be the reason=
not to expand block size, I think they are more just an example of how imm=
ature all of this technology is, and we should be concentrating on improvin=
g it before we're trying to scale it to world acceptance levels.=C2=A0 =
The saddest thing about this whole debate is how fundamental improvements t=
o the science of cryptocurrencies (things like segregated witness and confi=
dential transactions) are just getting lost in the circus debate around try=
ing to cram a few more users into the existing system sooner rather than la=
ter.</div><div><br></div><div><br></div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Mon, Aug 10, 2015 at 10:12 AM, Gavin Andres=
en via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@list=
s.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.=
org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><div class=3D"gmail_extra"><div><div class=3D"h5"><div class=3D"gmail_quo=
te">On Fri, Aug 7, 2015 at 1:33 PM, Jorge Tim=C3=B3n <span dir=3D"ltr"><=
<a href=3D"mailto:jtimon@jtimon.cc" target=3D"_blank">jtimon@jtimon.cc</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><p dir=3D"ltr"><b=
r>
On Aug 7, 2015 5:55 PM, "Gavin Andresen" <<a href=3D"mailto:ga=
vinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</a>> wr=
ote:<br>
><br>
> I think there are multiple reasons to raise the maximum block size, an=
d yes, fear of Bad Things Happening as we run up against the 1MB limit is o=
ne of the reasons.</p>
</span><p dir=3D"ltr">What are the other reasons?</p><span>
<p dir=3D"ltr">> I take the opinion of smart engineers who actually do r=
esource planning and have seen what happens when networks run out of capaci=
ty very seriously.</p>
</span><p dir=3D"ltr">When "the network runs out of capacity" (wh=
en we hit the limit) do we expect anything to happen apart from minimum mar=
ket fees rising (above zero)?<br>
Obviously any consequences of fees rising are included in this concern.</p>
</blockquote></div></div></div>It is frustrating to answer questions that w=
e answered months ago, especially when I linked to these in response to you=
r recent "increase advocates say that not increasing the max block siz=
e will KILL BITCOIN" false claim:</div><div class=3D"gmail_extra">=C2=
=A0=C2=A0<a href=3D"http://gavinandresen.ninja/why-increasing-the-max-block=
-size-is-urgent" target=3D"_blank">http://gavinandresen.ninja/why-increasin=
g-the-max-block-size-is-urgent</a></div><div class=3D"gmail_extra">=C2=A0=
=C2=A0<a href=3D"https://medium.com/@octskyward/crash-landing-f5cc19908e32"=
target=3D"_blank">https://medium.com/@octskyward/crash-landing-f5cc19908e3=
2</a></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">=
Executive summary: when networks get over-saturated, they become unreliable=
.=C2=A0 Unreliable is bad.</div><div class=3D"gmail_extra"><br></div><div c=
lass=3D"gmail_extra">Unreliable and expensive is extra bad, and that's =
where we're headed without an increase to the max block size.</div><div=
class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">RE: the recent =
thread about "better deal with that type of thing now rather than late=
r" : =C2=A0exactly the same argument can be made about changes needed =
to support a larger block size-- "better to do that now than to do tha=
t later." =C2=A0I don't think either of those arguments are very c=
onvincing.</div><span class=3D"HOEnZb"><font color=3D"#888888"><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div><br></div>-- <br=
><div>--<br>Gavin Andresen<br></div><div><br></div>
</div></font></span></div>
<br>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
<br></blockquote></div><br></div>
--089e0111e07ab22a15051cf5bdb2--
|
