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

Web prover is not updated in each commitment #545

Open
4 tasks
vivianjeng opened this issue Sep 18, 2023 · 0 comments
Open
4 tasks

Web prover is not updated in each commitment #545

vivianjeng opened this issue Sep 18, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@vivianjeng
Copy link
Member

#543 (comment)

When we update the circuits, the prover tests still take the released key url by default.
Instead, we should update keys in each commitment

  • upload keys in an r2 or s3 storage
  • use the tmp url in prover.test.ts (construct the prover like const prover = new WebProver(url))
  • delete keys from the storage (to save storage)
  • detect if the test is run in local or circle ci
    • in local, we don't run the web prover test, since there is no web prover uploaded
    • in circle CI, we run the web prover test
@vivianjeng vivianjeng added the enhancement New feature or request label Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant