Formal Verification
Formal Verification in Blockchain: What It Proves, What It Cannot
What a formal proof guarantees about a contract or circuit, and which questions it leaves open.
Picus proves your circuits are free of underconstrained bugs, the source of over 96% of bugs at that layer, or returns a concrete counterexample.
For Circom, Halo2, Zirgen and Plonky3.
Helped RISC Zero catch 35 issues in its zkVM during development.

Picus targets one vulnerability class, the one behind over 96% of real-world ZK circuit layer bugs, and settles it with a proof.
// 001
Constraints too weak or incomplete to fix a single output for each input.
// 002
Gaps an attacker could use to produce a valid proof for a false statement.
// 003
Two distinct witnesses that satisfy the same constraints, returned as a concrete counterexample.
A verified result holds for every possible input, not just the ones you tested.
Picus combines lightweight static analysis with solver-based reasoning. It proves that your constraints fix exactly one output for each input, across every possible input.
// 001

Circom, Halo2, Zirgen or Plonky3 circuits.
// 002

Picus reasons over the constraints of each circuit, not over sampled inputs.
// 003

A proof of determinism, or a counterexample you can reproduce.
Scout flags a signal it suspects is underconstrained. Picus verifies it and returns the evidence: a proof that the circuit is deterministic, or two witnesses that break it.
Scout AI - Findings
Line 10
Signal r may be underconstrained
Picus - Evidence
Circuit is nondeterministic
Two distinct witnesses satisfy the constraints.
// COUNTEREXAMPLE FOUND
Picus does not guess. When it can neither prove determinism nor build a counterexample, it tells you so.
Picus returns two distinct witnesses that satisfy the constraints.

Picus runs in your CI and re-verifies your circuits as your codebase evolves. A new underconstrained bug surfaces in the commit that introduced it, not weeks later.
ZK Vanguard catches likely underconstrained signals; Picus proves their absence. Run ZK Vanguard for a fast first pass, then Picus for a guarantee that holds for every input.
Catches likely underconstrained signals in a fast first pass.
// 01 ZK Vanguard
Explore ZK Vanguard →Proves the absence of underconstrained signals, for every input.
// 02 Picus
Picus re-verifies your circuits on every change, so your auditors start from circuits already proven deterministic, or with the counterexamples in hand. The audit still gives you a signed expert review.
Before audit
During audit
After audit



RISC Zero runs Picus in its CI/CD pipeline to verify the determinism of its RISC-V zkVM. 35 issues surfaced and were mitigated during development, and every new change is verified as the codebase evolves.
zkVM
It uses mathematical reasoning to prove a property of your circuit for every possible input, not just the ones you tested. Picus proves determinism: each input fixes exactly one valid output.
A circuit whose constraints are too weak to fix a single output for each input. An attacker can then produce a valid proof for a value you never intended.
Circom, Halo2, Zirgen and Plonky3.
It returns unknown: no proof and no counterexample, so you know exactly where you stand.
ZK Vanguard catches likely underconstrained signals; Picus proves their absence. ZK Vanguard runs first for speed, Picus follows for the guarantee.
Still have questions? Contact us
Formal Verification
What a formal proof guarantees about a contract or circuit, and which questions it leaves open.
ZK Security Audits
Why underconstrained signals and witness leaks break ZK circuits, and how to check for them.
Circom
Write a first Circom circuit, then verify that every signal is constrained the way you intend.
Run Picus on your ZK circuits today.