workspace,starknet_proof_verifier: bump privacy-{prove,circuit-verify} to 69ed219, add legacy alias

[Yoni-Starkware]

No description provided.

[cursor]

PR Summary

Medium Risk
Updates the proof verification/proving dependency graph to new upstream git revisions and changes runtime dispatch between legacy/current verifiers based on proof version, which could affect consensus-critical proof validation behavior.

Overview
Bumps privacy-{circuit-verify,prove} (and related stwo*/circuit crates via Cargo.lock) to a newer upstream revision, pulling in updated circuit/verifier dependencies.

Adds a privacy-circuit-verify-legacy workspace dependency pinned to the previous revision, and updates starknet_proof_verifier::verify_proof to route V0 proofs to the legacy verifier while routing V1 proofs to the updated verifier.

^{Reviewed by Cursor Bugbot for commit 85967fb. Bugbot is set up for automated code reviews on this repo. Configure here.}

[Yoni-Starkware]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• workspace,starknet_proof_verifier: bump privacy-{prove,circuit-verify} to 69ed219, add legacy alias #14017 👈 (View in Graphite)
• starknet_proof_verifier: add v0.14.3 regression case for PROOF_VERSION_V1 fixture #14016
• starknet_api,starknet_proof_verifier: write PROOF_VERSION_V1 in try_into_proof_facts #14015
• apollo_starknet_os_program,starknet_os: support PROOF_VERSION_V1 in check_proof_facts #14014
• starknet_proof_verifier: accept either PROOF_VERSION_V0 or PROOF_VERSION_V1 in verify_proof #14013
• starknet_api: add PROOF_VERSION_V1 and accept either marker in ProofFactsVariant #14012
• starknet_api,starknet_proof_verifier: rename PROOF_VERSION to PROOF_VERSION_V0 #14011
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[reviewable-StarkWare]

This change is 

[github-actions]

Artifacts upload workflows:

• Started at 2026-05-10T17:01:25Z
• Started at 2026-05-11T06:34:20Z
• Started at 2026-05-11T07:23:59Z
• Started at 2026-05-11T07:30:03Z
• Started at 2026-05-11T07:32:06Z
• Started at 2026-05-11T07:33:53Z
• Started at 2026-05-11T07:55:56Z
• Started at 2026-05-11T11:49:06Z
• Started at 2026-05-11T12:03:29Z

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 85967fb. Configure here.}

[cursor]

V1 regression test data incompatible with new verifier

Medium Severity

The version dispatch now routes ProofVersion::V1 to the new privacy-circuit-verify (rev 69ed219), but the existing 0.14.3 regression test data contains V1 proof facts with a proof generated by the old prover/circuit (rev 580135e). Since try_into_proof_facts always stamps ProofVersion::V1, all proofs produced between the V1 introduction and this circuit bump carry V1 but are only valid against the old circuit. The 0.14.3 regression test will likely fail, and any in-flight V1 proofs from the previous prover version would also fail verification in production during the upgrade window.

Additional Locations (1)

• crates/starknet_proof_verifier/src/proof_verifier.rs#L85-L94

 

^{Reviewed by Cursor Bugbot for commit 85967fb. Configure here.}

[AvivYossef-starkware]

Can be in a different PR, but I think we need to add cases for virtual snos prover test (round-trip proving and verifying in the CI) .
and maybe change/add cases to the os tests for tx with proof facts

@AvivYossef-starkware reviewed 4 files and all commit messages, and made 1 comment.
Reviewable status: 4 of 6 files reviewed, 1 unresolved discussion (waiting on Yoni-Starkware).