Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.149.80 as permitted sender)
	client-ip=62.13.149.80; envelope-from=pete@petertodd.org;
	helo=outmail149080.authsmtp.com; 
Date: Tue, 29 Oct 2013 06:14:52 -0400
From: Peter Todd <pete@petertodd.org>
To: Mike Hearn <mike@plan99.net>
Message-ID: <20131029101452.GA15808@savin>
References: <274a1888-276c-4aa6-a818-68f548fbe0fa@me.com>
	<9DCDB8F6-E3B2-426B-A41E-087E66B3821A@gmail.com>
	<526B45DB.2030200@jerviss.org>
	<CABsx9T2OMA_u=S9yUh2j78QDuCDUorYctktuixjwAjqc6neW=Q@mail.gmail.com>
	<526DD18A.7060201@jerviss.org> <l4lajm$3ga$1@ger.gmane.org>
	<CAAS2fgSuL4f9Sdg2CyK-EuCKK04gD98zHDoKFyTg_Fp_cNiz=A@mail.gmail.com>
	<CABsx9T3p6KFc8FiOgBwLtQsmkETE_iUbMhO47pS7J3hi3a9_4w@mail.gmail.com>
	<CANEZrP1teOnb=Gt_Nybh0jfQopK06Ps34Hy73OxOpHwuz-iZig@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q"
Content-Disposition: inline
In-Reply-To: <CANEZrP1teOnb=Gt_Nybh0jfQopK06Ps34Hy73OxOpHwuz-iZig@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Andreas Schildbach <andreas@schildbach.de>,
	Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Feedback requested: "reject" p2p message
Precedence: list


--Q68bSM7Ycu6FN28Q
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 29, 2013 at 10:52:31AM +0100, Mike Hearn wrote:
> For block 0x11 again shall there be a separate code for "block is from the
> future"? We don't want to lose the nVersion field to people just using it
> for nonsense, so does it make sense to reject blocks that claim to be v2 =
or
> v3?

That would prevent us from using nVersion as a soft-forking mechanism.

--=20
'peter'[:-1]@petertodd.org
000000000000000908fddb47210344de50e6d3bd842e649c68853eeee0390dcd

--Q68bSM7Ycu6FN28Q
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQGrBAEBCACVBQJSb4qbXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDkwOGZkZGI0NzIxMDM0NGRlNTBlNmQzYmQ4NDJlNjQ5YzY4
ODUzZWVlZTAzOTBkY2QvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkft4dQf9HNuVrFZJLcbhNyFpM7Xt6M1C
SyKdBaBDZQmuFS3lK/jmPBlSWzXLFRNAgZHiyCXyDG/8xRiMXeetc0oDTsqq4xTm
d6xwUu+3TGhV6diNaTV022LiAsbQseYtQ1KbKGTOGrpoVDRc0tdmsVUNeoTqwNdj
/JjqrtzWTIgXz072F5d2myWuDrL2zcuMRG1Px/pxoKpchIRbokN4BwIaiMkm5+Ty
xY0l4r6qYW+wB5RQkvl2vZMXMKOP3TnqBqQ5B6/GxtiSm54/15WPqhEMdyR0y9y7
ngnsRxZRTpG70gIRjXeFnNJUbDcp4opV896U9Ql38SNQA0l7oL3pdvUpoHZ/Lg==
=eVVn
-----END PGP SIGNATURE-----

--Q68bSM7Ycu6FN28Q--