From: Marcel Jamin <marcel@jamin•net>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Yet another blocklimit proposal / compromise
Date: Wed, 9 Sep 2015 09:55:44 +0200 [thread overview]
Message-ID: <CAAUq485B5AoTpRBzf0=KFm-k58Zoz+ns-Y7BXc3JwG87VsDo+g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1372 bytes --]
I propose to:
a) assess what blocklimit is currently technically possible without driving
up costs of running a node up too much. Most systems currently running a
fullnode probably have some capacity left.
b) set the determined blocklimit at the next reward halving
c) then double the blocksize limit at every halving thereafter up to a
hardlimit of 8GB.
Reasoning:
Doubling every four years will stay within expected technological growth.
Cisco's VNI forecast predicts a 2.1-fold increase in global average fixed
broadand speed from 2014 to 2019. Nielsen's law, which looks more at the
power user (probably more fitting) is even more optimistic with +50% per
year.
This proposal can be considered a compromise between Pieter's and Gavin's
proposals. While the growth rate is more or less what Pieter proposes, it
includes an initial increase to kickstart the growth. If we start with 8MB,
which seems to be popular among miners, we would reach 8GB in 2056 (as
opposed to 2036 in BIP101). The start date (ca. mid 2016) is also a
compromise between Pieter's 01/2017 and Gavin's 01/2016.
It's simple, predictable and IMHO elegant -- block subsidy halves,
blocksize limit doubles.
It might make sense to update the limit more often in between, though.
Either completely linearly based on a block's timestamp like in BIP101, or
for example for each difficulty period.
[-- Attachment #2: Type: text/html, Size: 1648 bytes --]
next reply other threads:[~2015-09-09 7:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 7:55 Marcel Jamin [this message]
2015-09-09 18:51 ` Jorge Timón
2015-09-09 19:00 ` Marcel Jamin
2015-09-11 16:22 ` Jorge Timón
2015-09-11 16:47 ` Adam Back
2015-09-11 17:54 ` Marcel Jamin
2015-09-11 18:17 ` Jorge Timón
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='CAAUq485B5AoTpRBzf0=KFm-k58Zoz+ns-Y7BXc3JwG87VsDo+g@mail.gmail.com' \
--to=marcel@jamin$(echo .)net \
--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