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
|
Return-Path: <me@ricmoo.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D4B2DBC2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 30 Jun 2015 16:03:31 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com
[209.85.223.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6D7C219E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 30 Jun 2015 16:03:05 +0000 (UTC)
Received: by iebmu5 with SMTP id mu5so15561905ieb.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 30 Jun 2015 09:03:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ricmoo.com; s=google;
h=content-type:mime-version:subject:from:in-reply-to:date:cc
:message-id:references:to;
bh=e/NIbklC/nY1+Gc6MKjiaiv4W4raUfl6i7FnwC9TlZk=;
b=gcsaZ+hX3O1Uln+f+L68y9lKZAa351edLEAMvDV6sLKBoi6UKPIily0yd0BE3E3ll8
uu1R5DwY3CbgVIJUZrjJggqTBx6YcLaDpHl25cq18c5mbIs/s7Th3lg8GMjJSr4J4ozN
TJsQ56OzvXnv3WvDtDOnJE36jfURf+rIwdaes=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:content-type:mime-version:subject:from
:in-reply-to:date:cc:message-id:references:to;
bh=e/NIbklC/nY1+Gc6MKjiaiv4W4raUfl6i7FnwC9TlZk=;
b=CynPzXeQzkEkjbyOzKAkLf6g9sV42XZyVjO0yUcpCrEFeC0S929cSCRUTNarE7BzVd
9q4ILlFQor/+ZfksEnhoP53avB8m6oV5I0C1iw2msE8l6SJTBo2ZJLKKsRZdd9Y4uLRx
TEzrJH9uXkSDLi19U3w6bEbM5qtbZrrCva9LRSV+fx42I+A8aiOWUHIx1Qf3f/mem/Nm
ZvptW6ml9Sp1KAZ7iG5ga/weFMrXj2gJJiqWgzqZntBR2Tbs7gb4tzXjHAGtZImnhij2
ZSVICMImjn5TK3U+hOHJkhxLi8AqIdJms6dkthcd/aZtaXR5ORfVJqg7JgWSOxKFmtXD
Dkrg==
X-Gm-Message-State: ALoCoQmRwfgBC0e3yJclh1/0aPReYBmLHXUddJv3dAHUbSCaAo3uFBpIwysGxxJQlJurCtgJFeb7
X-Received: by 10.50.7.68 with SMTP id h4mr26358474iga.40.1435680184757;
Tue, 30 Jun 2015 09:03:04 -0700 (PDT)
Received: from [192.168.2.79] (65-110-212-240.cpe.pppoe.ca. [65.110.212.240])
by mx.google.com with ESMTPSA id h7sm8013417igt.3.2015.06.30.09.03.02
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Tue, 30 Jun 2015 09:03:02 -0700 (PDT)
Content-Type: multipart/alternative;
boundary="Apple-Mail=_60150D31-74EB-44BB-B11E-A92CEB2FF2CF"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
From: Richard Moore <me@ricmoo.com>
In-Reply-To: <CALgxB7uvtKCNM-nH+aqqPa4KNf5O6Gx4GmgZY7Oq8=A24wCrfA@mail.gmail.com>
Date: Tue, 30 Jun 2015 12:03:02 -0400
Message-Id: <8F54D4D6-A2FE-4F20-9927-712187B2B03A@ricmoo.com>
References: <CALgxB7uvtKCNM-nH+aqqPa4KNf5O6Gx4GmgZY7Oq8=A24wCrfA@mail.gmail.com>
To: Michael Naber <mickeybob@gmail.com>
X-Mailer: Apple Mail (2.2098)
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE,
RCVD_IN_DNSWL_LOW autolearn=unavailable version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Block size increase oppositionists: please
clearly define what you need done to increase block size to a
static 8MB, and help do it
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: Tue, 30 Jun 2015 16:03:31 -0000
--Apple-Mail=_60150D31-74EB-44BB-B11E-A92CEB2FF2CF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
I=E2=80=99m not planning to take a firm stance against or for, but one =
problem with your analogy is that airplanes [currently] are not elastic =
(until we get TARDIS technology, or semi-TARDIS-like technology); they =
take up space and resources proportional to their capacity.
It is not the block size that is increasing, it is the *maximum* block =
size=E2=80=A6 So, it=E2=80=99s more like saying the *maximum* airplane =
size is increasing, which I think may be somewhat true (although, I =
agree, probably not exponentially). It would be more like an airplane =
whose capacity was doubling every two years, but would shrink when that =
extra capacity was not needed and only consume the maintenance, fuel, et =
cetera needed for its current size.
My semi-firm-ish stance is that kicking the can down the road with a =
static increase is less better. We can always soft-fork the limit down =
if the *actual* block size is growing too fast. When (and/or if) we need =
to. I also think 8MB is a rather large jump, for either static or =
dynamic.
*shrug*
RicMoo
> On Jun 30, 2015, at 11:34 AM, Michael Naber <mickeybob@gmail.com> =
wrote:
>=20
> As you know I'm trying to lobby for a block size increase to a static =
8MB.=20
>=20
> I'm happy to try to get the testing done that people want done for =
this, but I think the real crux of this issue is that we need to get =
consensus that we intend to continually push the block size upward as =
bounded only by technology.
>=20
> Imagine an engineer (Gavin) at Boeing (Bitcoin Core) said he was going =
to build an airplane (block) that was going to move 8x as many people =
(transactions) as today=E2=80=99s planes (blocks), all while costing =
about the same amount to operate. Imagine he then went on to tell you =
that he expects to double the plane=E2=80=99s (block's) capacity every =
two years!=20
>=20
> Without full planes (blocks), will the airlines (miners) go out of =
business, since planes (blocks) will never be full and the cost to add =
people (transactions) to a plane (block) will approach zero? Probably =
not. Airlines (miners) still have to pay for pilots, security screening =
staff, fuel, etc (engineers, hash rate, electricity, etc) so even if =
their airplanes (blocks) can hold limitless people (transactions), they =
would still have to charge sufficient fees to stay in business.
>=20
> What tests do you need done to move to 8MB? Pitch in and help get =
those tests done; agree that we'll run more tests next year or the year =
after when technology might allow for 16 MB blocks. Do you really want =
to be the guy holding back bigger planes? Do you really want to =
artificially constrain block size below what technology allows?=20
>=20
> In the face of such strong market demand for increased capacity in =
globally aware global consensus, do you really think you can prevent =
supply from meeting demand when the technology exists to deliver it? Do =
you really want to force a fork because you and others won't agree to a =
simple raise to a static 8MB?=20
>=20
> Do what's best for Bitcoin and define what needs to get done to agree =
to a simple block size increase to a static 8MB.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
=
.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=
=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=
=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8><(((=C2=BA>
Richard Moore ~ Founder
Genetic Mistakes Software inc.
phone: (778) 882-6125
email: ricmoo@geneticmistakes.com <mailto:ricmoo@geneticmistakes.com>
www: http://GeneticMistakes.com <http://geneticmistakes.com/>
--Apple-Mail=_60150D31-74EB-44BB-B11E-A92CEB2FF2CF
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""><div class=3D"">I=E2=80=99m not planning to take a firm =
stance against or for, but one problem with your analogy is that =
airplanes [currently] are not elastic (until we get TARDIS technology, =
or semi-TARDIS-like technology); they take up space and resources =
proportional to their capacity.</div><div class=3D""><br =
class=3D""></div><div class=3D"">It is not the block size that is =
increasing, it is the *maximum* block size=E2=80=A6 So, it=E2=80=99s =
more like saying the *maximum* airplane size is increasing, which I =
think may be somewhat true (although, I agree, probably not =
exponentially). It would be more like an airplane whose capacity was =
doubling every two years, but would shrink when that extra capacity was =
not needed and only consume the maintenance, fuel, et cetera needed for =
its current size.</div><div class=3D""><br class=3D""></div><div =
class=3D"">My semi-firm-ish stance is that kicking the can down the road =
with a static increase is less better. We can always soft-fork the limit =
down if the *actual* block size is growing too fast. When (and/or if) we =
need to. I also think 8MB is a rather large jump, for either static or =
dynamic.</div><div class=3D""><br class=3D""></div><div =
class=3D"">*shrug*</div><div class=3D""><br class=3D""></div><div =
class=3D"">RicMoo</div><div class=3D""><br class=3D""></div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Jun 30, 2015, at 11:34 AM, Michael Naber <<a =
href=3D"mailto:mickeybob@gmail.com" class=3D"">mickeybob@gmail.com</a>>=
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D"">As you know I'm trying to lobby for a block size =
increase to a static 8MB. <div class=3D""><br class=3D""></div><div =
class=3D"">I'm happy to try to get the testing done that people want =
done for this, but I think the real crux of this issue is that we need =
to get consensus that we intend to continually push the block size =
upward as bounded only by technology.</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">Imagine an engineer =
(Gavin) at Boeing (Bitcoin Core) said he was going to build an airplane =
(block) that was going to move 8x as many people (transactions) as =
today=E2=80=99s planes (blocks), all while costing about the same amount =
to operate. Imagine he then went on to tell you that he expects to =
double the plane=E2=80=99s (block's) capacity every two =
years! </div><div class=3D""><br class=3D""></div><div =
class=3D"">Without full planes (blocks), will the airlines (miners) go =
out of business, since planes (blocks) will never be full and the cost =
to add people (transactions) to a plane (block) will approach zero? =
Probably not. Airlines (miners) still have to pay for pilots, security =
screening staff, fuel, etc (engineers, hash rate, electricity, etc) so =
even if their airplanes (blocks) can hold limitless people =
(transactions), they would still have to charge sufficient fees to stay =
in business.</div><div class=3D""><br class=3D""></div></div><div =
class=3D"">What tests do you need done to move to 8MB? Pitch in and help =
get those tests done; agree that we'll run more tests next year or the =
year after when technology might allow for 16 MB blocks. Do you really =
want to be the guy holding back bigger planes? Do you really want to =
artificially constrain block size below what technology =
allows? </div><div class=3D""><br class=3D""></div><div class=3D"">In=
the face of such strong market demand for increased capacity in =
globally aware global consensus, do you really think you can prevent =
supply from meeting demand when the technology exists to deliver it? Do =
you really want to force a fork because you and others won't agree to a =
simple raise to a static 8MB? </div><div class=3D""><br =
class=3D""></div><div class=3D"">Do what's best for Bitcoin and define =
what needs to get done to agree to a simple block size increase to a =
static 8MB.</div></div>
_______________________________________________<br class=3D"">bitcoin-dev =
mailing list<br class=3D""><a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
class=3D"">bitcoin-dev@lists.linuxfoundation.org</a><br =
class=3D"">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev<=
br class=3D""></div></blockquote></div><br class=3D""><div =
apple-content-edited=3D"true" class=3D"">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; =
">.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=
=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=
=B8=C2=B8.=C2=B7=C2=B4=C2=AF`=C2=B7.=C2=B8><(((=C2=BA><br =
class=3D""><br class=3D"">Richard Moore ~ Founder<br class=3D"">Genetic =
Mistakes Software inc.<br class=3D"">phone: (778) 882-6125<br =
class=3D"">email: <a href=3D"mailto:ricmoo@geneticmistakes.com" =
class=3D"">ricmoo@geneticmistakes.com</a><br class=3D"">www: <a =
href=3D"http://GeneticMistakes.com/" =
class=3D"">http://GeneticMistakes.com</a></span>
</div>
<br class=3D""></body></html>=
--Apple-Mail=_60150D31-74EB-44BB-B11E-A92CEB2FF2CF--
|
