MIME-Version: 1.0
In-Reply-To: <2273244.fZU5ULDz4l@cherry>
References: <CAGCNRJoN7u3yvzitH2KSmVty-p0tX9jxWLHPb8uO5CPZmxmoRg@mail.gmail.com>
	<2273244.fZU5ULDz4l@cherry>
From: "t. khan" <teekhan42@gmail.com>
Date: Mon, 2 Jan 2017 14:32:24 -0500
Message-ID: <CAGCNRJp71NCxQ3jk4hu-kXF94RiqfeD=AVnxR37TrJ7bDG310w@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=f403045f8ab47f1d270545219c4b
Subject: Re: [bitcoin-dev] BIP - 'Block75' - New algorithm
Precedence: list

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

Math should decide the max block size, not humans (miners in this
case). The goal of Block75 is to manage the max block size without any
human intervention.

Under Block75, miners don't have any direct control but could still choose
to mine smaller blocks (same as now), though doing so would cost them the
fees from transactions they didn't include in their blocks.

A maximum block size is necessary to prevent a single nefarious miner from
creating a ridiculously large block which would break the network.

- t.k.

On Mon, Jan 2, 2017 at 2:01 PM, Tom Zander <tomz@freedommail.ch> wrote:

> On Monday, 2 January 2017 13:04:37 CET t. khan via bitcoin-dev wrote:
> > Thoughts?
>
> This proposal doesn't change the block size, it only changes the maximum
> block size. Which is expected, nothing bad there.
>
> The direct consequence of this, though is that the miners set the maximum
> block size. Because they decide on the actual created block size.
>
> This leads me to the simple question why we can't just give the miners full
> control of the maximum block size directly?
>
> The fact of the matter is that miners have for the full history of Bitcoin
> been able to set the block size, until they hit the 1MB limit.
> And your proposal keeps that property, but why have a maximum in the
> protocol?
> --
> Tom Zander
> Blog: https://zander.github.io
> Vlog: https://vimeo.com/channels/tomscryptochannel
>

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

<div dir=3D"ltr">Math should decide the max block size, not humans (miners =
in this case).=C2=A0The goal of Block75 is to manage the max block size wit=
hout any human intervention.<div><br></div><div>Under Block75, miners don&#=
39;t have any direct control but could still choose to mine smaller blocks =
(same as now), though doing so would cost them the fees from transactions t=
hey didn&#39;t include in their blocks.</div><div><div><br></div><div>A max=
imum block size is necessary to prevent a single nefarious miner from creat=
ing a ridiculously large block which would break the network.</div><div><br=
></div><div>- t.k.<br><div><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Mon, Jan 2, 2017 at 2:01 PM, Tom Zander <span dir=3D"ltr">&lt;=
<a href=3D"mailto:tomz@freedommail.ch" target=3D"_blank">tomz@freedommail.c=
h</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204=
);border-left-style:solid;padding-left:1ex">On Monday, 2 January 2017 13:04=
:37 CET t. khan via bitcoin-dev wrote:<br>
&gt; Thoughts?<br>
<br>
This proposal doesn&#39;t change the block size, it only changes the maximu=
m<br>
block size. Which is expected, nothing bad there.<br>
<br>
The direct consequence of this, though is that the miners set the maximum<b=
r>
block size. Because they decide on the actual created block size.<br>
<br>
This leads me to the simple question why we can&#39;t just give the miners =
full<br>
control of the maximum block size directly?<br>
<br>
The fact of the matter is that miners have for the full history of Bitcoin<=
br>
been able to set the block size, until they hit the 1MB limit.<br>
And your proposal keeps that property, but why have a maximum in the<br>
protocol?<br>
<span class=3D"gmail-HOEnZb"><font color=3D"#888888">--<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></blockquote></div><br></div></div></div></div></div>

--f403045f8ab47f1d270545219c4b--