Skip to content

fix(sysgo): support SP1_PROVER=cluster in verifier and mock mode#340

Open
fakedev9999 wants to merge 1 commit intoop-succinct-sysgofrom
fakedev9999/cluster-proving-support-clean
Open

fix(sysgo): support SP1_PROVER=cluster in verifier and mock mode#340
fakedev9999 wants to merge 1 commit intoop-succinct-sysgofrom
fakedev9999/cluster-proving-support-clean

Conversation

@fakedev9999
Copy link
Member

Summary

  • resolveSP1VerifierAddr() now uses the real SP1 Plonk verifier when SP1_PROVER=cluster
  • Mock mode defaulting logic also checks for cluster mode to set OP_SUCCINCT_MOCK=false

Context

When running E2E tests with self-hosted cluster proving (SP1_PROVER=cluster), the test harness deployed SP1MockVerifier and set OP_SUCCINCT_MOCK=true because it only checked NETWORK_PRIVATE_KEY to detect real proving mode. This caused:

  1. assert(false) reverts when the proposer tried to submit real Plonk proofs to L2OO via the MockVerifier
  2. mock and cluster modes are mutually exclusive panic in the validity binary

Test plan

  • Validated with test-e2e-sysgo-altda using SP1_PROVER=cluster on self-hosted EKS cluster
  • Mock proving CI tests unaffected (no SP1_PROVER env var set)

… mode

resolveSP1VerifierAddr() only checked NETWORK_PRIVATE_KEY to decide
between MockVerifier and real PlonkVerifier. In cluster mode
(SP1_PROVER=cluster), there is no NETWORK_PRIVATE_KEY, so the test
harness deployed MockVerifier even when the cluster produces real Plonk
proofs. This caused assert(false) reverts on L2OO submission.

Similarly, the mock mode defaulting logic set OP_SUCCINCT_MOCK=true
unless NETWORK_PRIVATE_KEY was set, conflicting with cluster mode.

Both conditions now also check SP1_PROVER=cluster.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant