I built a verifier that never checks anything. It passes your receipt schema.

Description and use

The article explains how to build a verifier that prevents receipt forgery by having an oracle run the check and sign the result, rather than allowing a stub to produce a true verdict.

Problem

A verification pipeline can issue receipts that claim a verdict without actually performing the check, allowing forgery.

Outcome

The oracle‑based receipt design ensures that a receipt cannot be forged because the signature is produced only after the verifier executes the registered check. Stubs cannot produce a true verdict without running the check.

Workflow

• Define artifact and verdict
• Create receipt with artifact hash and verdict
• Compare real and stub verifier outputs
• Add check_id and signed check_name to receipt
• Implement oracle that runs registered check and signs result

Evidence

A true verdict, for the real check's id, signed. The check never ran.

Source

The swapped bytes get a false receipt, validly signed. The stub cannot ask for a true one, because it cannot ask for a verdict at all.

Source