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.

Sign up for GitHub

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

Jump to bottom

DKG should continue in new epoch if it does not complete int is scheduled epoch #727

Open
batconjurer opened this issue Dec 21, 2021 · 0 comments
Open

DKG should continue in new epoch if it does not complete int is scheduled epoch #727

batconjurer opened this issue Dec 21, 2021 · 0 comments
Labels
crypto DKG enhancement New feature or request ledger

Comments

@batconjurer
Copy link
Member

batconjurer commented Dec 21, 2021 •
edited by sync-by-unito bot

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

┆Issue is synchronized with this Asana task by Unito
@sync-by-unito sync-by-unito bot closed this as completed Feb 3, 2022
@juped juped reopened this Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
crypto DKG enhancement New feature or request ledger
Projects
No open projects
Namada-Old
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
2 participants
@juped @batconjurer