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
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.
Curious to understand better what's preventing this from being production ready as described in the README below:
Would love to help if the problem is well understood!
The text was updated successfully, but these errors were encountered: