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

Remove the remainder of statfulness from the DKG instances #108

Closed
Tracked by #122
piotr-roslaniec opened this issue May 4, 2023 · 1 comment · Fixed by #183
Closed
Tracked by #122

Remove the remainder of statfulness from the DKG instances #108

piotr-roslaniec opened this issue May 4, 2023 · 1 comment · Fixed by #183
Labels
design decision 🚦 Requires a design decision

Comments

@piotr-roslaniec
Copy link

piotr-roslaniec commented May 4, 2023 •
edited
Loading

  • Refers to the usage of DkgState in verification logic etc.
  • Replace this logic with on-the-fly verification and remove the DkgState
  • Consider whether a stateless DKG library would be easier to handle from nucypher/nucypher perspective. Alternatively, keep the DKG object stateful, but consider how to make testing integrations easier. Related: Sans-IO protocol implementations.
@piotr-roslaniec piotr-roslaniec added the design decision 🚦 Requires a design decision label May 4, 2023
@piotr-roslaniec piotr-roslaniec mentioned this issue May 23, 2023
Open
12 tasks
This was referenced Feb 14, 2024
Closed
Merged
@piotr-roslaniec
Copy link
Author

Closed by #183

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design decision 🚦 Requires a design decision
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove statefullness from DKG instances piotr-roslaniec/ferveo
1 participant
@piotr-roslaniec