From: jl2012@xbt•hk
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] CORRECTIONS: A summary of block size hardfork proposals
Date: Fri, 31 Jul 2015 03:10:34 +0000 [thread overview]
Message-ID: <20150731031034.Horde.pF0_RVukjyAUe06VAuvqaA1@server47.web-hosting.com> (raw)
In-Reply-To: <20150730181450.Horde.mXJp1wMjXROJvXZ_Vhv2RQ2@server47.web-hosting.com>
I am making some corrections to my previous summary
Currently, there are 4 block size BIP by Bitcoin developers:
BIP100 by Jeff:
http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdf
BIP101 by Gavin:
https://github.com/bitcoin/bips/blob/master/bip-0101.mediawiki
BIP102 by Jeff: https://github.com/bitcoin/bips/pull/173/files
BIP??? by Pieter (called "BIP103" below):
https://gist.github.com/sipa/c65665fc360ca7a176a6
To facilitate further discussion, I'd like to summarize these
proposals by a series of questions. Please correct me if I'm wrong.
Something like sigop limit are less controversial and are not shown.
Should we use a miner voting mechanism to initiate the hardfork?
BIP100: Yes, support with 10800 out of last 12000 blocks (90%)
BIP101: Yes, support with 750 out of last 1000 blocks (75%)
BIP102: No
BIP103: No
When should we initiate the hardfork?
BIP100: 2016-01-11#
BIP101: 2 weeks after 75% miner support, but not before 2016-01-11
BIP102: 2015-11-11
BIP103: 2017-01-01
# The network does not actually fork until having 90% miner support
What should be the block size at initiation?
BIP100: 1MB
BIP101: 8MB*
BIP102: 2MB
BIP103: 1MB
* It depends on the exact time of initiation, e.g. 8MB if initiated on
2016-01-11, 16MB if initiated on 2018-01-10.
Should we allow further increase / decrease?
BIP100: By miner voting, 0.5x - 2x every 12000 blocks (~3 months)
BIP101: Double every 2 years, with linear interpolations in between
(41.4% p.a.)
BIP102: No
BIP103: +4.4% every 97 days (double every 4.3 years, or 17.7% p.a.)
The earliest date for a >=2MB block?
BIP100: 2016-04-03^
BIP101: 2016-01-11
BIP102: 2015-11-11
BIP103: 2020-12-27
^ Assuming 10 minutes blocks and votes cast before 2016-01-11 are not counted
What should be the final block size?
BIP100: 32MB is the max, but it is possible to reduce by miner voting
BIP101: 8192MB
BIP102: 2MB
BIP103: 2048MB
When should we have the final block size?
BIP100: Decided by miners
BIP101: 2036-01-06
BIP102: 2015-11-11
BIP103: 2063-07-09
prev parent reply other threads:[~2015-07-31 3:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 18:14 [bitcoin-dev] " jl2012
2015-07-30 20:32 ` [bitcoin-dev] A summary of block size hardfork proposals (and a softforking one) odinn
2015-07-31 3:10 ` jl2012 [this message]
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=20150731031034.Horde.pF0_RVukjyAUe06VAuvqaA1@server47.web-hosting.com \
--to=jl2012@xbt$(echo .)hk \
--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