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

Key refresh w/o aux data (re)gen #22

Open
survived opened this issue Apr 21, 2023 · 0 comments
Open

Key refresh w/o aux data (re)gen #22

survived opened this issue Apr 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@survived
Copy link
Contributor

We want to be able to run key refresh protocol w/o aux data (re)gen. There are two approaches to do so:

  1. Delete aux (re)gen part from existing key refresh implementation
    If one needs to crry out key refresh & aux data (re)gen simultaneously, they would need to run two protocol separately (can be done in parallel). In other cases, when user needs to run either of the protocols, they just run it directly.
  2. Add a bunch of conditions, so key refresh is configurable (whether we want to carry out exact part of the protocol, etc.)

We need to pick whatever approach that produces clearer and simpler code, with the fewest code duplication

@survived survived added the enhancement New feature or request label Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant