From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Date: Sat, 23 Mar 2013 17:09:05 +0000
User-Agent: KMail/1.13.7 (Linux/3.7.3-gentoo; KDE/4.9.5; x86_64; ; )
References: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com>
In-Reply-To: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201303231709.07059.luke@dashjr.org>
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
Precedence: list

On Saturday, March 23, 2013 4:16:19 PM Jeff Garzik wrote:
> 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.

I don't think anyone is mining using bitcoind 0.7 or later? Deepbit is the 
only pool I know of using bitcoind at all, and it's based on 0.3.21 (or about 
that)...

p2pool has supported v2 blocks since 2012 Aug 8.
Eloipool has supported v2 blocks since 2012 Sep 1.
slush's stratum server has supported v2 blocks since it was written.

I'm not aware of any other maintained open source poolservers.
At least PoolServerJ and ecoinpool are known to break when v2 blocks become 
mandatory.