[zk-sdk] Expose sigma proof types for wasm target #4315
+344
−1
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
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.
Problem
Not all types and functions are exposed for wasm target in the zk-sdk.
Summary of Changes
This is a follow-up to #4171. In this PR, the focus is on exposing the sigma proof types.
a20506c: I exported the Pedersen opening and grouped ElGamal ciphertext types for wasm as they are used to define parameters for certain sigma proof types. Unfortunately, I could not export the
GroupedElGamalCiphertext<N>directly since it has a generic constant parameter which wasm-bindgen does not seem to support. So I created two wrapper types specifically forGroupedElGamalCiphertext<2>andGroupedElGamalCiphertext<3>.5b55e8e: Exported some pod number types as they are going to be used as parameters for certain sigma proof types.
Fixes #