Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqOON-0003gS-S8 for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 16:11:19 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.181 as permitted sender) client-ip=209.85.212.181; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f181.google.com; Received: from mail-wi0-f181.google.com ([209.85.212.181]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YqOOM-0006m2-7K for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 16:11:19 +0000 Received: by widdi4 with SMTP id di4so65887965wid.0 for ; Thu, 07 May 2015 09:11:12 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.9.161 with SMTP id a1mr9068474wjb.39.1431015072198; Thu, 07 May 2015 09:11:12 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.194.90.114 with HTTP; Thu, 7 May 2015 09:11:11 -0700 (PDT) In-Reply-To: References: <554A91BE.6060105@bluematt.me> Date: Thu, 7 May 2015 18:11:11 +0200 X-Google-Sender-Auth: eHOao9wbohyfWshNl4vHQy_poG8 Message-ID: From: Mike Hearn To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= Content-Type: multipart/alternative; boundary=047d7b5d34fa0bf6c60515802902 X-Spam-Score: -0.5 (/) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1YqOOM-0006m2-7K Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Block Size Increase X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 May 2015 16:11:19 -0000 --047d7b5d34fa0bf6c60515802902 Content-Type: text/plain; charset=UTF-8 > > It is an argument against my admittedly vague definition of > "non-controversial change". > If it's an argument against something you said, it's not a straw man, right ;) Consensus has to be defined as agreement between a group of people. Who are those people? If you don't know, it's impossible to decide when there is consensus or not. Right now there is this nice warm fuzzy notion that decisions in Bitcoin Core are made by consensus. "Controversial" changes are avoided. I am trying to show you that this is just marketing. Nobody can define what these terms even mean. It would be more accurate to say decisions are vetoed by whoever shows up and complains enough, regardless of technical merit. After all, my own getutxo change was merged after a lot of technical debate (and trolling) ..... then unmerged a day later because "it's a shitstorm". So if Gavin showed up and complained a lot about side chains or whatever, what you're saying is, oh that's different. We'd ignore him. But when someone else complains about a change they don't like, that's OK. Heck, I could easily come up with a dozen reasons to object to almost any change, if I felt like it. Would I then be considered not a part of the consensus because that'd be convenient? > I'm sure that's not what the proponents of the size increase want, and > I'm not defending 1 MB as a sacred limit or anything, but my question > is "where is the limit for them?" > 20mb is an arbitrary number, just like 1mb. It's good enough to keep the Bitcoin ecosystem operating as it presently does: gentle growth in usage with the technology that exists and is implemented. Gavin has discussed in his blog why he chose 20mb, I think. It's the result of some estimates based on average network/hardware capabilities. Perhaps one day 20mb will not be enough. Perhaps then the limit will be raised again, if there is sufficient demand. You are correct that "no limit at all" is a possible answer. More precisely, in that case miners would choose. Gavin's original proposal was 20mb+X where X is decided by some incrementing formula over time, chosen to approximate expected improvements in hardware and software. That was cool too. The 20mb figure and the formula were an attempt to address the concerns of people who are worried about the block size increase: a meet-in-the-middle compromise. Unfortunately it's hard to know what other kinds of meet-in-the-middle compromise could be made here. I'm sure Gavin would consider them if he knew. But the concerns provided are too vague to address. There are no numbers in them, for example: - We need more research -> how much more? - I'm not against changing the size, just not now -> then when? - I'm not wedded to 1mb, but not sure 20mb is right -> then what? - Full node count is going down -> then what size do you think would fix that? 100kb? - It will make mining more centralised -> how do you measure that and how much centralisation would you accept? and so on. --047d7b5d34fa0bf6c60515802902 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It is an argument against my admittedly vague de= finition of
"non-controversial change".

I= f it's an argument against something you said, it's not a straw man= , right ;)

Consensus has to be defined as agreemen= t between a group of people. Who are those people? If you don't know, i= t's impossible to decide when there is consensus or not.

=
Right now there is this nice warm fuzzy notion that decisions in= Bitcoin Core are made by consensus. "Controversial" changes are = avoided. I am trying to show you that this is just marketing. Nobody can de= fine what these terms even mean. It would be more accurate to say decisions= are vetoed by whoever shows up and complains enough, regardless of technic= al merit. After all, my own getutxo change was merged after a lot of techni= cal debate (and trolling) ..... then unmerged a day later because "it&= #39;s a shitstorm".

So if Gavin showed up and= complained a lot about side chains or whatever, what you're saying is,= oh that's different. We'd ignore him. But when someone else compla= ins about a change they don't like, that's OK.

=
Heck, I could easily come up with a dozen reasons to object to almost = any change, if I felt like it. Would I then be considered not a part of the= consensus because that'd be convenient?
=C2=A0
I'm sure that's not what the proponents of t= he size increase want, and
I'm not defending 1 MB as a sacred limit=C2=A0 or anything, but my ques= tion
is "where is the limit for them?"

=
20mb is an arbitrary number, just like 1mb. It's good enough to ke= ep the Bitcoin ecosystem operating as it presently does: gentle growth in u= sage with the technology that exists and is implemented. Gavin has discusse= d in his blog why he chose 20mb, I think. It's the result of some estim= ates based on average network/hardware capabilities.

Perhaps one day 20mb will not be enough. Perhaps then the limit will be = raised again, if there is sufficient demand.

You a= re correct that "no limit at all" is a possible answer. More prec= isely, in that case miners would choose. Gavin's original proposal was = 20mb+X where X is decided by some incrementing formula over time, chosen to= approximate expected improvements in hardware and software. That was cool = too. The 20mb figure and the formula were an attempt to address the concern= s of people who are worried about the block size increase: =C2=A0a meet-in-= the-middle compromise.

Unfortunately it's hard= to know what other kinds of meet-in-the-middle compromise could be made he= re. I'm sure Gavin would consider them if he knew. But the concerns pro= vided are too vague to address. There are no numbers in them, for example:<= /div>
  • We need more research -> how much more?
  • I'= m not against changing the size, just not now -> then when?
  • I= 9;m not wedded to 1mb, but not sure 20mb is right -> then what?
  • = Full node count is going down -> then what size do you think would fix t= hat? 100kb?
  • It will make mining more centralised -> how do you m= easure that and how much centralisation would you accept?
and= so on.
--047d7b5d34fa0bf6c60515802902--