Sending control extension message to remote peers#442
Merged
lucassaldanha merged 6 commits intolibp2p:developfrom Feb 17, 2026
Merged
Sending control extension message to remote peers#442lucassaldanha merged 6 commits intolibp2p:developfrom
lucassaldanha merged 6 commits intolibp2p:developfrom
Conversation
This file contains hidden or 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
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.
The overall logic for sending control extension messages to remote peers is simple:
GossipExtensionsStateclass was added toGossipRouterto help keep track of which peers our node has already sent a control extension message to, to avoid sending it again.GossipExtensionsStatepart of #436