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

which AIR constraints are missing right now? #1

Open
lsankar4033 opened this issue Jul 14, 2022 · 1 comment
Open

which AIR constraints are missing right now? #1

lsankar4033 opened this issue Jul 14, 2022 · 1 comment

Comments

@lsankar4033
Copy link

Curious to understand better what's preventing this from being production ready as described in the README below:

Screen Shot 2022-07-14 at 10 55 46 AM

Would love to help if the problem is well understood!

@maxgillett
Copy link
Owner

maxgillett commented Jul 14, 2022

Great! The AIR constraints I'm referring to are specifically those covering the range check (RC) and bitwise operations used in the attestations program. RC constraints are implemented in Giza, but they're only enforcing that the instruction offsets of the Cairo VM are within $[0,2^{16})$. These RC constraints will also need to be applied to certain memory values as well (using the builtin approach described in the Cairo whitepaper). I think this should be fairly straightforward to do.

The bitwise constraints are not implemented at all, and not documented for the Cairo VM. It might be possible to adapt the bitwise constraints that are documented for Miden (https://maticnetwork.github.io/miden/design/aux_table/bitwise.html), but I haven't looked in to it. This will be a bit more challenging.

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