You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, we need to test the circuits and the token implementations with these different proving systems.
We should also think about how to capture the support for those different proving systems. There are differences in the following aspects:
proof format: right now the client/test code and solidity code both assume the groth16 proof format
proving keys generation
verifier Solidity: the current naming conventions for the file names don't take the proving system into account, although the contract names do have the proving system name in it
client sdk: how much would the client SDK in golang and node.js have to change to support multiple proving systems?
The text was updated successfully, but these errors were encountered:
First of all, we need to test the circuits and the token implementations with these different proving systems.
We should also think about how to capture the support for those different proving systems. There are differences in the following aspects:
The text was updated successfully, but these errors were encountered: