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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <morcos@gmail.com>) id 1YqNLn-000164-Q6
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 15:04:35 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.50 as permitted sender)
client-ip=74.125.82.50; envelope-from=morcos@gmail.com;
helo=mail-wg0-f50.google.com;
Received: from mail-wg0-f50.google.com ([74.125.82.50])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YqNLj-0004Ll-Oc
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 15:04:35 +0000
Received: by wgyo15 with SMTP id o15so46576528wgy.2
for <bitcoin-development@lists.sourceforge.net>;
Thu, 07 May 2015 08:04:25 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.180.75.197 with SMTP id e5mr7458234wiw.94.1431011065687;
Thu, 07 May 2015 08:04:25 -0700 (PDT)
Received: by 10.180.168.34 with HTTP; Thu, 7 May 2015 08:04:25 -0700 (PDT)
In-Reply-To: <CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>
References: <554A91BE.6060105@bluematt.me>
<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
<CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>
Date: Thu, 7 May 2015 11:04:25 -0400
Message-ID: <CAPWm=eUFe7dKJCLeNACZ4n9vw0Xj9rHVM_RRLSczGXNU-ShR2w@mail.gmail.com>
From: Alex Morcos <morcos@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043be0ee3d728005157f3a85
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
(morcos[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: 1YqNLj-0004Ll-Oc
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
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: Thu, 07 May 2015 15:04:35 -0000
--f46d043be0ee3d728005157f3a85
Content-Type: text/plain; charset=UTF-8
That strikes me as a dangerous path forward.
I don't actually think there is anything wrong with this: "everybody
eventually gets tired of arguing angels-dancing-on-the-head-of-a-pin, and
we're left with the status quo"
What gives Bitcoin value aren't its technical merits but the fact that
people believe in it. The biggest risk here isn't that 20MB blocks will
be bad or that 1MB blocks will be bad, but that by forcing a hard fork that
isn't nearly universally agreed upon, we will be damaging that belief. If
I strongly believed some hard fork would be better for Bitcoin, say
permanent inflation of 1% a year to fund mining, and I managed to convince
80% of users, miners, businesses and developers to go along with me, I
would still vote against doing it. Because that's not nearly universal
agreement, and it changes what people chose to believe in without their
consent. Forks should be hard, very hard. And both sides should recognize
that belief in the value of Bitcoin might be a fragile thing. I'd argue
that if we didn't force through a 20MB fork now, and we ran into major
network difficulties a year from now and had no other technical solutions,
that maybe we would get nearly universal agreement, and the businesses and
users that were driven away by the unusable system would be a short term
loss in value considerably smaller than the impairment we risk by forcing a
change.
On Thu, May 7, 2015 at 10:52 AM, Gavin Andresen <gavinandresen@gmail.com>
wrote:
> For reference: the blog post that (re)-started this debate, and which
> links to individual issues, is here:
> http://gavinandresen.ninja/time-to-roll-out-bigger-blocks
>
> In it, I asked people to email me objections I might have missed. I would
> still appreciate it if people do that; it is impossible to keep up with
> this mailing list, /r/bitcoin posts and comments, and #bitcoin-wizards and
> also have time to respond thoughtfully to the objections raised.
>
> I would very much like to find some concrete course of action that we can
> come to consensus on. Some compromise so we can tell entrepreneurs "THIS is
> how much transaction volume the main Bitcoin blockchain will be able to
> support over the next eleven years."
>
> I've been pretty clear on what I think is a reasonable compromise (a
> one-time increase scheduled for early next year), and I have tried to
> explain why I think it it is the right set of tradeoffs.
>
> There ARE tradeoffs here, and the hard question is what process do we use
> to decide those tradeoffs? How do we come to consensus? Is it worth my
> time to spend hours responding thoughtfully to every new objection raised
> here, or will the same thing happen that happened last year and the year
> before-- everybody eventually gets tired of arguing
> angels-dancing-on-the-head-of-a-pin, and we're left with the status quo?
>
> I AM considering contributing some version of the bigger blocksize-limit
> hard-fork patch to the Bitcoin-Xt fork (probably "target a hobbyist with a
> fast Internet connection, and assume Nelson's law to increase over time),
> and then encouraging merchants and exchanges and web wallets and
> individuals who think it strikes a reasonable balance to run it.
>
> And then, assuming it became a super-majority of nodes on the network,
> encourage miners to roll out a soft-fork to start producing bigger blocks
> and eventually trigger the hard fork.
>
> Because ultimately consensus comes down to what software people choose to
> run.
>
> --
> --
> Gavin Andresen
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--f46d043be0ee3d728005157f3a85
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">That strikes me as a dangerous path forward.<div><br></div=
><div>I don't actually think there is anything wrong with this: "<=
span style=3D"font-size:12.8000001907349px">everybody eventually gets tired=
of arguing angels-dancing-on-the-head-of-</span><span style=3D"font-size:1=
2.8000001907349px">a-pin, and we're left with the status quo"</spa=
n></div><div><span style=3D"font-size:12.8000001907349px"><br></span></div>=
<div><span style=3D"font-size:12.8000001907349px">What gives Bitcoin value =
aren't its technical merits but the fact that people believe in it. =C2=
=A0 The biggest risk here isn't that 20MB blocks will be bad or that 1M=
B blocks will be bad, but that by forcing a hard fork that isn't nearly=
universally agreed upon, we will be damaging that belief. =C2=A0 If I stro=
ngly believed some hard fork would be better for Bitcoin, say permanent inf=
lation of 1% a year to fund mining, and I managed to convince 80% of users,=
miners, businesses and developers to go along with me, I would still vote =
against doing it.=C2=A0 Because that's not nearly universal agreement, =
and it changes what people chose to believe in without their consent. Forks=
should be hard, very hard.=C2=A0 And both sides should recognize that beli=
ef in the value of Bitcoin might be a fragile thing. =C2=A0 I'd argue t=
hat if we didn't force through a 20MB fork now, and we ran into major n=
etwork difficulties a year from now and had no other technical solutions, t=
hat maybe we would get nearly universal agreement, and the businesses and u=
sers that were driven away by the unusable system would be a short term los=
s in value considerably smaller than the impairment we risk by forcing a ch=
ange.</span></div><div><span style=3D"font-size:12.8000001907349px"><br></s=
pan></div><div><span style=3D"font-size:12.8000001907349px"><br></span></di=
v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, M=
ay 7, 2015 at 10:52 AM, Gavin Andresen <span dir=3D"ltr"><<a href=3D"mai=
lto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@gmail.com</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"><div dir=3D"ltr"><div c=
lass=3D"gmail_extra">For reference: the blog post that (re)-started this de=
bate, and which links to individual issues, is here:</div><div class=3D"gma=
il_extra">=C2=A0=C2=A0<a href=3D"http://gavinandresen.ninja/time-to-roll-ou=
t-bigger-blocks" target=3D"_blank">http://gavinandresen.ninja/time-to-roll-=
out-bigger-blocks</a></div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">In it, I asked people to email me objections I might have =
missed. I would still appreciate it if people do that; it is impossible to =
keep up with this mailing list, /r/bitcoin posts and comments, and #bitcoin=
-wizards and also have time to respond thoughtfully to the objections raise=
d.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I w=
ould very much like to find some concrete course of action that we can come=
to consensus on. Some compromise so we can tell entrepreneurs "THIS i=
s how much transaction volume the main Bitcoin blockchain will be able to s=
upport over the next eleven years."<br><br>I've been pretty clear =
on what I think is a reasonable compromise (a one-time increase scheduled f=
or early next year), and I have tried to explain why I think it it is the r=
ight set of tradeoffs.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">There ARE tradeoffs here, and the hard question is what pr=
ocess do we use to decide those tradeoffs?=C2=A0 How do we come to consensu=
s? Is it worth my time to spend hours responding thoughtfully to every new =
objection raised here, or will the same thing happen that happened last yea=
r and the year before-- everybody eventually gets tired of arguing angels-d=
ancing-on-the-head-of-a-pin, and we're left with the status quo?</div><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I AM conside=
ring contributing some version of the bigger blocksize-limit hard-fork patc=
h to the Bitcoin-Xt fork (probably =C2=A0"target a hobbyist with a fas=
t Internet connection, and assume Nelson's law to increase over time), =
and then encouraging merchants and exchanges and web wallets and individual=
s who think it strikes a reasonable balance to run it.</div><div class=3D"g=
mail_extra"><br></div><div class=3D"gmail_extra">And then, assuming it beca=
me a super-majority of nodes on the network, encourage miners to roll out a=
soft-fork to start producing bigger blocks and eventually trigger the hard=
fork.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"=
>Because ultimately consensus comes down to what software people choose to =
run.</div><span class=3D"HOEnZb"><font color=3D"#888888"><div class=3D"gmai=
l_extra"><div><br></div>-- <br><div>--<br>Gavin Andresen<br></div><div><br>=
</div>
</div></font></span></div>
<br>-----------------------------------------------------------------------=
-------<br>
One dashboard for servers and applications across Physical-Virtual-Cloud<br=
>
Widest out-of-the-box monitoring support with 50+ applications<br>
Performance metrics, stats and reports that give you Actionable Insights<br=
>
Deep dive visibility with transaction tracing using APM Insight.<br>
<a href=3D"http://ad.doubleclick.net/ddm/clk/290420510;117567292;y" target=
=3D"_blank">http://ad.doubleclick.net/ddm/clk/290420510;117567292;y</a><br>=
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@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></blockquote></div><br></div>
--f46d043be0ee3d728005157f3a85--
|
