security(zk): commit circuit and verifier versions into every proof

[enliven17]

Summary

Prevent valid proofs from being replayed across incompatible circuit, verifier, network, or deployment versions.

Motivation

Harpocrates handles privacy-sensitive media, proof material, Stellar transactions, and on-chain verification. This change must be production grade: secure by default, bounded under hostile inputs, observable without leaking evidence or witnesses, and recoverable across partial failures.

Scope

• Design and implement: domain format, version constants, public inputs, backend/frontend/contract propagation, migration policy, and cross-version rejection vectors
• Integrate with existing area/zk modules and preserve API, artifact, proof, and contract compatibility unless a versioned migration is provided.
• Define typed boundaries, configuration, persistence/artifact changes, rollout, and rollback constraints.
• Add privacy-safe signals for state transitions, failures, saturation, and recovery.
• Document threat assumptions, local verification, deployment impact, and troubleshooting.

Acceptance criteria

• End-to-end behavior is implemented with explicit compatibility and rollout semantics.
• Invalid, oversized, duplicated, concurrent, timed-out, cancelled, and partial operations fail deterministically and within resource bounds.
• Unit tests cover logic and negative paths; integration/conformance tests exercise the real boundary.
• Witnesses, media, credentials, signatures, and sensitive proof metadata never leak to logs or unintended storage.
• Authorization, version/network binding, and abuse limits are tested.
• Existing formatting, lint, type checks, tests, circuit checks, contract tests, and builds remain green.
• Documentation covers configuration, migration/rollback, signals, and limitations.

Engineering expectations

Use explicit state machines, bounded work, idempotent transitions, canonical encodings, and versioned cryptographic domains. Avoid single-process correctness assumptions. Cryptographic changes require deterministic vectors shared across circuit, backend, frontend, and contract layers.

Out of scope

Real user evidence, production secrets, live mainnet deployment, unrelated visual redesign, or unrelated dependency upgrades.

Definition of done

Maintainers can reproduce positive and adversarial behavior, confirm privacy properties, operate the feature safely, and roll it back without undocumented repair.

[OnyemaAnthony]

@OnyemaAnthony has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

maintainer please assign me this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OnyemaAnthony to this issue.

[drips-wave]

Congratulations, @OnyemaAnthony! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @OnyemaAnthony: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊