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

Consistent mechanism for indicating kernel circuits from ACIR #1165

Open
ledwards2225 opened this issue Dec 4, 2024 · 0 comments
Open

Consistent mechanism for indicating kernel circuits from ACIR #1165

ledwards2225 opened this issue Dec 4, 2024 · 0 comments

Comments

@ledwards2225
Copy link
Collaborator

In the IVC setting, it must be known whether a circuit is a kernel or an app in order to properly perform the databus consistency checks. At some point I was using the presence of calldata acir constraints as an indicator (since apps only have return_data). This works in some cases but not in others. Another option is the presence of ivc_recursion_constraints in the constraint system. This is likely the better choice but either could potentially work. Either way, find a way to set this once and for all in a location sufficiently upstream so as to tricker all of the relevant logic.

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

1 participant