You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the DKG protocol has one epoch to create an encryption key for the next epoch. If it does not finish, it stops and the next DKG instance begins. That means there is no encryption key for a whole epoch. Instead, we should run two DKG instances:
Continue the old one to get a key for the current epoch
The regularly scheduled one to get a key for the next epoch
Currently, the DKG protocol has one epoch to create an encryption key for the next epoch. If it does not finish, it stops and the next DKG instance begins. That means there is no encryption key for a whole epoch. Instead, we should run two DKG instances:
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: