Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@exmulti.com>) id 1UJR7K-0007iG-Ib
	for bitcoin-development@lists.sourceforge.net;
	Sat, 23 Mar 2013 16:16:26 +0000
X-ACL-Warn: 
Received: from mail-pa0-f52.google.com ([209.85.220.52])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UJR7J-0006Wv-Lx
	for bitcoin-development@lists.sourceforge.net;
	Sat, 23 Mar 2013 16:16:26 +0000
Received: by mail-pa0-f52.google.com with SMTP id fb1so388956pad.25
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 23 Mar 2013 09:16:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=mime-version:x-received:x-originating-ip:date:message-id:subject
	:from:to:content-type:x-gm-message-state;
	bh=Aydb97Wnk/o5SnYnfoBfLTWOqKKyxtg45QOwbp37XZo=;
	b=myfAO6+ePa/lRGSM3uSg0jC7NND5aKQsSQh9XkudeedEgFyMAGVZQoPSVNFnL131hW
	tuzXEgKOqleU4GdQ7hqTLqUlsmUQxWVIgMFuCDyxR9m61gqgNv/dTRRD+ZCX4LoLgUnc
	vvs3upa4fQ6kAcn0cHeQsmn6Z5DmlJUbquc6xgPYquoaE1YOlOCrHOvf6KUccOP7C7Ax
	AmprjNXKpnpzb+N+houaoGtCIbgxmuFkW1HmGJVxDAqkQ1Pc/0iiDoDiAvj9kVkfzYd/
	sAr0vBJBi8PoKDCfLTXEH+FJ+SXlkf41jCVt+nKb06IeODIIwGzjFsaTfz81zT8ONq9x
	AaTw==
MIME-Version: 1.0
X-Received: by 10.68.143.197 with SMTP id sg5mr8717259pbb.101.1364055379631;
	Sat, 23 Mar 2013 09:16:19 -0700 (PDT)
Received: by 10.68.146.133 with HTTP; Sat, 23 Mar 2013 09:16:19 -0700 (PDT)
X-Originating-IP: [99.43.178.25]
Date: Sat, 23 Mar 2013 12:16:19 -0400
Message-ID: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQndhoXCbHmFxmw5z+99//QKujDBGZZMZBFcEhmrG1ABEtuI3rpEX+SLq2Df5Rg9Qa6ERf65
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1UJR7J-0006Wv-Lx
Subject: [Bitcoin-development] Upcoming network event: block v2 lock-in
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: Sat, 23 Mar 2013 16:16:26 -0000

Once a supermajority (95%) of mining reaches block version 2,
nVersion==1 blocks will be rejected.  This event seems likely to occur
in the next week.

Version 2 block specification: https://en.bitcoin.it/wiki/BIP_0034

Watching for the event: http://blockorigin.pfoe.be/top.php  The text
is at the bottom:
"We are currently at 100 out of the latest 1000 blocks on version 1
(10.00%) and 899 out of the latest 1000 blocks on version 2 (89.90%)"

Users should not be impacted.  Some ancient miners will produce
newly-invalid blocks (v1), that will get ignored.  The easy solution
is to mine using a recent bitcoind (0.7 or later).  If you are a miner
and need help upgrading to v2, ping us on #bitcoin-dev or
bitcoin-development@lists.sourceforge.net.

-- 
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com