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
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1S8bCP-0001S3-FO
for bitcoin-development@lists.sourceforge.net;
Fri, 16 Mar 2012 17:44:21 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.175 as permitted sender)
client-ip=209.85.212.175; envelope-from=gavinandresen@gmail.com;
helo=mail-wi0-f175.google.com;
Received: from mail-wi0-f175.google.com ([209.85.212.175])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1S8bCL-0003sQ-Fr
for bitcoin-development@lists.sourceforge.net;
Fri, 16 Mar 2012 17:44:21 +0000
Received: by wibhn6 with SMTP id hn6so1050431wib.10
for <bitcoin-development@lists.sourceforge.net>;
Fri, 16 Mar 2012 10:44:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.131.34 with SMTP id l34mr2053542wei.54.1331919851321; Fri,
16 Mar 2012 10:44:11 -0700 (PDT)
Received: by 10.223.108.19 with HTTP; Fri, 16 Mar 2012 10:44:11 -0700 (PDT)
Date: Fri, 16 Mar 2012 13:44:11 -0400
Message-ID: <CABsx9T3Hvx-A5+tdPi=-wMWXd_3mW6GbLoponZUjwBA_A=gMMA@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: 1S8bCL-0003sQ-Fr
Subject: [Bitcoin-development] April 1 BIP16 switchover time is definite
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: Fri, 16 Mar 2012 17:44:21 -0000
Support for BIP16 has been approximately 70% of hashing power for the
last two days, and is 54% over the last week, so we're going to
announce that the BIP16 switchover time of April 1 is final and
strongly encourage any pools/miners that haven't yet upgraded their
software to do so in the next two weeks or risk hashing on a minority
chain.
I'll be checking to make sure support doesn't slip before April 1.
I've learned a lot, and have started writing up a document that
suggests how we can make the next upgrade process less painful for
everybody; when I've got a reasonable draft I'll start a discussion
about it here.
--
--
Gavin Andresen
PS: If you're curious, here is what support over the last 30 days
looks like, beginning with the last 24 hours (144 blocks) and going
backwards for each 24 hour period:
Found 103 matches in 144 blocks (71.5 percent)
Found 99 matches in 144 blocks (68.8 percent)
Found 87 matches in 144 blocks (60.4 percent)
Found 70 matches in 144 blocks (48.6 percent)
Found 73 matches in 144 blocks (50.7 percent)
Found 57 matches in 144 blocks (39.6 percent)
Found 52 matches in 144 blocks (36.1 percent)
Found 40 matches in 144 blocks (27.8 percent)
Found 40 matches in 144 blocks (27.8 percent)
Found 46 matches in 144 blocks (31.9 percent)
Found 41 matches in 144 blocks (28.5 percent)
Found 45 matches in 144 blocks (31.2 percent)
Found 57 matches in 144 blocks (39.6 percent)
Found 69 matches in 144 blocks (47.9 percent)
Found 51 matches in 144 blocks (35.4 percent)
Found 53 matches in 144 blocks (36.8 percent)
Found 65 matches in 144 blocks (45.1 percent)
Found 43 matches in 144 blocks (29.9 percent)
Found 48 matches in 144 blocks (33.3 percent)
Found 51 matches in 144 blocks (35.4 percent)
Found 46 matches in 144 blocks (31.9 percent)
Found 57 matches in 144 blocks (39.6 percent)
Found 61 matches in 144 blocks (42.4 percent)
Found 54 matches in 144 blocks (37.5 percent)
Found 53 matches in 144 blocks (36.8 percent)
Found 44 matches in 144 blocks (30.6 percent)
Found 52 matches in 144 blocks (36.1 percent)
Found 51 matches in 144 blocks (35.4 percent)
Found 53 matches in 144 blocks (36.8 percent)
Command used to get that data:
for i in {1..30}; do ./search_coinbases.py --n=$(($i * 144))
--start=$(( ($i -1) * 144)); done
search_coinbases is one of my bitcointools:
https://github.com/gavinandresen/bitcointools
Pretty graph of support over the last 100 blocks here:
github.com/bitcoin/bitcoin/
|
