-
Notifications
You must be signed in to change notification settings - Fork 391
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
Upgrade 5 #1445
Upgrade 5 #1445
Conversation
btw.. if i provide curie-chunk-circuit as HALO2_PROTOCOL, and darwin-chunk-circuit as SP1_PROTOCOL, actually the batch circuit can verify either curie chunks or darwin chunks? so if we think more generally, the batch circuit is just a one-in-many mixer. |
Technically, yes. But as of the current changes the batch circuit supports only 2 variants, which I have called |
Description
The batch circuit now supports aggregation of chunk SNARKS (layer-2) that can belong to either of the following routes:
super circuit
->compression circuit
->compression circuit
sp1
->halo2-backend
-> compression circuit`Prior, since only route 1 existed, the SNARK protocol was loaded as a constant. The fundamental change made in
snark-verifier
(scroll-tech/snark-verifier#39) is to expose aaggregate_as_witness
method that loads the SNARK protocols as witness instead.In the batch circuit, we add the following constraints:
Type of change