Signal GossipQuery
support when using IgnoringMessagHandler
#2959
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With its v24.02 release CLN made
GossipQueries
a required feature (see ElementsProject/lightning#6864 and https://github.com/ElementsProject/lightning/blob/master/CHANGELOG.md#2402---2024-02-27-uint-needs-signature), leading to a incompatibility between LDK and CLN when usingIgnoringMessagHandler
as aRoutingMessageHandler
, which is usually the case when a node uses RGS.To fix this issue, we let
IgnoringMessagHandler
signalGossipQuery
support, just to go ahead and ignore every gossip message the peer will send us. While this is nonsensical and still might result in some unnecessary bandwidth wasted, we have to do something to fix the incompatibility.