-
Notifications
You must be signed in to change notification settings - Fork 26
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
feat(l2): multi prover foundations #1397
Open
fborello-lambda
wants to merge
38
commits into
main
Choose a base branch
from
l2/implement_sp1
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
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
**Motivation** We would like to have the contracts that perform the zk proof verification deployed locally. **Description** - Deploy the `groth16verifier` - Extra steps are needed to allow multiple zkVMs, we may configure the contract to skip the verification of each zk proof independently. Will be used by #1397
fborello-lambda
force-pushed
the
l2/implement_sp1
branch
from
December 10, 2024 12:54
8ab3806
to
6ef5133
Compare
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.
Motivation
We want to have multiple
prover_clients
with different proving systems running in parallel, then theprover_server
should keep track of each proving system and their proofs to verify them on chain.When all the required proving systems finish to create the blocks proof, and then verified on chain, we can say that the blockchain is advancing.
At the moment, just one proving system is allowed, there isn't a mechanism to keep track of many
prover_clients
with different proving systems.Description
prover_client's
proving systems