Make Qurrency ML-KEM compliant #148
Draft
Conversation
This file contains hidden or 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
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
Signed-off-by: Matthew Gregoire <[email protected]>
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.
The current K-PKE based implementation in the circuits makes it difficult to work with prevalent libraries that are developed with the NIST standard FIPS-203 in mind, which has the ML-KEM interface with key encapsulation and decapsulation.
The goal is to make the following flows possible, so that developers can easily use any ML-KEM libraries in their applications and use Zeto tokens.