summaryrefslogtreecommitdiff
path: root/0b/772780679e4c3abfb7b76df6c71703f1a3d6f6
blob: 67e7ae35428adf067166d31cf357dce3a813216c (plain)
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
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 9D6ED8AD
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  6 Aug 2015 14:06:07 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f170.google.com (mail-ig0-f170.google.com
	[209.85.213.170])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C49B312A
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu,  6 Aug 2015 14:06:04 +0000 (UTC)
Received: by iggf3 with SMTP id f3so11962637igg.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 06 Aug 2015 07:06:03 -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=74rwTrybUDG7nyHWvLsdruyT65VgbMxoMrsMG2S39Jw=;
	b=bEnUmzlrlCuC0yYqQgg29QOj+XhYOxJU1eeiXaZ1XXLHevkUJePbHbGCHy+NPtRLgj
	6YsSJHbfO71jrg7Qw/1qGiOTX+5Y7GREScYkbHRFYl9ZN+PZ/HtzZyEyO/+3xneS8roP
	iqw0tv3Js4ga/f2SkUvlQMM8LWbk+thmkmdbxLVHQnOTKjwM5bMLXih3HHvORuv7czN5
	EXgCcoML8QAcYxnb6IO6t1w+rBkVZEyFEvcSK158pp0ShV+Cs0XERexOOoRe34lfr5jZ
	f90Jvt+nFEuQJ53d6WMpun1n7NOtxA+AOuE+N/MtgrOz9Dg0FrfocbCIuSwfxWP3fPvn
	cAJQ==
MIME-Version: 1.0
X-Received: by 10.50.134.226 with SMTP id pn2mr4064707igb.21.1438869963648;
	Thu, 06 Aug 2015 07:06:03 -0700 (PDT)
Received: by 10.36.77.201 with HTTP; Thu, 6 Aug 2015 07:06:03 -0700 (PDT)
In-Reply-To: <CABsx9T22KUcbRb4ZfRDikbxK05pqWY1=uvYo10toWA-JwGa-PQ@mail.gmail.com>
References: <CAPg+sBj-wA1DMrwkQRWnzQoB5NR-q=2-5=WDAAUYfSpXRZSTqw@mail.gmail.com>
	<CABsx9T1NqBX9Tr8vRCtCeri76e0wrtkvRhEPyG9Advv_3Uqxng@mail.gmail.com>
	<CAPg+sBjwVxYTOn3+bwahHGSGpBh5BCh5b4OOFkw_2x97YZSFPQ@mail.gmail.com>
	<CA+w+GKS_wDDgf=HjPgD5QZ_wdTRg7i_oYUgBRmh9HpufETAP=w@mail.gmail.com>
	<CABm2gDqvpWdHdjo1OBzbw-6ivu5DEGcfvK8duc3-KAjsSeWapA@mail.gmail.com>
	<CA+w+GKRPPcgCO0pBP2PjKGU49tWuBoF1vRJzY+4fWn71HOVDPw@mail.gmail.com>
	<CABm2gDqV1NdHJZBmUWX3AxVYy6ErU7AB-wsWgGzbiTL1twdq6g@mail.gmail.com>
	<CA+w+GKTLBWj6b4ppwrmnXb_gybYFcrX7haLBSdCnMaijy2An4w@mail.gmail.com>
	<CABm2gDpWPhYNh=g-ZXCsfe-aPq=N6NKSWKP9kr-KtPVrWAxB7Q@mail.gmail.com>
	<CAAO2FKHsczkwwqO87cJFtxBp9JE=vf=GcxLx37GpRUkPq8VGHQ@mail.gmail.com>
	<CABm2gDpp5+hkHmd6op6PPW658siKoEMRDfTWiEHHM7vJSLDhyA@mail.gmail.com>
	<CA+BnGuFNOjzLaiPPnUSi-rkU94UMgmP30Si8N3oBSYG0q8j-_w@mail.gmail.com>
	<CABm2gDoNbhc1=kgc0F+wSm33hTmRmmptk-XcaZxsm=6iJkWu=w@mail.gmail.com>
	<CABsx9T22KUcbRb4ZfRDikbxK05pqWY1=uvYo10toWA-JwGa-PQ@mail.gmail.com>
Date: Thu, 6 Aug 2015 16:06:03 +0200
Message-ID: <CAPg+sBg-KN5=A5_Fx3fo0dcD6mAdMUXBMNzW52SkQsRbADTmSg@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b2e148d0fb531051ca5055e
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] Block size following technological growth
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: Thu, 06 Aug 2015 14:06:07 -0000

--047d7b2e148d0fb531051ca5055e
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 6, 2015 at 3:40 PM, Gavin Andresen via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On Wed, Aug 5, 2015 at 9:26 PM, Jorge Tim=C3=B3n <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> This is a much more reasonable position. I wish this had been starting
>> point of this discussion instead of "the block size limit must be
>> increased as soon as possible or bitcoin will fail".
>>
>
> It REALLY doesn't help the debate when you say patently false statements
> like that.
>
> My first blog post on this issue is here:
>   http://gavinandresen.ninja/why-increasing-the-max-block-size-is-urgent
>
> ... and I NEVER say "Bitcoin will fail".  I say:
>
> "If the number of transactions waiting gets large enough, the end result
> will be an over-saturated network, busy doing nothing productive. I don=
=E2=80=99t
> think that is likely=E2=80=93 it is more likely people just stop using Bi=
tcoin
> because transaction confirmation becomes increasingly unreliable."
>

But you seem to consider that a bad thing. Maybe saying that you're
claiming that this equals Bitcoin failing is an exaggeration, but you do
believe that evolving towards an ecosystem where there is competition for
block space is a bad thing, right?

I don't agree that "Not everyone is able to use the block chain for every
use case" is the same thing as "People stop using Bitcoin". People are
already not using it for every use case.

Here is what my proposed BIP says: "No hard forking change that relaxes the
block size limit can be guaranteed to provide enough space for every
possible demand - or even any particular demand - unless strong
centralization of the mining ecosystem is expected. Because of that, the
development of a fee market and the evolution towards an ecosystem that is
able to cope with block space competition should be considered healthy."

--=20
Pieter

--047d7b2e148d0fb531051ca5055e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Aug 6, 2015 at 3:40 PM, Gavin Andresen via bitcoin=
-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundat=
ion.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</s=
pan> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><span =
class=3D""><div class=3D"gmail_quote">On Wed, Aug 5, 2015 at 9:26 PM, Jorge=
 Tim=C3=B3n <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linux=
foundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</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 style=3D"overflow=
:hidden">This is a much more reasonable position. I wish this had been star=
ting<br>
point of this discussion instead of &quot;the block size limit must be<br>
increased as soon as possible or bitcoin will fail&quot;.</div></blockquote=
></div><br></span>It REALLY doesn&#39;t help the debate when you say patent=
ly false statements like that.</div><div class=3D"gmail_extra"><br></div><d=
iv class=3D"gmail_extra">My first blog post on this issue is here:</div><di=
v class=3D"gmail_extra">=C2=A0=C2=A0<a href=3D"http://gavinandresen.ninja/w=
hy-increasing-the-max-block-size-is-urgent" target=3D"_blank">http://gavina=
ndresen.ninja/why-increasing-the-max-block-size-is-urgent</a></div><div cla=
ss=3D"gmail_extra"><br></div><div class=3D"gmail_extra">... and I NEVER say=
 &quot;Bitcoin will fail&quot;.=C2=A0 I say:</div><br>&quot;If the number o=
f transactions waiting gets large enough, the end result will be an over-sa=
turated network, busy doing nothing productive. I don=E2=80=99t think that =
is likely=E2=80=93 it is more likely people just stop using Bitcoin because=
 transaction confirmation becomes increasingly unreliable.&quot;<br></div><=
/blockquote><div><br></div><div>But you seem to consider that a bad thing. =
Maybe saying that you&#39;re claiming that this equals Bitcoin failing is a=
n exaggeration, but you do believe that evolving towards an ecosystem where=
 there is competition for block space is a bad thing, right?<br><br></div><=
div>I don&#39;t agree that &quot;Not everyone is able to use the block chai=
n for every use case&quot; is the same thing as &quot;People stop using Bit=
coin&quot;. People are already not using it for every use case.<br></div><d=
iv><br></div><div>Here is what my proposed BIP says: &quot;No hard forking =
change that relaxes the block size limit can be=20
guaranteed to provide enough space for every possible demand - or even=20
any particular demand - unless strong centralization of the mining=20
ecosystem is expected. Because of that, the development of a fee market=20
and the evolution towards an ecosystem that is able to cope with block=20
space competition should be considered healthy.&quot;<br><br>-- <br></div><=
div>Pieter<br><br> </div></div></div></div>

--047d7b2e148d0fb531051ca5055e--