Skip to content

Zero-knowledge proofs for AI agents

Proved,
not promised.

OATHKEEPER coin logo

An AI agent with money is a liability — unless it can prove it obeyed. OATHKEEPER seals its owner's private rules into a cryptographic commitment, then attaches a Groth16 zero-knowledge proof to every decision.

Specimen ledger

rules 0x2b7e…91c4

  • #0141Cloud hosting

    $180.00

    Allowed· proof attached

    Finalized

  • #0142Online casino

    $2,400.00

    Refused· proof attached

    Finalized

  • #0143API credits

    $36.50

    Allowed· proof attached

    Proving

Illustrative entries. Every verdict carries a Groth16 proof from the 516-constraint circuit, sent via Kurier and verified on zkVerify testnet. The live demo makes real ones.
Proof system
Groth16
A zero-knowledge proof on every decision
Circuit
516
Constraints in the rule-checking circuit
Commitment
Poseidon
Only this hash of the owner's rules is published
Settlement
zkVerify
Verified on testnet via Kurier until Finalized

IThe problem

Logs can be edited.
Promises prove nothing.

Give an AI agent a wallet and you are trusting two things you cannot check: the log it writes, and the word of whoever runs it. Both can be rewritten after the fact.

Exhibit A

agent.log · edited after the fact

  • $180.00cloud hostingallowed
  • Erased: $2,400.00online casinoallowed
  • Written in its place: $240.00office suppliesallowed
  • $36.50API creditsallowed

1 entry rewritten · 0 signatures · no way to tell

The log is just a file.

Whoever runs the agent can rewrite its history. A casino payment becomes office supplies, and nothing in the file shows the seam.

Exhibit B

operator statement · unverifiable

“Relax. The agent always follows your rules.”

The promise is just words.

A claim is not evidence. Dashboards, screenshots and audit reports all ask you to trust the very people you are trying to hold to account.

The case for proof

Trust is not a security model. A proof is.

OATHKEEPER replaces the operator's word with mathematics: a commitment to the owner's rules, and a proof for every decision that anyone can check.

IIHow it works

Seal. Decide. Prove.

The owner's rules are never published. The world sees only a commitment to them, and a proof for every decision measured against it.

  1. Step 01

    Seal

    The owner seals a spending cap and a list of forbidden categories. The rules stay private: only a Poseidon commitment to them is published.

    spending cap
    sealed, never published
    forbidden categories
    sealed, never published
    published
    Poseidon commitment
  2. Step 02

    Decide

    Every transaction the agent attempts is screened against the sealed rules, and each one comes out with a verdict: allowed or refused.

    transaction
    $2,400.00 · online casino
    sealed rules
    checked in private
    verdict
    refused
  3. Step 03

    Prove

    Each verdict carries a Groth16 zero-knowledge proof from a 516-constraint circuit, verified on the zkVerify testnet via Kurier until it is Finalized on-chain.

    proof
    Groth16 · 516 constraints
    relayed by
    Kurier
    status
    Finalized on zkVerify

Stays sealed

  • The spending cap
  • The forbidden categories

Never published, and never revealed by a proof. The world only ever sees the commitment.

Goes public

  • The Poseidon commitment to the rules
  • Every verdict and its Groth16 proof
  • Each proof's Finalized record on zkVerify

Enough for anyone to check the agent. Not enough for anyone to learn the rules.

IIIVerify it yourself

Don't trust the agent.
Check the proof.

Checking a proof needs no account, no API key and no permission from us. Anyone can re-check any OATHKEEPER proof with plain snarkjs, the open-source zkSNARK toolkit, on their own machine.

# Install the open-source verifiernpm install -g snarkjs# Check a proof against the circuit's verification keysnarkjs groth16 verify verification_key.json public.json proof.json[INFO]  snarkJS: OK!
Runs locallyNo accountNo API key

Point it at a proof, its public signals and the circuit's verification key. Same inputs, same answer, on any machine.

Browse the code on GitHub(opens in a new tab)

What a passing check tells you

  1. The rules were applied

    The verdict was computed against the exact rules behind the published commitment, not a convenient substitute.

  2. The rules stayed sealed

    The proof shows the rules were obeyed without revealing what they are: not the cap, not the categories.

  3. Nothing was edited

    Change a single bit of the verdict or the proof and the check fails. There is no seam to hide behind.

Finalized on zkVerify

Every proof is also verified on the zkVerify testnet via Kurier and followed until it is Finalized, leaving a public, on-chain record that it passed.

Made with Modulify