MIME-Version: 1.0
From: Paul Iverson <piverson1024@gmail.com>
Date: Tue, 28 Mar 2017 12:56:49 -0700
Message-ID: <CAAeo5+jSfp5XWj=EYJ_i-XS+=RjxfY-co7+b7iu3Gd=WWHbHzQ@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=f403045f8a86457589054bcfdc9a
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
Precedence: list

--f403045f8a86457589054bcfdc9a
Content-Type: text/plain; charset=UTF-8

Thank you for the proposal Wang Chung!

It is clear that, spam aside, blocks are getting full and we need increase
them soon. What I don't like about your proposal is it forces all node
operators to implicitly accept larger blocks in 2020, even maybe against
their will. 32 MB blocks might result in a loss of decentralization, and it
might be too difficult to coordinate for small blocks before it's too late.


So I think Core can't decide on hard forks like this. It must be left up to
the users. I think only choice is for Core to add a run-time option to
allow node operators to increase block size limit, so that this very
controversial decision is not coming from Core. It must come from the
community.

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

<div dir=3D"ltr">Thank you for the proposal Wang Chung! =C2=A0<div><br></di=
v><div>It is clear that, spam aside, blocks are getting full and we need in=
crease them soon. What I don&#39;t like about your proposal is it forces al=
l node operators to implicitly accept larger blocks in 2020, even maybe aga=
inst their will. 32 MB blocks might result in a loss of decentralization, a=
nd it might be too difficult to coordinate for small blocks before it&#39;s=
 too late. =C2=A0</div><div><br></div><div>So I think Core can&#39;t decide=
 on hard forks like this. It must be left up to the users. I think only cho=
ice is for Core to add a run-time option to allow node operators to increas=
e block size limit, so that this very controversial decision is not coming =
from Core. It must come from the community. =C2=A0</div><div><br></div></di=
v>

--f403045f8a86457589054bcfdc9a--