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

[SPEC] Message buffering in DKG to prevent initialisation bugs #34

Closed
7 tasks
drewstone opened this issue Dec 20, 2021 · 0 comments
Closed
7 tasks

[SPEC] Message buffering in DKG to prevent initialisation bugs #34

drewstone opened this issue Dec 20, 2021 · 0 comments
Assignees

Comments

@drewstone
Copy link
Contributor

drewstone commented Dec 20, 2021

Overview

Upon a new authorities set notification the nodes start a new DKG process. We cannot guarantee a perfect simultaneous startup so in the current implementation some nodes might miss initial messages and be unable to further participate in the protocol.

Checklist

On every new DKG message:

  • Iterate through the buffer and perform an action for each message. An action can be:
    • Feed the message to the corresponding rounds object if possible
    • Do nothing if the message is not considered expired yet.
    • Discard the message if it is expired
  • Try to feed newly received message to the corresponding rounds object
  • If there is no rounds object available, append the message to the buffer
  • Define en expiration policy for buffered messages.

Issues

Linked tasks

@drewstone drewstone changed the title [SPEC] Message buffering in DKG [SPEC] Message buffering in DKG to prevent initialisation bugs Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants