Every trajectory has a URL.
The proof of correctness is not a side-effect of running the verifier — it is the trajectory. veric encodes that trajectory into the URL itself, so the artifact is content- addressed and self-contained: no database, no expiry, no server lookup. Below are three canonical examples.
- 03-knight-capital-old-flagKnight Capital — old activation flag
Re-enacted SQL the Knight pipeline tripped on in 2012. The verifier halts on the off-by-one in the activation predicate.
/proof/N4IgjiBcILQwBAQwDYHMD2B9AxugdgGYCWqAdAM5jIA6ec8AsogC4CmATkSkQF6vnxmAC1bwADhxjkAn… - 07-int-string-coercionInteger / string coercion
A silent type promotion that compares aren't going to surface. The proof shows the abstract value at the join point and a counterexample row.
/proof/N4IgjiBcILQwBAewE4BMCmyD6BnAxiugHQ5gA2AOgHZzwDCiAtgA4CuALujvAIbw4BLFmXRI0mfgWTF4… - 09-lattice-pii-low-k-aggregationPII low-k aggregation
T6 (lattice / privacy) — the verifier proves the aggregation never falls below the k-anonymity floor.
/proof/N4IgjiBcILQwBABwK4CMA2BLAxgfQBYCmAhgC4C2xiAdAM5joA6AdnPAIIDmnAToZ2ULwAZplLNCtWvF…
Want to mint your own? Open the playground, write a query, and click Share — the verifier runs in your browser and the resulting URL is its own proof receipt.