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
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.
The text was updated successfully, but these errors were encountered:
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 havereturn_data
). This works in some cases but not in others. Another option is the presence ofivc_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.The text was updated successfully, but these errors were encountered: