MIME-Version: 1.0
In-Reply-To: <10740865.BWG7G26IGS@cherry>
References: <CAAeo5+jSfp5XWj=EYJ_i-XS+=RjxfY-co7+b7iu3Gd=WWHbHzQ@mail.gmail.com>
	<10740865.BWG7G26IGS@cherry>
From: Alphonse Pace <alp.bitcoin@gmail.com>
Date: Tue, 28 Mar 2017 15:53:30 -0500
Message-ID: <CAMBsKS_Fp79jn_zSyzrcJU01Ri1hUtoVPoDf64mB-uDOEYEQbA@mail.gmail.com>
To: Tom Zander <tomz@freedommail.ch>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=94eb2c1165060d0dbf054bd0a708
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
Precedence: list

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

His demand (not suggestion) allows it without any safeguards.

>This patch must be in the immediate next release of Bitcoin Core.

That is not a suggestion.

Wang - still waiting on the details of this meeting.  In the spirit of
openness, I think you ought to share with the community what kind of secret
meetings are happening.


On Tue, Mar 28, 2017 at 3:43 PM, Tom Zander via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> On Tuesday, 28 March 2017 21:56:49 CEST Paul Iverson via bitcoin-dev wrote:
> > 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.
>
> The suggestion was not to produce 32MB blocks, so your fear here is
> unfounded.
>
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

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

<div dir=3D"ltr">His demand (not suggestion) allows it without any safeguar=
ds.<div><br></div><div>&gt;<span style=3D"font-size:12.8px">This patch must=
 be=C2=A0</span><span style=3D"font-size:12.8px">in the immediate next rele=
ase of Bitcoin Core.</span></div><div><span style=3D"font-size:12.8px"><br>=
</span></div><div><span style=3D"font-size:12.8px">That is not a suggestion=
.</span></div><div><span style=3D"font-size:12.8px"><br>Wang - still waitin=
g on the details of this meeting.=C2=A0 In the spirit of openness, I think =
you ought to share with the community what kind of secret meetings are happ=
ening.</span></div><div><span style=3D"font-size:12.8px"><br></span></div><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Mar =
28, 2017 at 3:43 PM, Tom Zander via bitcoin-dev <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitco=
in-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;padd=
ing-left:1ex"><span class=3D"">On Tuesday, 28 March 2017 21:56:49 CEST Paul=
 Iverson via bitcoin-dev wrote:<br>
&gt; It is clear that, spam aside, blocks are getting full and we need incr=
ease<br>
&gt; them soon. What I don&#39;t like about your proposal is it forces all =
node<br>
&gt; operators to implicitly accept larger blocks in 2020, even maybe again=
st<br>
&gt; their will. 32 MB blocks might result in a loss of decentralization, a=
nd<br>
&gt; it might be too difficult to coordinate for small blocks before it&#39=
;s too<br>
&gt; late.<br>
<br>
</span>The suggestion was not to produce 32MB blocks, so your fear here is<=
br>
unfounded.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Tom Zander<br>
Blog: <a href=3D"https://zander.github.io" rel=3D"noreferrer" target=3D"_bl=
ank">https://zander.github.io</a><br>
Vlog: <a href=3D"https://vimeo.com/channels/tomscryptochannel" rel=3D"noref=
errer" target=3D"_blank">https://vimeo.com/channels/<wbr>tomscryptochannel<=
/a><br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5">_____________________=
_________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
</div></div></blockquote></div><br></div>

--94eb2c1165060d0dbf054bd0a708--