Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.171 as permitted sender)
	client-ip=209.85.212.171; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f171.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <554BA032.4040405@bluematt.me>
References: <554A91BE.6060105@bluematt.me>
	<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
	<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
	<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
	<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
	<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
	<CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>
	<554BA032.4040405@bluematt.me>
Date: Thu, 7 May 2015 19:43:30 +0200
Message-ID: <CANEZrP3yM9wsSPNgpOsXDk-DjUy5PW2XuRTvK2AyCNbVJ5hZHw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matt Corallo <bitcoin-list@bluematt.me>
Content-Type: multipart/alternative; boundary=047d7ba9791c24d7990515817337
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
Precedence: list

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

> The only answer to this that anyone with a clue should give is "it
> will very, very likely be able to support at least 1MB blocks roughly
> every 10 minutes on average for the next eleven years, and it seems
> likely that a block size increase of some form will happen at some point in
> the next eleven years", anything else is dishonest.


Matt, you know better than that. Gavin neither lacks clue nor is he
dishonest.

He has been working on the assumption that other developers are reasonable,
and some kind of compromise solution can be found that everyone can live
with. Hence trying to find a middle ground, hence considering and writing
articles in response to every single objection raised. Hence asking for
suggestions on what to change about the plan, to make it more acceptable.
What more do you want, exactly?

And I'll ask again. Do you have a *specific, credible alternative*? Because
so far I'm not seeing one.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">The=C2=A0only answer to t=
his that anyone with a clue should give is &quot;it will=C2=A0very, very li=
kely be able to support at least 1MB blocks roughly every=C2=A010 minutes o=
n average for the next eleven years, and it seems likely=C2=A0that a block =
size increase of some form will happen at some point in the=C2=A0next eleve=
n years&quot;, anything else is dishonest.</blockquote></div></div><div cla=
ss=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Matt, you know bett=
er than that. Gavin neither lacks clue nor is he dishonest.=C2=A0</div><div=
 class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">He has been wor=
king on the assumption that other developers are reasonable, and some kind =
of compromise solution can be found that everyone can live with. Hence tryi=
ng to find a middle ground, hence considering and writing articles in respo=
nse to every single objection raised. Hence asking for suggestions on what =
to change about the plan, to make it more acceptable. What more do you want=
, exactly?</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_ex=
tra">And I&#39;ll ask again. Do you have a <b>specific, credible alternativ=
e</b>? Because so far I&#39;m not seeing one.</div></div>

--047d7ba9791c24d7990515817337--