Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1S239g-0004nI-QG for bitcoin-development@lists.sourceforge.net; Mon, 27 Feb 2012 16:10:28 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=gavinandresen@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1S239b-0002DU-CM for bitcoin-development@lists.sourceforge.net; Mon, 27 Feb 2012 16:10:28 +0000 Received: by wera1 with SMTP id a1so994186wer.34 for ; Mon, 27 Feb 2012 08:10:17 -0800 (PST) Received-SPF: pass (google.com: domain of gavinandresen@gmail.com designates 10.180.83.70 as permitted sender) client-ip=10.180.83.70; Authentication-Results: mr.google.com; spf=pass (google.com: domain of gavinandresen@gmail.com designates 10.180.83.70 as permitted sender) smtp.mail=gavinandresen@gmail.com; dkim=pass header.i=gavinandresen@gmail.com Received: from mr.google.com ([10.180.83.70]) by 10.180.83.70 with SMTP id o6mr20116538wiy.19.1330359017386 (num_hops = 1); Mon, 27 Feb 2012 08:10:17 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.83.70 with SMTP id o6mr15837342wiy.19.1330359017344; Mon, 27 Feb 2012 08:10:17 -0800 (PST) Received: by 10.223.121.197 with HTTP; Mon, 27 Feb 2012 08:10:17 -0800 (PST) Date: Mon, 27 Feb 2012 11:10:17 -0500 Message-ID: From: Gavin Andresen To: Bitcoin Dev Content-Type: multipart/alternative; boundary=f46d04428854a70e3b04b9f45805 X-Spam-Score: -0.8 (/) 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 1.0 HTML_MESSAGE BODY: HTML included in message -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 -0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1S239b-0002DU-CM Subject: [Bitcoin-development] BIP 16 status update X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2012 16:10:28 -0000 --f46d04428854a70e3b04b9f45805 Content-Type: text/plain; charset=ISO-8859-1 Mining support for BIP 16 is still under 50%, and won't possibly be over 50% by March 1. Which means we need a new evaluation/switchover date: Re-evaluate support: March 15'th Target switchover: April 1 If you're already supporting BIP16, restart bitcoind with the argument: -paytoscripthashtime=1333238400 ... to delay switchover until April 1. Hopefully this will be the last delay; Tycho has told me that deepbit will support BIP16 as soon as he's able to merge and test the changes, which will put support at well over 55%. -- -- Gavin Andresen --f46d04428854a70e3b04b9f45805 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mining support for BIP 16 is still under 50%, and won't possibly be ove= r 50% by March 1. =A0Which means we need a new evaluation/switchover date:<= div>
Re-evaluate support: March 15'th
Target sw= itchover: April 1

If you're already supporting BIP16, restart bitcoin= d with the argument:
=A0 -paytoscripthashtime=3D1333238400

... to delay switchover until April 1.

Hopefully this will be the last delay; Tycho has told me tha= t deepbit will support BIP16 as soon as he's able to merge and test the= changes, which will put support at well over 55%.

--
--
Gavin Andresen

--f46d04428854a70e3b04b9f45805--