Purpose
This umbrella issue tracks the current ZeroJ work in recommended priority order. It is a coordination checklist, not a claim that completing every enhancement is required for the same release.
The ordering follows the project priorities: cryptographic correctness, explicit security boundaries, interoperability and independent evidence first; performance and ergonomics later.
Execution rules
- Complete accepted ADR/security design work before implementing an R2/R3 change.
- Preserve canonical encodings and equivalent security semantics across Java, blst, codecs, setup/prover paths, and JuLC where applicable.
- Require positive, negative, differential, and independent evidence appropriate to each issue.
- Do not upgrade production or maturity claims merely because this checklist is complete.
- Revisit this order when an issue uncovers a dependency or changes the security model.
Phase 0 — Resolve the blocking cryptographic profile decision
Phase 1 — Immediate correctness and privacy boundaries
Phase 2 — Independent interoperability and PlonK correctness
Establishing #31 first provides independent evidence for subsequent PlonK changes.
Phase 3 — Provider consistency and secret-handling contracts
Phase 4 — Release assurance and production ceremony gates
Phase 5 — Circuit safety, scalability, and cryptographic performance
Correctness and assurance phases take precedence over these performance changes.
Phase 6 — API and tooling improvements
Reconcile or rescope before implementation
These issues should not be implemented as currently written until their remaining scope is confirmed.
Suggested next action
Start with the ADR and reproducer for #52. If a bounded implementation issue is needed while that design is under review, take #46.
Completion definition
This umbrella can close when:
- Phases 0–4 are complete or explicitly moved to a separately approved release plan;
- remaining Phase 5–6 work is either complete or assigned to a later milestone; and
- every reconciliation item has been closed, rewritten, or deliberately deferred with current rationale.
Purpose
This umbrella issue tracks the current ZeroJ work in recommended priority order. It is a coordination checklist, not a claim that completing every enhancement is required for the same release.
The ordering follows the project priorities: cryptographic correctness, explicit security boundaries, interoperability and independent evidence first; performance and ergonomics later.
Execution rules
Phase 0 — Resolve the blocking cryptographic profile decision
Phase 1 — Immediate correctness and privacy boundaries
Phase 2 — Independent interoperability and PlonK correctness
Establishing #31 first provides independent evidence for subsequent PlonK changes.
Phase 3 — Provider consistency and secret-handling contracts
Phase 4 — Release assurance and production ceremony gates
Phase 5 — Circuit safety, scalability, and cryptographic performance
Correctness and assurance phases take precedence over these performance changes.
Phase 6 — API and tooling improvements
Reconcile or rescope before implementation
These issues should not be implemented as currently written until their remaining scope is confirmed.
Suggested next action
Start with the ADR and reproducer for #52. If a bounded implementation issue is needed while that design is under review, take #46.
Completion definition
This umbrella can close when: