MIME-Version: 1.0
From: "t. khan" <teekhan42@gmail.com>
Date: Mon, 2 Jan 2017 13:04:37 -0500
Message-ID: <CAGCNRJoN7u3yvzitH2KSmVty-p0tX9jxWLHPb8uO5CPZmxmoRg@mail.gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=f403045e34f48e3bb0054520627f
Subject: [bitcoin-dev] BIP - 'Block75' - New algorithm
Precedence: list

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

Based on feedback from this list and further simulations, here is a new
algorithm for Block75:

new max blocksize = x + (x * (AVERAGE_CAPACITY - TARGET_CAPACITY)

TARGET_CAPACITY = 0.75
AVERAGE_CAPACITY = average percentage full of the last 2016 blocks, as a
decimal
x = current max block size

Please note that this algorithm actually tries to keep blocks 75% full,
unlike the old one that unnecessarily capped growth at 250KB. While this
would theoretically allow a maximum increase of 25% over the previous max
block size, in practice it's not possible to get that high.

This would be calculated every 2016 blocks along with difficulty.

Block75 should maintain transaction fees at about the level they were in
May/June 2016 when blocks started hitting 75% full somewhat consistently.

Thoughts? For any predictions as to how this would behave, please provide
the numbers used to arrive at any conclusions.

Other questions:
1. How do we make Block75 play nice with SegWit?
2. Is there any need for a minimum max blocksize? Block75 allows for
decreasing the size as well as increasing it.

Activation:
To help negate some of the risk associated with a hard fork and to prevent
a single relatively small mining pool from blocking Block75's adoption,
activation would occur once 900 of the last 1,000 blocks mined signaled
support, with a grace period of 4,032 blocks.

Thank you again to all those who commented on the previous Block75 thread.
Together, we can make 2017 the year the block size debate ends (hopefully
forever).

Happy New Year!

- t.k.

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

<div dir=3D"ltr"><div>Based on feedback from this list and further simulati=
ons, here is a new algorithm for Block75:</div><div><br></div>new max block=
size =3D x + (x * (AVERAGE_CAPACITY - TARGET_CAPACITY)<div><br></div><div><=
div>TARGET_CAPACITY =3D 0.75</div><div>AVERAGE_CAPACITY =3D average percent=
age full of the last 2016 blocks, as a decimal</div><div>x =3D current max =
block size</div><div><br></div><div>Please note that this algorithm actuall=
y tries to keep blocks 75% full, unlike the old one that unnecessarily capp=
ed growth at 250KB. While this would theoretically allow a maximum increase=
 of 25% over the previous max block size, in practice it&#39;s not possible=
 to get that high.</div><div><br></div><div>This would be calculated every =
2016 blocks along with difficulty.</div><div><br></div><div>Block75 should =
maintain transaction fees at about the level they were in May/June 2016 whe=
n blocks started hitting 75% full somewhat consistently.</div><div><br></di=
v><div>Thoughts? For any predictions as to how this would behave, please pr=
ovide the numbers used to arrive at any conclusions.</div><div><br></div><d=
iv>Other questions:</div><div>1. How do we make Block75 play nice with SegW=
it?<br></div><div>2. Is there any need for a minimum max blocksize? Block75=
 allows for decreasing the size as well as increasing it.</div></div><div><=
br></div><div>Activation:</div><div>To help negate some of the risk associa=
ted with a hard fork and to prevent a single relatively small mining pool f=
rom blocking Block75&#39;s adoption, activation would occur once 900 of the=
 last 1,000 blocks mined signaled support, with a grace period of 4,032 blo=
cks.</div><div><br></div><div>Thank you again to all those who commented on=
 the previous Block75 thread. Together, we can make 2017 the year the block=
 size debate ends (hopefully forever).</div><div><br></div><div>Happy New Y=
ear!</div><div><br></div><div>- t.k.</div></div>

--f403045e34f48e3bb0054520627f--