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

refactor(crypto): CRP-2596 rename VetKdArgs::encryption_key to encryption_public_key #2789

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fspreiss
Copy link
Member

Renames VetKdArgs::encryption_key to VetKdArgs::encryption_public_key to avoid confusions as to whether this is the private or the public part of an asymmetric encryption key pair and thus to make clear that this is not sensitive information.

@fspreiss fspreiss changed the title refactor(crypto): rename VetKdArgs::encryption_key to encryption_public_key refactor(crypto): CRP-2596 rename VetKdArgs::encryption_key to encryption_public_key Nov 25, 2024
fspreiss referenced this pull request Nov 25, 2024
Introduce a `VetKdProtocol` trait and implement it for
`CryptoReturningOk`.

The trait is designed so that underneath we can implement the
cryptographic protocol specified in the π<sub>vetbls-agg2</sub> scheme
specified in section 5.3 of the [vetKeys research
paper](https://eprint.iacr.org/2023/616.pdf), in its _optimistic_
variant, where the meaning of optimistic is described in section 9 of
the research paper. The π<sub>vetbls-agg2</sub> scheme is implemented in
[ic-crypto-internal-bls12-381-vetkd](https://github.com/dfinity/ic/blob/master/rs/crypto/internal/crypto_lib/bls12_381/vetkd/src/lib.rs).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant