feat: create default aggregation object for easier recursion#6087
feat: create default aggregation object for easier recursion#6087lucasxia01 wants to merge 16 commits intomasterfrom
Conversation
Benchmark resultsMetrics with a significant change:
Detailed resultsAll benchmarks are run on txs on the This benchmark source data is available in JSON format on S3 here. L2 block published to L1Each column represents the number of txs on an L2 block published to L1.
L2 chain processingEach column represents the number of blocks on the L2 chain where each block has 16 txs.
Circuits statsStats on running time and I/O sizes collected for every circuit run across all benchmarks.
Tree insertion statsThe duration to insert a fixed batch of leaves into each tree type.
MiscellaneousTransaction sizes based on how many contract classes are registered in the tx.
Transaction size based on fee payment method
Transaction processing duration by data writes.
|
…t, updated input proof/vks for double_verify_proof to reflect
|
Opted not to modify plonk recursion constraint since a lot of tests would need to be changed, and instead moved the changes to a new honk recursion constraint here: #6489. The new honk recursion constraint therefore always has a default aggregation object when the circuit is recursive. |
Create new recursion constraint for honk, which is the same as the plonk recursion constraint, but with a default aggregation object. The default aggregation object work was moved from #6087. This PR is mostly for setup for AztecProtocol/barretenberg#933.
Create new recursion constraint for honk, which is the same as the plonk recursion constraint, but with a default aggregation object. The default aggregation object work was moved from AztecProtocol/aztec-packages#6087. This PR is mostly for setup for #933.
Create new recursion constraint for honk, which is the same as the plonk recursion constraint, but with a default aggregation object. The default aggregation object work was moved from #6087. This PR is mostly for setup for AztecProtocol/barretenberg#933.
Please read contributing guidelines and remove this line.