Proving flow

The CLI wraps ProveKit’s lifecycle in three primary commands (prepare, prove, and verify) plus generate-gnark-inputs when you need to wrap a proof in Groth16 for on-chain verification.

prove reads the .pkp plus a per-instance witness (Prover.toml, an input object, or an SDK witness map) and produces proof.np. verify reads the .pkv plus that proof and returns valid or invalid. The optional gnark wrap takes the same .pkv and proof and emits a Groth16 outer proof for EVM consumption.

Filenames do not imply compatibility

basic.pkp, basic.pkv, and proof.np are only compatible when generated from the same circuit configuration, branch, and commit. Use checksums and provenance records; never trust the filename alone.

Where to go next

• Artifact lifecycle: pairing, regeneration, and custody rules.
• Designing circuits for ProveKit: ProveKit-specific mechanics that shape circuit authoring.
• Security and trust model: what verification proves and what it doesn’t.
• CLI reference: every command’s options.
• Glossary: Noir, ACIR, R1CS, WHIR, and the artifact-file terminology.