barretenberg icon indicating copy to clipboard operation
barretenberg copied to clipboard

Add aggregation to merge/decider/translator recursive verifiers

Open lucasxia01 opened this issue 1 year ago • 3 comments

This would involve modifying the verify_proof interfaces to take in an aggregation object and aggregating the pairing points from KZG.

The tube circuit would then have proper aggregation. (but that's set to change with much of the tube circuit going to Noir?)

lucasxia01 avatar Aug 02 '24 08:08 lucasxia01

Maybe none of this needs to be done except for the merge part, which needs to be handled through folding because we don't have a proof of correctness otherwise.

codygunton avatar Sep 10 '24 15:09 codygunton

Unless we implement the Honk recursive verifiers using the Decider recursive verifier.

codygunton avatar Sep 10 '24 15:09 codygunton

So yeah: we only need to do this for UH

codygunton avatar Oct 03 '24 14:10 codygunton

@lucasxia01 please assess

codygunton avatar Dec 12 '24 20:12 codygunton

I would think we need to do this for all three still. They all output pairing point objects that need to be accumulated. I'm not sure how difficult it would be to do for the merge verifier since that would be in the clientIVC side, but for the decider/translator, it should be pretty trivial to do.

lucasxia01 avatar Dec 12 '24 22:12 lucasxia01