From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] 0.8.1 plan
Date: Sat, 16 Mar 2013 21:13:51 -0400 [thread overview]
Message-ID: <CABsx9T050Zia=5Xy4fRh_RtjOQzAVi-UPKmhYCuKbdZTF3U7dA@mail.gmail.com> (raw)
Here's the plan for the 0.8.1 release:
A new CheckBlock() rule, in effect until 15 May, that ensure only
blocks compatible with old releases are accepted into the main chain
(only blocks that touch 4,500 or fewer distinct txids are allowed).
A limit of 500k to blocks created, also in effect until 15 May.
Alerts will be sent to pre-0.8 releases over the next two months,
telling people to either upgrade or create a DB_CONFIG file so they
can handle large blocks.
Code is : https://github.com/bitcoin/bitcoin/pull/2373
I chose May 15 arbitrarily; two months seems like a reasonable 'quick'
amount of time to give people to upgrade/workaround.
The fix was written to be trivial to port to previous versions, and to
be as simple as possible.
Some of the exact details may still change before the 0.8.1 release
(e.g. it might not be exactly 4,500 distinct txids).
Schedule:
0.8.1 binaries late tomorrow or Monday. An expires-after-24-hours
Alert sent on Tuesday to everybody running pre-0.8, pointing to
http://bitcoin.org/may15.html
Another 24-hour Alert sent on April 15, reminding everybody again they
will need to upgrade or workaround.
A final Alert that never expires sent on May 8th.
After May 15, miners will be free to create blocks up to 1MB, and
anybody running old versions who ignored the alerts may be left
behind.
--
--
Gavin Andresen
next reply other threads:[~2013-03-17 1:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 1:13 Gavin Andresen [this message]
2013-03-17 2:03 ` Alan Reiner
2013-03-17 2:20 ` Frank F
2013-03-17 2:31 ` Gavin Andresen
2013-03-17 15:29 ` Luke-Jr
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='CABsx9T050Zia=5Xy4fRh_RtjOQzAVi-UPKmhYCuKbdZTF3U7dA@mail.gmail.com' \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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