DEMO
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 Ironproof code. The wire format is published, so anyone can write a second verifier: read the spec →