Do gossip timestamp request so we get sent gossip by peers #9474
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
limit amount of times we request full gossip from peers remove timestamp don't fetch if we are alredy synced move sleep add gossip timestamp request so we even get sent gossip improve gossip query timestamp add gossip timestamp request so gn get sent gossip
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bolt 7 says in Rebroadcasting
We already had the function
request_gossip()which was never called, so we only pulled the gossip by requesting channel ids inquery_gossip()but never told the peer to forward gossip to us (by sendinggossip_timestamp_filter).With this PR we also first check if the peer supports gossip queries (has
gossip_queriesfeature bit) and limit the gossip fetching a bit by not requesting the full gossip every time we connect.