To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
	libbitcoin@lists.dyne.org
From: Eric Voskuil <eric@voskuil.org>
Message-ID: <ba422d5e-8e96-3475-2a29-80d89fd67322@voskuil.org>
Date: Sun, 12 Feb 2017 21:18:41 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
	Thunderbird/45.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="5v4tMrNrSlKbtkmknS9F6cThn8RqK9csK"
Subject: [bitcoin-dev] BIP151 protocol incompatibility
Precedence: list

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--5v4tMrNrSlKbtkmknS9F6cThn8RqK9csK
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

The BIP151 proposal states:

> This proposal is backward compatible. Non-supporting peers will ignore
the encinit messages.

This statement is incorrect. Sending content that existing nodes do not
expect is clearly an incompatibility. An implementation that ignores
invalid content leaves itself wide open to DOS attacks. The version
handshake must be complete before the protocol level can be determined.
While it may be desirable for this change to precede the version
handshake it cannot be described as backward compatible.

e


--5v4tMrNrSlKbtkmknS9F6cThn8RqK9csK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJYoUGxAAoJEDzYwH8LXOFOTiwIAIixQ/0F7Zqmcndk80xmMW5R
mTrNA+p2VGc3OdKnjZcodDEHNIIP0kxF372H9smn22LNYgKMU63a9na1HmOevjXO
/lIbPsIOvvKuyDDggVSURBlKo0EUsnRyvlL3M2ERFQw5N8N6f0rXh3YQKmAyaq0B
buOOsquVOW6tbBlmcE2fN4Lr6oa6SSR/glsrtD7cdBcXLrkUZ/AvxeT4e7i6B+5Y
RMv3ZdiHuaKBsuU/vavOYG+omqtRD3tiTCzC11p1PDUyX+dCMvGd1Y8A4/uz4uqc
8Bqwpi2eKYiYsszqR3JPBBFHE9PGpP+4UxikBUEpJGtigLe2C+7xYhaagKtbPsk=
=GF0g
-----END PGP SIGNATURE-----

--5v4tMrNrSlKbtkmknS9F6cThn8RqK9csK--