1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1UH2Ak-0004Nw-Nt
for bitcoin-development@lists.sourceforge.net;
Sun, 17 Mar 2013 01:14:02 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.49 as permitted sender)
client-ip=74.125.82.49; envelope-from=gavinandresen@gmail.com;
helo=mail-wg0-f49.google.com;
Received: from mail-wg0-f49.google.com ([74.125.82.49])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UH2Ag-0004MJ-1F
for bitcoin-development@lists.sourceforge.net;
Sun, 17 Mar 2013 01:14:02 +0000
Received: by mail-wg0-f49.google.com with SMTP id ds1so3215563wgb.16
for <bitcoin-development@lists.sourceforge.net>;
Sat, 16 Mar 2013 18:13:51 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.92.231 with SMTP id cp7mr17966357wjb.19.1363482831821;
Sat, 16 Mar 2013 18:13:51 -0700 (PDT)
Received: by 10.194.157.168 with HTTP; Sat, 16 Mar 2013 18:13:51 -0700 (PDT)
Date: Sat, 16 Mar 2013 21:13:51 -0400
Message-ID: <CABsx9T050Zia=5Xy4fRh_RtjOQzAVi-UPKmhYCuKbdZTF3U7dA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UH2Ag-0004MJ-1F
Subject: [Bitcoin-development] 0.8.1 plan
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sun, 17 Mar 2013 01:14:02 -0000
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
|
