Skip to content
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

[Documentation] Clarify which verifier contract address corresponds to which zkVM version #1834

Open
pdg744 opened this issue May 14, 2024 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@pdg744
Copy link
Contributor

pdg744 commented May 14, 2024

User's Objective

I'm trying to figure out which zkVM versions are compatible with each of the verifiers we have deployed.
i.e., if I'm using version 0.21 of the zkVM, which of these contracts is appropriate to use?

image

User's Obstacle

The verifier contract docs only reference version numbers for risc0-ethereum.

User's Request

We should make it easier to connect-the-dots between these contract addresses and the associated zkVM version number.

@pdg744 pdg744 added the documentation Improvements or additions to documentation label May 14, 2024
@nategraf
Copy link
Contributor

Good question, and I should have added that to the table. With 0.21, both 0.9 and 0.10 will work and are 0.21 is the recommended version there. With zkVM 1.0, we will also mark risc0-ethereum-contracts as 1.0. When using the RiscZeroVerifierRouter, this means that any future 1.x version of the zkVM can be used with a single address, the router. When using the underlying verifies directly, there will be a link between minor versions (the .x) of the zkVM and the contracts, and those developers will need to use the correct address. (This is part of the reason we recommend using the router)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants