ethereum-optimism / ethereum-optimism/optimism
contracts: Add checks to confirm that SP1Verifier is compatible with the SP1 zkVM releases
Open
@digorithm is already working on this.
Since Sep 16, 2026.
proofs: ZK
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 134
Description
We'll need extra checks to ensure this is the case. This is possible by comparing the contract VERIFIER_HASH() against the first four bytes of simple proof and wiring that into CI / op-contracts release.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the contract's VERIFIER_HASH() and the referenced simple proof, then inspect how CI and the op-contracts release are wired. The work is done when checks compare the verifier hash with the proof's first four bytes and run as part of CI and the op-contracts release process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, solidity
- Domain
- blockchain, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100