Skip to content
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

feat(dot/parachain/bitfield-distribution): handle DistributeBitfield message #4235

Open
Tracked by #3599
haikoschol opened this issue Oct 8, 2024 · 0 comments
Open
Tracked by #3599
Labels
S-subsystems-availability issues related to polkadot host availability subsystem functionality.

Comments

@haikoschol
Copy link
Contributor

Issue summary

The overseer forwards DistributeBitfield messages from other subsystems. Therefore the signature on the bitfield does not need to be checked. The message just needs to be gossiped to peers according to the following rules:

  • Ignore messages with a relay parent that's not in our view
  • Send BitfieldProtocolMessage to all peers that
    • have the relay parent in their view
    • have not already received a message from us with a bitfield signed by the same validator
    • have not already sent us a message with a bitfield signed by the same validator
    • we have a route to as a local grid neighbor in the current topology
  • Send the content of the message as a ProvisionableData message to the overseer

Other information and links

@haikoschol haikoschol added the S-subsystems-availability issues related to polkadot host availability subsystem functionality. label Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-subsystems-availability issues related to polkadot host availability subsystem functionality.
Projects
None yet
Development

No branches or pull requests

1 participant