Plonky3 audit tools that prove your circuits are deterministic

In Plonky3, your trace generator and your AIR are separate code, and only the AIR binds the prover. AI agents review both, ZK Vanguard catches the columns your constraints leave loose, and Picus backs the result with formal verification.

For AIRs and trace generators written in Rust. ZK Vanguard results in seconds to minutes, depending on complexity.

A Plonky3 AIR with an unconstrained trace column: Scout finding, ZK Vanguard finding with the column trace and the Picus Unsafe result.

What AI agents review in your Plonky3 code

Scout reads your AIR definitions and the trace generation code that feeds them, builds a threat model for the circuit, and reports what it finds. It works even before your crate compiles.

Threat model

What your AIR must guarantee: the public values it exposes, and what a valid proof should attest.

AIR and trace logic

Boundary rows, transition gating and how each column gets filled, read the way a reviewer would.

Evidence for every finding

Each suspect in your AIR goes to ZK Vanguard or Picus and comes back with tool output behind it.

Security tools for Plonky3 AIRs

For every AIR you change, the same pair runs: ZK Vanguard catches likely underconstrained signals; Picus proves their absence.

Static analysis for ZK circuits

Detects underconstrained columns, witness leakage, non-deterministic dataflow and unused components in your constraints. Results in seconds to minutes.

Formal verification for ZK circuits

Proves your AIR fixes every output for given inputs, or returns two distinct witnesses that satisfy every constraint.

Common Plonky3 vulnerabilities, and the tool that covers each

STARK-friendly fields are small and AIR constraints only see what you wire into them, so the classic bugs look different from R1CS.

Common Plonky3 vulnerabilities, and the tool that covers each
VulnerabilityWhat happensCovered by
Column never constrainedA trace column your generator fills but no AIR constraint reads.ZK Vanguard + Picus
Missing boundary constraintAn initial or final state never pinned on the first or last row, so a trace can start anywhere.Picus
Ungated transitionA transition constraint applied on the last row, where it wraps around to the first.Scout
Small-field overflowBabyBear and KoalaBear are 31-bit fields: a u32 or a sum of limbs wraps without limb range checks.ZK Vanguard + Picus
Non-boolean flagsA selector or flag column used as 0 or 1 but never constrained to be boolean.ZK Vanguard + Picus
Trace and AIR disagreeYour generator computes one value while the AIR only enforces a weaker relation.ZK Vanguard

A fully constrained AIR can still encode the wrong logic: Scout reviews it against your threat model.

From Plonky3 finding to formal proof

Scout flags a column your trace generator fills but no AIR constraint reads. Picus verifies the AIR and returns the evidence: two distinct witnesses that satisfy every constraint.

Picus results: unsafe, verified, unknown.
Finding (Scout) → Evidence (Picus): two witnesses

Fits your Plonky3 toolchain

Your AIRs and trace generators stay in Rust, as they are. Determinism is a property of your constraints, not of FRI or your hash, so the result holds across the prover configuration you choose.

// 001

Connect your repository

Your Plonky3 crate on GitHub.

// 002

Prepare the circuit

Plonky3 AIRs are translated into LLZK, the intermediate representation ZK Vanguard analyzes.

// 003

Run on every commit

GitHub Actions runs ZK Vanguard and Picus on each commit, before your AIR changes ship.

Building with a coding agent? Call the same tools from your session through AuditHub MCP.

Alongside your Plonky3 audit

AIRs get optimized after the audit, often to cut trace width or constraint degree, and each change can loosen a constraint. AuditHub rechecks every change in CI, and the audit still gives you a signed expert review.

Before audit

During audit

After audit

ZK Vanguard // EVERY CHANGE
ZK Vanguard task summary: steps, findings and artifacts.
AuditHub ZK Vanguard check on a pull request.
ZK Vanguard recent tasks across versions v1 to v3.
Picus // EVERY CHANGE
Picus task summary: steps, findings and artifacts.
AuditHub Picus check on a pull request.
Picus recent tasks across versions v1 to v3.

Continuous determinism checks at RISC Zero

RISC Zero runs Picus in its CI on its zkVM circuits, where it surfaced 35 issues during development. Every new change is verified as the codebase evolves.

Other languages AuditHub checks

Plonky3 security FAQ

What makes a Plonky3 AIR underconstrained?

A column, boundary or transition the AIR does not fully pin down. A prover can then reach a different output from the same inputs and still produce a valid proof.

Can Picus prove a Plonky3 AIR is deterministic?

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.

How do ZK Vanguard and Picus work together?

ZK Vanguard runs first and catches likely underconstrained signals in seconds to minutes. Picus follows and proves their absence, or returns a concrete counterexample.

Do these tools replace a Plonky3 audit?

No. They check your AIRs continuously between audits, and the audit gives you a signed expert review.

Still have questions? Contact us

Learn more about Plonky3

Keep every AIR change deterministic

Run ZK Vanguard and Picus on your Plonky3 code today.