Circom
Circom for ZK Circuits: Write and Verify Your First Circuit
Write a first Circom circuit, then verify that every signal is constrained the way you intend.
Every <-- in a template is a value your constraints must pin down. AI agents review the logic, ZK Vanguard catches likely underconstrained signals, and Picus proves their absence with formal verification.
For Circom templates and circomlib components. Over 96% of ZK circuit layer bugs come from underconstrained logic.

Scout reads your templates and the components they wire together, builds a threat model for the circuit, and reports what it finds. It works even before your circuit compiles.
What your circuit must guarantee: which signals are public, and what a valid proof should attest.
Bit widths, comparator inputs and component wiring, read the way a reviewer would.
Each finding goes to ZK Vanguard or Picus, so it comes back with tool output behind it.
ZK Vanguard catches likely underconstrained signals; Picus proves their absence.
Detects underconstrained signals, witness leakage, non-deterministic dataflow and unused components across your templates. Results in seconds to minutes.
// CIRCOM
Explore ZK Vanguard →Proves every output of your circuit is uniquely determined by its inputs, or returns two distinct witnesses that satisfy the same constraints.
// CIRCOM
Explore Picus →Most Circom bugs come from the gap between what a template computes and what it constrains.
| Vulnerability | What happens | Covered by |
|---|---|---|
| Assigned, never constrained | A <-- assignment with no matching ===: a prover can set the signal to any value. | ZK Vanguard + Picus |
| Ignored component outputs | A circomlib component such as IsZero or LessThan whose output the template never uses. | ZK Vanguard |
| Bit decomposition aliasing | Num2Bits over the full field width accepts two binary representations of the same value. | Picus |
| Unchecked comparator inputs | LessThan(n) assumes inputs fit in n bits. Without a range check, a false comparison can pass. | ZK Vanguard |
| Division by zero in witness code | An inverse computed with <-- that breaks, or misleads, when the input is zero. | ZK Vanguard |
| Private input leakage | A private signal that reaches a public output and reveals part of the witness. | ZK Vanguard |
Plus logic errors that are fully constrained but still wrong: Scout reviews those against your threat model.
Scout flags a signal your template assigns with <-- and never constrains. Picus verifies the circuit and returns the evidence: two distinct witnesses that satisfy every constraint.

Keep writing templates with circom and circomlib, and keep your prover. Determinism is a property of your constraints, so the result holds whether you prove with Groth16, PLONK or fflonk.
// 001
Your Circom templates on GitHub.
// 002
ZK Vanguard and Picus run in GitHub Actions and report during development.
Working with a coding agent? Run AuditHub’s tools from your session through AuditHub MCP.
ZK Vanguard and Picus check your templates on every commit, so your auditors start from circuits Picus has already verified and spend their time on protocol logic. The audit still gives you a signed expert review.
Before audit
During audit
After audit






RISC Zero runs Picus in its CI to verify determinism across its zkVM circuits. 35 issues were found and mitigated during development, and every new change is checked as the code evolves.
A signal your constraints do not pin to a single value. It usually comes from a <-- assignment with no matching ===, and it lets a prover create a valid proof for a wrong result.
Yes. Picus returns verified when every output is uniquely determined by the inputs, unsafe with two distinct witnesses when it is not, or unknown when it can give neither.
ZK Vanguard runs first and catches likely underconstrained signals in seconds to minutes. Picus follows and proves their absence, or returns a concrete counterexample.
No. They check your circuits continuously between audits, and the audit gives you a signed expert review.
Still have questions? Contact us
Circom
Write a first Circom circuit, then verify that every signal is constrained the way you intend.
ZK Security Audits
Why underconstrained signals and witness leaks break ZK circuits, and how to check for them.
Formal Verification
What a formal proof guarantees about a contract or circuit, and which questions it leaves open.
Run ZK Vanguard and Picus on your templates today.