-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gossip support subsystem #4133
Comments
@kishansagathiya from what I understand from the link, the The gossip topology is used for sending GRANDPA commit messages, Block Announcements, and then it should be used to gossip subsystems message among validators that are present in the The message limitation and the group creating is explained better here paritytech/polkadot#3239, but, as I mention, is part of the broader gossip topology that is used by the client in different parts. So the statement:
will need to implemented separately and take in account that it will affect other parts of the code not only subsystems. |
This is what I meant. You can see in that code a message called |
I see, but the gossip topology is not responsibility of the subsystem as it seems to be described in this issue. |
I have a feeling you might not be happy with the wordings here, but you understand the meaning. If you have any better way to describe it we can change it. |
Issue summary
NetworkBridgeRxMessage::NewGossipTopology
message.It would be very important to confirm with polkadot-sdk team, whether gossip support is part of the spec or not and figure out the implications of not using the gossip topology.
Other information and links
The text was updated successfully, but these errors were encountered: