DEMO
CAD 7.2 million. Should it go?
An AI agent wants to send CAD 7.2 million. The bank’s rule says no payment above CAD 5 million leaves without a second signature. Proven: without that signature, no single payment above the ceiling can be approved. Refuted: that the rule caps every payment; a signed one of any size passes. This payment arrives unsigned, and it is blocked at the gate.
Animated film, 2 min 17 s, in English. The rule and its proof are real; the scene is an illustration. Near the end, the film says what this does not guard.
CODE VERIFICATION
Your code was rewritten. Does it still do the same thing?
No film yet for this one. Two things you can open today: a translation checked by a solver step by step, with the files to re-run it, and a difference found in a public AI-generated translation.
ALREADY RUN
On public AI-generated COBOL-to-Java translations, we found differences in behavior, confirmed on IBM’s COBOL compiler, and documentation that does not match the code it describes.
PROOF INTELLIGENCE
2 minutes 17 seconds, with sound. The payments in the film illustrate a payment policy; they are not a client case. The standards shown are the ones each sector already works under; naming a sector does not mean it uses Ironproof today.
AGCO DEMO
3 minutes 43 seconds, with sound. The rule is quoted from the AGCO Registrar’s Standards for Internet Gaming, 2.23 and 2.24. Systems A, B and C and the twelve implementations are illustrative: of the eight that break, seven are common mistakes written on purpose and one comes from an open-source project. All are replayed through the same checker; no operator’s system was examined. Results hold within the bounds shown in the film: up to 8 events over 75 days. The 2023 penalty shown is quoted from an AGCO news release of November 9, 2023.
IN THE TERMINAL
One transfer. Allowed, then blocked.
A $50,000 transfer clears the bank’s policy and is sealed. Then the account is frozen: the same transfer is blocked, the money never moves, and the refusal is sealed too.
- 01The bank’s rules become formal constraints.
- 02The transfer is checked against them before it executes.
- 03Every decision is sealed — Ed25519 + ML-DSA-65 — and re-checked offline.
- 04One edited number in the receipt, and both checks turn red.
Recorded in the terminal on the real engine, 75 seconds. A sample bank policy, not a customer deployment.
THE SEAL
Check the refusal yourself.
This is the sealed receipt of the blocked transfer from the video. Verify it here, in your browser, without us. Then load the copy where one number was changed: $50,000 became $900,000. The seal breaks.
Checked in this tab: both signatures (Ed25519 + ML-DSA-65) and the content hash. The receipts are signed with a demo key, not a customer key.
Runs entirely in your browser — pure-JavaScript Ed25519 + ML-DSA-65 (FIPS 204) + SHA3-512, no server, and no code shared with the software that seals. The wire format is published, so anyone can write a second verifier: read the spec →