Gossip Extensions feature flag#443
Merged
lucassaldanha merged 4 commits intolibp2p:developfrom Feb 19, 2026
Merged
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
2 participants
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.
Main change
The main idea behind this change is to ensure backwards compatibility with anyone already using GossipRouter.
Introduce a new
GossipExtensionConfigdata class that is used to set which extensions should be enabled.The
GossipRouterhas been updated to receive a new constructor parametergossipExtensionsConfigthat is used to initialise the objectGossipExtensionsState.GossipRouterBuilderwas updated to receive aGossipExtensionsConfig; this way, the application can decide what extensions to enable when creating a router.When processing extensions messages on
processExtensions, the router uses the flags from GossipExtentionState to determine if:Other changes
Had to rename a bunch of methods and variables because it wasn't consistent with the spec. We have ControlExtensions (and not ExtensionsControl), etc.