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
As part of the DSL integration of the avm recursive verifier, the aggregation object pertaining to the AVM recursion constraint is separate from the one handling the Honk recursion constraints.
See acir_format::process_honk_recursion_constraints() and acir_format::process_avm_recursion_constraints() which both initialized an aggregation object.
Ultimately, it would be more efficient for the public kernel/rollup to aggregate them together.
The text was updated successfully, but these errors were encountered:
ClosesAztecProtocol/barretenberg#1095.
We should aggregate the aggregation objects generated by the Honk and
AVM recursion constraints. Previously, we were creating 2 separate ones
and adding them to the builder, which would've triggered an assert
failure. This work should allow for circuits (like the public kernel) to
have both Honk and AVM recursion constraints.
Closes#1095.
We should aggregate the aggregation objects generated by the Honk and
AVM recursion constraints. Previously, we were creating 2 separate ones
and adding them to the builder, which would've triggered an assert
failure. This work should allow for circuits (like the public kernel) to
have both Honk and AVM recursion constraints.
As part of the DSL integration of the avm recursive verifier, the aggregation object pertaining to the AVM recursion constraint is separate from the one handling the Honk recursion constraints.
See acir_format::process_honk_recursion_constraints() and acir_format::process_avm_recursion_constraints() which both initialized an aggregation object.
Ultimately, it would be more efficient for the public kernel/rollup to aggregate them together.
The text was updated successfully, but these errors were encountered: