[ZIP 312] Key generation #883
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
daira
reviewed
Jul 23, 2024
Co-authored-by: Daira-Emma Hopwood <daira@jacaranda.org>
|
I added sketches of possible approaches to key generation |
str4d
commented
Apr 2, 2025
| This option SHOULD be used if distributed key generation was used. | ||
| - (TODO: evaluate if it is secure) Participants derive :math:`\mathsf{sk}` from | ||
| the public keys of the particpants (`PK_i` in [#FROST]_) via (TODO: specify | ||
| mechanism to hash all PK_i and derive sk) |
There was a problem hiding this comment.
In the R&D Meeting today, @daira, @ebfull, @nuttycom and myself were discussing post-quantum Zcash preparations, and part of the approach we are discussing requires that ivk can be treated as a commitment to sk. I raised the point that with this draft proposal for FROST keygen, this is not the case. After discussion, we decided to suggest here that for FROST viewing keys, rivk be derived from (sk, ak, nk) instead of just sk. This is sufficient to ensure that Commit^ivk is effectively post-quantum binding (the argument is complicated, but a draft ZIP is forthcoming).
daira
reviewed
Apr 4, 2025
| - (TODO: evaluate if it is secure) Participants derive :math:`\mathsf{sk}` from | ||
| the public keys of the particpants (`PK_i` in [#FROST]_) via (TODO: specify | ||
| mechanism to hash all PK_i and derive sk) | ||
|
|
There was a problem hiding this comment.
Suggested change
| In all cases, the specification in § 4.2.2 ‘Sapling Key Components’ or § 4.2.3 ‘Orchard Key Components’ | |
| MUST be followed when generating key components. If `draft-ecc-quantum-resilience` is adopted, the | |
| $\mathsf{allow\_arbitrary\_ask}$ flag MUST be set to true for the last two options. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.