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
|
Return-Path: <pieter.wuille@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 58388AAE
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 14:09:20 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com
[209.85.214.179])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6C095147
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 14:09:19 +0000 (UTC)
Received: by obpn3 with SMTP id n3so67450681obp.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 26 Jun 2015 07:09:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=hKMz2xN/QZQw/vKePDjdAHmcCB4YwbKTEwO+moUnskc=;
b=cGKqGKFQ+6/QMT2oHqTU5S7uhy4twRrYo6AHYHXG5pvcNzIOPOKGPcJFnNEMUhw4Zr
kK2cuofWH+Zx1dh/nSkCa9m2vG7Wi+Bz3uSAEp8GV2jIUTg83izE+0Tt2XZ7j8hRqy0c
Th6a07cK1mWbrjcGFnwQnVMSfBL/gPqcJNgf5DA1HiLmubmVylsWUZfy3X25yi+og2A7
hlEzvp1SoadBb9GHB9zpdX+wd6aSXxSZDmQSp0+WT6DrYJcuvQBtg30HdBj0eojqOYQP
LRHTGkugN55i44v23OBEHtnGGfNFGmyGHa5zIjzE9oyxt9nSpOnJzVwox53/LCsQ8Q8j
xRZw==
MIME-Version: 1.0
X-Received: by 10.202.194.9 with SMTP id s9mr1590709oif.39.1435327758727; Fri,
26 Jun 2015 07:09:18 -0700 (PDT)
Received: by 10.182.33.137 with HTTP; Fri, 26 Jun 2015 07:09:18 -0700 (PDT)
Date: Fri, 26 Jun 2015 16:09:18 +0200
Message-ID: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=001a113dc33431ff6805196c4975
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_20,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
Subject: [bitcoin-dev] The need for larger blocks
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: Fri, 26 Jun 2015 14:09:20 -0000
--001a113dc33431ff6805196c4975
Content-Type: text/plain; charset=UTF-8
Hello all,
here I'm going to try to address a part of the block size debate which has
been troubling me since the beginning: the reason why people seem to want
it.
People say that larger blocks are necessary. In the long term, I agree - in
the sense that systems that do not evolve tend to be replaced by other
systems. This evolution can come in terms of layers on top of Bitcoin's
blockchain, in terms of the technology underlying various aspects of the
blockchain itself, and also in the scale that this technology supports.
I do, however, fundamentally disagree that a fear for a change in economics
should be considered to necessitate larger blocks. If it is, and there is
consensus that we should adapt to it, then there is effectively no limit
going forward. This is similar to how Congress voting to increase the
copyright term retroactively from time to time is really no different from
having an infinite copyright term in the first place. This scares me.
Here is how Gavin summarizes the future without increasing block sizes in
PR 6341:
> 1. Transaction confirmation times for transactions with a given fee will
rise; very-low-fee transactions will fail to get confirmed at all.
> 2. Average transaction fee paid will rise
> 3. People or applications unwilling or unable to pay the rising fees will
stop submitting transactions
> 4. People and businesses will shelve plans to use Bitcoin, stunting
growth and adoption
Is it fair to summarize this as "Some use cases won't fit any more, people
will decide to no longer use the blockchain for these purposes, and the
fees will adapt."?
I think that is already happening, and will happen at any scale. I believe
demand for payments in general is nearly infinite, and only a small portion
of it will eventually fit on a block chain (independent of whether its size
is limited by consensus rules or economic or technological means).
Furthermore, systems that compete with Bitcoin in this space already offer
orders of magnitude more capacity than we can reasonably achieve with any
blockchain technology at this point.
I don't know what subset of use cases Bitcoin will cater to in the long
term. They have already changed - you see way less betting transactions
these days than a few years ago for example - and they will keep changing,
independent of what effective block sizes we end up with. I don't think we
should be afraid of this change or try to stop it.
If you look at graphs of block sizes over time (for example,
http://rusty.ozlabs.org/?p=498), it seems to me that there is very little
"organic" growth, and a lot of sudden changes (which could correspond to
changing defaults in miner software, introduction of popular
sites/services, changes in the economy). I think these can be seen as the
economy changing to full up the available space, and I believe these will
keep happening at any size effectively available.
None of this is a reason why the size can't increase. However, in my
opinion, we should do it because we believe it increases utility and
understand the risks; not because we're afraid of what might happen if we
don't hurry up. And from that point of view, it seems silly to make a huge
increase at once...
--
Pieter
--001a113dc33431ff6805196c4975
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div>Hello all,<br=
><br></div>here I'm
going to try to address a part of the block size debate which has been=20
troubling me since the beginning: the reason why people seem to want it.<br=
><br></div>People
say that larger blocks are necessary. In the long term, I agree - in=20
the sense that systems that do not evolve tend to be replaced by other=20
systems. This evolution can come in terms of layers on top of Bitcoin's=
=20
blockchain, in terms of the technology underlying various aspects of the
blockchain itself, and also in the scale that this technology supports.<br=
><br></div>I
do, however, fundamentally disagree that a fear for a change in=20
economics should be considered to necessitate larger blocks. If it is,=20
and there is consensus that we should adapt to it, then there is=20
effectively no limit going forward. This is similar to how Congress=20
voting to increase the copyright term retroactively from time to time is
really no different from having an infinite copyright term in the first
place. This scares me.<br><br></div>Here is how Gavin summarizes the futur=
e without increasing block sizes in PR 6341:<br><br>> 1. Transaction con=
firmation times for transactions with a given fee=20
will rise; very-low-fee transactions will fail to get confirmed at all.<br>=
> 2. Average transaction fee paid will rise<br>> 3. People or applica=
tions unwilling or unable to pay the rising fees will stop submitting trans=
actions<br>> 4. People and businesses will shelve plans to use Bitcoin, =
stunting growth and adoption<br><br></div>Is
it fair to summarize this as "Some use cases won't fit any more, =
people
will decide to no longer use the blockchain for these purposes, and the
fees will adapt."?<br><br></div>I think that is already happening, an=
d=20
will happen at any scale. I believe demand for payments in general is=20
nearly infinite, and only a small portion of it will eventually fit on a
block chain (independent of whether its size is limited by consensus=20
rules or economic or technological means). Furthermore, systems that=20
compete with Bitcoin in this space already offer orders of magnitude=20
more capacity than we can reasonably achieve with any blockchain=20
technology at this point.<br><br>I don't know what subset of use cases=
=20
Bitcoin will cater to in the long term. They have already changed - you=20
see way less betting transactions these days than a few years ago for=20
example - and they will keep changing, independent of what effective=20
block sizes we end up with. I don't think we should be afraid of this=
=20
change or try to stop it.<br><br></div>If you look at graphs of block sizes=
over time (for example, <a href=3D"http://rusty.ozlabs.org/?p=3D498" targe=
t=3D"_blank">http://rusty.ozlabs.org/?p=3D498</a>),
it seems to me that there is very little "organic" growth, and a=
lot of
sudden changes (which could correspond to changing defaults in miner=20
software, introduction of popular sites/services, changes in the=20
economy). I think these can be seen as the economy changing to full up=20
the available space, and I believe these will keep happening at any size
effectively available.<br><br></div>None of this is a reason why the=20
size can't increase. However, in my opinion, we should do it because we=
=20
believe it increases utility and understand the risks; not because we'r=
e
afraid of what might happen if we don't hurry up. And from that point=
=20
of view, it seems silly to make a huge increase at once...<br><br>-- <br></=
div>Pieter<br><br></div>
--001a113dc33431ff6805196c4975--
|
