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

Testing with other proving systems supported by circom #89

Open
jimthematrix opened this issue Sep 30, 2024 · 0 comments
Open

Testing with other proving systems supported by circom #89

jimthematrix opened this issue Sep 30, 2024 · 0 comments
Assignees

Comments

@jimthematrix
Copy link
Contributor

jimthematrix commented Sep 30, 2024

  • Nova
  • Plonk
  • Marlin

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?
@Chengxuan Chengxuan self-assigned this Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants