From a0e74f89d6966cbd1eec156d34ab51195e47b346 Mon Sep 17 00:00:00 2001 From: R E Broadley Date: Fri, 16 Sep 2016 06:45:38 +0700 Subject: [PATCH] Remove filterclear This message isn't included in the reasosn for moving bloom services into a opt-out service. Also, filterclear is a useful way for nodes to start with TX relay off and to request TX relay later. (e.g. during IBD). --- bip-0111.mediawiki | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/bip-0111.mediawiki b/bip-0111.mediawiki index 45578329d4..7fc57b7e1b 100644 --- a/bip-0111.mediawiki +++ b/bip-0111.mediawiki @@ -48,11 +48,11 @@ NODE_BLOOM is distinct from NODE_NETWORK, and it is legal to advertise NODE_BLOOM but not NODE_NETWORK (though there is little reason to do so now, some proposals may make this more useful in the future) -If a node does not support bloom filters but receives a "filterload", -"filteradd", or "filterclear" message from a peer the node should -disconnect that peer immediately. For backwards compatibility, in -initial implementations, nodes may choose to only disconnect nodes which -have the new protocol version set and attempt to send a filter command. +If a node does not support bloom filters but receives a "filterload" or +"filteradd" message from a peer the node should disconnect that peer +immediately. For backwards compatibility, in initial implementations, +nodes may choose to only disconnect nodes which have the new protocol +version set and attempt to send a filter command. While outside the scope of this BIP it is suggested that DNS seeds and other peer discovery mechanisms support the ability to specify the