Quickstart
Prepare keys, generate proof.np, and verify it locally using the noir-examples/basic circuit.
ProveKit turns a Noir circuit into a verifiable WHIR proof. These v1.0.2 guides show the tested CLI and Rust flows, plus the compatibility status of other integration paths.
From a checkout of the v1.0.2 release:
cd noir-examples/basiccargo run --release --bin provekit-cli -- prepare # compile circuit → .pkp + .pkvcargo run --release --bin provekit-cli -- prove # .pkp + Prover.toml → proof.npcargo run --release --bin provekit-cli -- verify # .pkv + proof.np → exit 0That’s the CLI proving pipeline. The Rust integration was also verified with v1.0.2 artifacts; check each platform guide before using those artifacts in another runtime. Walk through it step by step →
Quickstart
Prepare keys, generate proof.np, and verify it locally using the noir-examples/basic circuit.
What is ProveKit?
A developer-friendly introduction to zero-knowledge proofs and the problems this toolkit solves.
Pick an integration
Choose where ProveKit runs in your system, CLI, Rust, WASM, mobile, or recursive.
Deployment checklist
The provenance, evidence, and operational controls required before accepting proofs in production.
For the full integration menu, including CLI, HTTP verifier, and recursive paths, see Integrations overview.
prepare, consumed by prove and recursive export.prepare, consumed by verify.prove, consumed by every verification path..pkp and proof.Every artifact is bound to a specific circuit and release. Treat them as versioned deployment objects. See Artifact lifecycle for the full pairing rules.