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

feat: efficient batch range check #462

Open
3 tasks done
gbotrel opened this issue Feb 8, 2023 · 2 comments
Open
3 tasks done

feat: efficient batch range check #462

gbotrel opened this issue Feb 8, 2023 · 2 comments

Comments

@gbotrel
Copy link
Collaborator

gbotrel commented Feb 8, 2023

see also #388 .

The batch range check component should enable:

  • efficient limb batch range checks for emulated arithmetic (Groth16)
  • efficient limb batch range checks for emulated arithmetic (PlonK)
  • bypass the range check constraints (but still identify the affected variable that need to be range checked) to perform the range checks out-of-circuit.
@gbotrel
Copy link
Collaborator Author

gbotrel commented Mar 15, 2023

@ivokub can you update status on this one?

@ivokub
Copy link
Collaborator

ivokub commented Mar 15, 2023

@ivokub can you update status on this one?

All is done. The range check gadget is agnostic to the builder if it either implements Committer or Rangechecker interfaces. If PLONK is to receive Commit method, then range checks start working automatically. Or if we plug in builder (e.g. Wizard) which has native support for range checks, then starts automatically working (i.e. we relay all range checks to the proof system, which handles it on its own).

I'm not sure if should close before PLONK commitment is done? Otherwise done from my side.

@ivokub ivokub removed this from the v0.9.0 milestone Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants