Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.47 as permitted sender)
	client-ip=209.85.215.47; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f47.google.com; 
MIME-Version: 1.0
In-Reply-To: <CA+8xBpfzNYqFm-zCD8L7KDiL9x+ez-pUM3B3T981D1n69t8gQQ@mail.gmail.com>
References: <CA+8xBpcwLUt=RBYynbQDwY2Bv1keCPy0pdXP4+8CG-wqvrxOCA@mail.gmail.com>
	<201303231709.07059.luke@dashjr.org>
	<CA+8xBpc9n4_CDYTq80+u3V=sD+F-tTnc1NMVnK1Z_UnNix75dg@mail.gmail.com>
	<201303231743.59510.luke@dashjr.org>
	<CA+8xBpfzNYqFm-zCD8L7KDiL9x+ez-pUM3B3T981D1n69t8gQQ@mail.gmail.com>
Date: Sat, 23 Mar 2013 12:18:03 -0700
Message-ID: <CAAS2fgTq2xz6P1C8kk_HrWsKcJ8rsDSzF_4ceRS+ympj7K-SCA@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=UTF-8
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Upcoming network event: block v2 lock-in
Precedence: list

On Sat, Mar 23, 2013 at 10:47 AM, Jeff Garzik <jgarzik@exmulti.com> wrote:
> On Sat, Mar 23, 2013 at 1:43 PM, Luke-Jr <luke@dashjr.org> wrote:
>> Not for producing coinbases (where BIP 34 is implemented).
> Sure, that is largely the pool server layer.  But it is misleading to
> imply that bitcoind is nowhere in the stack.

You're both right: BIP34's addition of the height is implemented in
the coinbase generator, so for almost everyone the Bitcoind version is
not very relevant for that.  Rejection of invalid chains, however, is
in the Bitcoin daemon.  Upgrading bitcoind alone should be sufficient
to prevent the creation of forks, though if miners would like to avoid
losing income they must update _both_ so that they don't create
invalid blocks or mine on invalid forks.