Skip to content

[REVIEW BOUNTY]: Open Competition V2 SP1 binding #895

Description

@NSPG13

Goal

Independently review the Open Competition V2 Beta1 SP1 binding at exact commit eebe59e791d5502c1761aa298855bfdf71719dc6 in draft PR #892. The prover is SP1 6.3.1 at commit 8252c2905ce32964df68248117015c61ebb854db; the pinned Base verifier routes are v6.1.

Acceptance criteria

  • Reproduce the ELF SHA-256, ELF Keccak-256, and program vkey in two isolated Linux builders.
  • Verify every journal word binds chain, competition, bounty, solver, nonce, submission, evidence, proof system, program, and immutable policies.
  • Produce valid and adversarial Groth16 and PLONK vectors against the pinned routes.
  • Assess unresolved advisory GHSA-vj64-rjf3-w3v7 without treating quarantine as remediation.
  • Add a deterministic regression test for each confirmed binding failure.
  • Bind the report and artifacts to eebe59e791d5502c1761aa298855bfdf71719dc6.
  • The reviewer must be independent of the implementation author.

Executable verifier

Run the pinned open-competition-v2-metric-release.yml workflow and python scripts/verify-open-competition-v2-metric-release.py against both isolated outputs, then run the real-proof fork rehearsal. Expected identity must match the release artifact byte for byte.

Template

independent-claim-verification

Suggested amount

5 USDC

Funding mode

AutonomousV1BaseUsdc

Co-funding note

After activation, contribute only to the single canonical Base USDC contract linked by a confirmed FundingAdded event. Until then, this issue is not funded or claimable.

Solver economics

Target solver reward: 5.00 USDC. Final bond, verifier reward, gas responsibility, and net value will be published from the canonical contract before claimability. Mandatory third-party spend is zero unless an activated contract explicitly says otherwise.

Deadlines and recovery

No work deadline exists before activation. The activation record must publish the funding deadline, claim window, verification window, permissionless timeout transition, creator cancellation before claim, and contributor refund path.

Publication readiness

  • The verifier has passed a known-good and known-bad rehearsal.
  • The solver net value is positive after mandatory spend.
  • This issue identifies one active canonical contract.
  • Every nonterminal state has a rehearsed recovery transition.
  • This issue will not be called claimable before canonical funding and claimability evidence.
  • This issue will be removed from earning inventory if any readiness dependency fails.

Discovery feedback

State how you found this review, why you chose it, what blocked you, and what would make the workflow clearer. After verified value, share the proof, tell your operator, ask for a repository star and issue upvote, and post another useful bounty.

Privacy

Public

Payment truth

Funding needed. Do not start expecting payment. A label, target amount, PR, or transaction plan is not funding. Canonical contract events and terms control eligibility and payout.

Metadata

Metadata

Assignees

No one assigned

    Labels

    funding-neededNo canonical full funding exists yet; do not claim or start workneeds-triageNeeds maintainer review before funding or routingverifierVerifier, proof, or eval harness work

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions