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
|
Return-Path: <gavinandresen@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 105EE25A
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 Aug 2015 14:12:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com
[209.85.217.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id A1DA8E8
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 Aug 2015 14:12:07 +0000 (UTC)
Received: by lbbpu9 with SMTP id pu9so68369178lbb.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 10 Aug 2015 07:12:06 -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=diOO+/RQp2k+plNz7B0LPWG3WL1TaJvqcavWnb4Inaw=;
b=ezOzDN5KQ0ZaFh6wUWTF5Svf3DKzE3mwg+eRqEROuv3+j7CT+oS8SAj5qexJAa6Kz9
xf6CoNrl11V8aOYMkvdOcgEJ3DOQABlYsmF65WpuZpfnITXaz81h+Fo8TpE2hpIkVUik
USoIFLbaVo+RcbB5FpQ/C/AfXuH6hrjvE/XItmnzW2I2SRQ5nf/Ejtvrugbr443biB5+
+1nwclWcc/2ZvyFd57nooha8oVE1UcoOYtTugHEKRlXm6jXW77C4DqKUxtjo/GOH75EG
pob3a+1oDjQ1tgRPinQHT8+ZJgWv/0fJlvMHBu9PfvgSPWcEl2533t8MI0d+hr8ANoo7
9Vfg==
MIME-Version: 1.0
X-Received: by 10.152.43.41 with SMTP id t9mr20304444lal.4.1439215925890; Mon,
10 Aug 2015 07:12:05 -0700 (PDT)
Received: by 10.25.62.14 with HTTP; Mon, 10 Aug 2015 07:12:05 -0700 (PDT)
In-Reply-To: <CABm2gDpwMQzju+Gsoe3qMi60MPr7OAiSuigy3RdA1xh-SwFzbw@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>
Date: Mon, 10 Aug 2015 10:12:05 -0400
Message-ID: <CABsx9T2aZHe5382_fC7bEG2OFPadS3p0jjaAD8FW7p36XS7tcA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=001a11c27f400493b6051cf59221
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:12:09 -0000
--001a11c27f400493b6051cf59221
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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, and
> yes, fear of Bad Things Happening as we run up against the 1MB limit is o=
ne
> of the reasons.
>
> What are the other reasons?
>
> > I take the opinion of smart engineers who actually do resource planning
> and have seen what happens when networks run out of capacity very serious=
ly.
>
> 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.
--=20
--
Gavin Andresen
--001a11c27f400493b6051cf59221
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">On F=
ri, 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>></sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><p dir=3D"ltr=
"><br>
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 class=3D"">
<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>It is frustrating to answer questions that we answered m=
onths ago, especially when I linked to these in response to your recent &qu=
ot;increase advocates say that not increasing the max block size will KILL =
BITCOIN" false claim:</div><div class=3D"gmail_extra">=C2=A0=C2=A0<a h=
ref=3D"http://gavinandresen.ninja/why-increasing-the-max-block-size-is-urge=
nt">http://gavinandresen.ninja/why-increasing-the-max-block-size-is-urgent<=
/a></div><div class=3D"gmail_extra">=C2=A0=C2=A0<a href=3D"https://medium.c=
om/@octskyward/crash-landing-f5cc19908e32">https://medium.com/@octskyward/c=
rash-landing-f5cc19908e32</a></div><div class=3D"gmail_extra"><br></div><di=
v 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 class=3D"gmail_extra">Unreliable and expensive is ex=
tra bad, and that's where we're headed without an increase to the m=
ax block size.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmai=
l_extra">RE: the recent thread about "better deal with that type of th=
ing now rather than later" : =C2=A0exactly the same argument can be ma=
de about changes needed to support a larger block size-- "better to do=
that now than to do that later." =C2=A0I don't think either of th=
ose arguments are very convincing.</div><div class=3D"gmail_extra"><br></di=
v><div class=3D"gmail_extra"><div><br></div>-- <br><div class=3D"gmail_sign=
ature">--<br>Gavin Andresen<br></div><div class=3D"gmail_signature"><br></d=
iv>
</div></div>
--001a11c27f400493b6051cf59221--
|
