From: Erik Aronesty <erik@q32•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] BIP103 to 30MB
Date: Wed, 30 Aug 2017 13:14:22 -0400 [thread overview]
Message-ID: <CAJowKgLwAjR9VqzvmR3wsy_p6-F4Mp1X6PUibgpnHUXVA9uUhQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 409 bytes --]
If you use this formula, with a decaying percentage, it takes about 100
years to get to 30MB, but never goes past that.
Since it never passes 32, we don't have to worry about going past that
ever... unless another hard fork is done. A schedule like this could
allow block size to scale with tech growth asymptotically. Might be nice
to include with other things
P=17%, Pn = P*0.95 X = 1, Xn = X * (1+P)
[-- Attachment #2: Type: text/html, Size: 724 bytes --]
reply other threads:[~2017-08-30 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJowKgLwAjR9VqzvmR3wsy_p6-F4Mp1X6PUibgpnHUXVA9uUhQ@mail.gmail.com \
--to=erik@q32$(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