From: "t. khan" <teekhan42@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP - 'Block75' - New algorithm
Date: Mon, 2 Jan 2017 13:04:37 -0500 [thread overview]
Message-ID: <CAGCNRJoN7u3yvzitH2KSmVty-p0tX9jxWLHPb8uO5CPZmxmoRg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1556 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1915 bytes --]
next reply other threads:[~2017-01-02 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 18:04 t. khan [this message]
2017-01-02 19:01 ` Tom Zander
2017-01-02 19:32 ` t. khan
2017-01-02 20:35 ` Tom Zander
2017-01-02 21:05 ` t. khan
2017-01-02 22:33 ` Tom Zander
2017-01-02 21:19 ` Luke Dashjr
2017-01-02 22:01 ` Tom Zander
2017-01-03 14:28 ` t. khan
2017-02-13 11:21 ` Hampus Sjöberg
2017-01-02 20:04 ` Luke Dashjr
2017-01-02 20:41 ` t. khan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGCNRJoN7u3yvzitH2KSmVty-p0tX9jxWLHPb8uO5CPZmxmoRg@mail.gmail.com \
--to=teekhan42@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox