Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Eric Voskuil <eric@voskuil.org>
Mime-Version: 1.0 (1.0)
Date: Thu, 17 Oct 2019 13:16:47 -0700
Message-Id: <5C03EE5A-B29E-44BC-903F-7094E504580D@voskuil.org>
References: <qoag0d$65ad$1@blaine.gmane.org>
In-Reply-To: <qoag0d$65ad$1@blaine.gmane.org>
To: Andreas Schildbach <andreas@schildbach.de>,
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Removal of reject network messages from Bitcoin
	Core (BIP61)
Precedence: list

As this is a P2P protocol change it should be exposed as a version increment=
 (and a BIP), not just as a conditional service. If the intent is to retain t=
his protocol indefinitely, exposing it conditionally, then a service bit wou=
ld make sense, but it remains a protocol change.

BIP61 is explicit:

=E2=80=9CAll implementations of the P2P protocol version 70,002 and later sh=
ould support the reject message.=E2=80=9C

e

> On Oct 17, 2019, at 12:54, Andreas Schildbach via bitcoin-dev <bitcoin-dev=
@lists.linuxfoundation.org> wrote:
>=20
> =EF=BB=BFOn 16/10/2019 18.43, John Newbery via bitcoin-dev wrote:
>=20
>> Following discussion on this mailing list, support for BIP 61 REJECT
>> messages was not removed from Bitcoin Core in V0.19. The behaviour in
>> that upcoming release is that REJECT messages are disabled by default
>> and can be enabled using the `-enablebip61` command line option.
>=20
> Is there a NODE_* bit we can use to pick peers that support this
> (useful!) feature?
>=20
>=20
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev