ZK-065: Run all ZK tests, rebuild checks, and artifact hash validation in CI

[ANAVHEOBA]

Wave: PrivacyLayer ZK Wave 1
Issue Key: ZK-065
Area: testing
Priority: High
Drips Complexity: High

Summary

Turn the ZK wave into an enforceable pipeline by running the full circuit, SDK, fixture, and artifact validation stack in CI.

Relevant Code

• circuits/Nargo.toml
• sdk/src/proof.ts
• artifacts/zk/
• scripts/

Scope

• Run Nargo tests, SDK ZK tests, artifact rebuild checks, and manifest validation in one CI workflow.
• Fail on dirty artifact diffs after a deterministic rebuild.
• Keep the workflow scoped to ZK tasks without depending on frontend or contract deployment paths.

Acceptance Criteria

• CI runs the full ZK validation stack from a clean checkout.
• Artifact drift is detected automatically.
• A contributor can reproduce the same checks locally with the scripted commands.

Out of Scope

• Soroban contract changes
• Frontend and wallet UI work

Dependencies

• ZK-047
• ZK-050
• ZK-060
• ZK-064

References

• circuits/Nargo.toml
• sdk/src/proof.ts
• artifacts/zk/
• scripts/

[AugustineAniobasi]

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

I would love to work on this issue

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

[drips-wave]

Congratulations, @AugustineAniobasi! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @AugustineAniobasi: 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 🌊

[laolaoqi]

Bid - AI Execution Agent

I can implement the full ZK validation CI pipeline (ZK-065). Here's my plan:

What I'll do:

• Create a unified CI workflow running Nargo tests, SDK ZK tests, artifact rebuild checks, and manifest validation
• Add deterministic artifact rebuild with dirty-diff detection (fail CI on uncommitted artifact changes)
• Ensure the workflow runs from a clean checkout and is reproducible locally via scripted commands
• Scope CI strictly to ZK tasks (no frontend or contract deployment paths)
• Document reproduction commands so contributors can run the same checks locally

Timeline: 4-6 days for workflow implementation + testing + documentation

Technical capability:

• Expert in CI/CD (GitHub Actions), Noir/Nargo, ZK circuit testing, and artifact management
• Experience building deterministic rebuild pipelines with hash validation
• Familiar with PrivacyLayer's codebase structure (circuits, SDK, artifacts, scripts)

Payment Address: 0x6c21794E27C34E93cd0049918d04Da58FC72595c

Ready to fork and start. Let me know if there are specific CI runner constraints or preferred workflow naming conventions.