-
Notifications
You must be signed in to change notification settings - Fork 215
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
arithmic/on-chain #604
Open
arithmic-ASHISH
wants to merge
101
commits into
a16z:main
Choose a base branch
from
arithmic:arithmic/on-chain
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
arithmic/on-chain #604
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nto integrate_circom_cleaning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The objective of this PR is to have the Jolt proof verified on-chain. To achieve this, we proceed with the following steps:
Porting the Jolt Verifier:
Split the Jolt Verifier into two parts Jolt1(ops over BN254 Scalar field) and Jolt2 (ops over BN254 Base field)
Compute a Rank-1 Constraint System (R1CS) for the Jolt1 Verifier over the BN254 scalar field(1).
Compute an R1CS for the Jolt2 Verifier over the BN254 base field(2).
The above R1CS (1) will be verified using Spartan, with Polynomial Commitment Scheme (PCS) Hyperkzg.
Linking Jolt1 and Jolt2:
Jolt1 and Jolt2 share some data like commitments, combiners etc. Check this via Linking.
Compute an R1CS for Linking over the BN254 base field(3)
Porting the Spartan Verifier(Hyperkzg):
Port the Spartan Verifier(Hyperkzg) from the BN254 scalar field to the BN254 base field.
Compute an R1CS for the Spartan Verifier over the BN254 base field(4).
Combined R1CS
Combine the R1CS (2), (3) and (4) as a single R1CS(5)
The above R1CS will be verified using Spartan, with PCS via Surge.
Porting the Spartan Verifier(Surge):
Port the Spartan Verifier(Surge) from the BN254 base field to the BN254 scalar field.
Compute an R1CS for the Spartan Verifier over the BN254 base field(4).
This R1CS will be proved using Groth-16, with the resulting proof being verified on-chain via a Groth-16 verifier.