Project status and versioning

ProveKit is under active development. Code, proof and key formats, recursive-verifier inputs, and integration APIs are branch-scoped unless a release note explicitly says otherwise.

Record provenance before sharing artifacts

Before sharing .pkp, .pkv, proof, or recursive-verifier artifacts, capture the release tag, commit, lockfile, toolchain, and full command line used to produce them.

Branch policy

Branch	Audience	Status
v1.0.2 tag	Users who need a reproducible v1 interface today.	Published v1 release; uses Noir v1.0.0-beta.26.
v1	Users following ongoing v1 maintenance.	Stable branch, but its head can advance beyond a pinned release.
main	Contributors and early adopters.	May include breaking changes to proof, key, recursive-verifier, or API formats between commits.

Use the v1.0.2 tag for the commands on this site. Use main only when you are prepared to regenerate artifacts and adapt to source-level changes.

Artifact compatibility

Do not assume compatibility across branches or commits unless a release note states the formats are unchanged.

Regenerate every affected artifact after changing any of:

• Git branch, commit, Cargo.lock, or Noir compiler version.
• Noir circuit source, package selection, or workspace layout.
• Prover inputs (regenerate the proof, not the keys).
• Recursive-verifier export settings or the proof/verifier pair.

Integration status

Path	Status	Compatibility notes
CLI prepare / prove / verify	Primary local workflow.	Defaults are package-derived; use explicit paths in CI and production.
Rust crates	Direct integration for Rust services and tests; published to docs.rs.	API names and proof/key types may move while main evolves.
WASM bindings	Included in the v1.0.2 source.	Cross-verification with the CLI did not pass in this documentation check; see JS compatibility.
FFI bindings	Included in the v1.0.2 source.	iOS and Android end-to-end checks remain pending; see the Swift and Kotlin pages.
Verifier server	Active HTTP verification path.	Requires reachable HTTP/HTTPS artifact URLs and tuned request/time/concurrency limits.
Recursive verifier	Active Go/gnark wrapper.	Recursive params and R1CS JSON must be regenerated with the matching verifier/proof pair.

For deployment-specific readiness, see the Production checklist.