Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <pete@petertodd.org>) id 1Vb6KK-0001Az-2E for bitcoin-development@lists.sourceforge.net; Tue, 29 Oct 2013 10:15:08 +0000 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; Received: from outmail149080.authsmtp.com ([62.13.149.80]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Vb6KG-0005y5-NC for bitcoin-development@lists.sourceforge.net; Tue, 29 Oct 2013 10:15:08 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt10.authsmtp.com (8.14.2/8.14.2) with ESMTP id r9TAEvno033334; Tue, 29 Oct 2013 10:14:57 GMT Received: from savin (76-10-178-109.dsl.teksavvy.com [76.10.178.109]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id r9TAEqSk066023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 29 Oct 2013 10:14:55 GMT 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) X-Server-Quench: f564352a-4082-11e3-b802-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR bgdMdAsUF1YAAgsB AmUbWlReUVl7XGY7 bAxPbAVDY01GQQRq WVdMSlVNFUsqCHhw c199CRl0cQVEezBx Z09gWz4NWUJ+dkN/ E1NQFWUEeGZhPWMC AkhYdR5UcAFPdx8U a1UrBXRDAzANdhES HhM4ODE3eDlSNilR RRkIIFQOdA4lEzMw TRkJHn01EFQYSj4v IhB0YhQGEUQcOVl4 eUN7QRodPgQJAwJT dwAA X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 76.10.178.109/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) 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 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: petertodd.org] X-Headers-End: 1Vb6KG-0005y5-NC Cc: Andreas Schildbach <andreas@schildbach.de>, Bitcoin Development <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Feedback requested: "reject" p2p message 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: Tue, 29 Oct 2013 10:15:08 -0000 --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--