From 350189ad489c99a426915b123502a8339ef8d1ba Mon Sep 17 00:00:00 2001 From: Vasil Dimov Date: Tue, 9 Jun 2020 09:36:26 +0200 Subject: BIP155: use a dedicated message for signalling Change signaling of support for the new `addrv2` messages to be done via a dedicated message `sendaddrv2` instead of protocol bump. The drawback of using a protocol bump is that the protocol version is not a bitmask and if a node wants to announce support for `addrv2` this would imply support for all prior features included in that protocol version. --- bip-0155.mediawiki | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) (limited to 'bip-0155.mediawiki') diff --git a/bip-0155.mediawiki b/bip-0155.mediawiki index ba0c798..1364a3f 100644 --- a/bip-0155.mediawiki +++ b/bip-0155.mediawiki @@ -130,14 +130,13 @@ Clients SHOULD reject messages that contain addresses that have a different leng See the appendices for the address encodings to be used for the various networks. -==Compatibility== - -Send addrv2 messages only, and exclusively, when the peer has a certain protocol version (or higher): - -//! gossiping using `addrv2` messages starts with this version -static const int GOSSIP_ADDRV2_VERSION = 70016; - -For older peers keep sending the legacy addr message, ignoring addresses with the newly introduced address types. +==Signaling support and compatibility== + +Introduce a new message type sendaddrv2. Sending such a message indicates that a node can understand and prefers to receive addrv2 messages instead of addr messages. I.e. "Send me addrv2". + +sendaddrv2 SHOULD be sent after receiving the verack message from the peer. + +For older peers, that did not emit sendaddrv2, keep sending the legacy addr message, ignoring addresses with the newly introduced address types. ==Reference implementation== -- cgit v1.2.3