(dot/parachain): handle view update message for receiver side of the network bridge #3864
Assignees
Comments
7 tasks
3 tasks
kishansagathiya
added a commit
that referenced
this issue
Oct 4, 2024
- handled active leaves update message - handled block finalized message - relay network protocol messages - handle view update message for receiver side of the network bridge #3864 - decode messages to wire message (PR #4188), Fixes #4108 - handle our view change in collator protocol validator side (PR #4197), Issue #4156 - Handle network bridge messages (UpdateAuthorityIDs and NewGossipTopology) Fixes #3862 - process network events for receiver side of network bridge Issue Fixes #3863 - process overseer signals for network bridge Fixes #3861
edwardmack
added a commit
that referenced
this issue
Oct 4, 2024
statement distribution skeleton (#4169) Statement Distribution subsystem is responsible for distributing signed statements that we have generated and forwarding statements generated by our peers. This commit just introduces a skeleton for it. - implements the subsystem interface - registers the subsystem with overseer - add the processMessage method with messages to be handled Issue #3583 cleanup remove un-used code add comments regenerate mocks feat(dot/parachain): receiver side of network bridge (#3955) - handled active leaves update message - handled block finalized message - relay network protocol messages - handle view update message for receiver side of the network bridge #3864 - decode messages to wire message (PR #4188), Fixes #4108 - handle our view change in collator protocol validator side (PR #4197), Issue #4156 - Handle network bridge messages (UpdateAuthorityIDs and NewGossipTopology) Fixes #3862 - process network events for receiver side of network bridge Issue Fixes #3863 - process overseer signals for network bridge Fixes #3861
kishansagathiya
added a commit
that referenced
this issue
Oct 14, 2024
Over the network through collation and validation protocol, as part of WireMessage we could get a PeerMessage or a ViewUpdate. ViewUpdate tells us about latest blocks (heads) and finalized number with our peers. We are supposed to be update our peer data with these views. This commit, reads ViewUpdate from both collation and validation protocol and handles them inside network bridge by updating our peer data. Later, it sends that view to other subsystems so that each subsystem can update their view too. Fixes #3864
kishansagathiya
added a commit
that referenced
this issue
Oct 17, 2024
… network bridge (#4249) Over the network through collation and validation protocol, as part of WireMessage we could get a PeerMessage or a ViewUpdate. ViewUpdate tells us about latest blocks (heads) and finalized number with our peers. We are supposed to be update our peer data with these views. This commit, reads ViewUpdate from both collation and validation protocol and handles them inside network bridge by updating our peer data. Later, it sends that view to other subsystems so that each subsystem can update their view too. Fixes #3864
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue summary
Other information and links
The text was updated successfully, but these errors were encountered: