Don't trust the casino. Check it.

Every bet settled with Vantax comes with a receipt the operator signs with ML-DSA-87, a post-quantum signature, before the server seed is revealed. Paste it here: this page checks the signature and recomputes the outcome itself, in WebAssembly. Nothing you paste leaves your device.

Loading the verifier…

Verify a bet.

You need the receipt and the operator's public key. Add the server seed once the operator reveals it (when you rotate your seed), and the outcome is recomputed from scratch.

Receipt check Signature, commitment and outcome

No receipt yet? Load a demo bet: this page plays the operator, signs a crash bet with a fresh ML-DSA-87 key and fills in the form. Verify it before and after adding the seed, then tamper with it and verify again.

Recompute any outcome.

The same integer-only algorithm the operator runs: a ChaCha20 stream keyed by the server seed, your client seed and the nonce, with rejection sampling so no result is more likely than another.

Outcome calculator Nine games, one specification

Pick a game, give the seeds and the nonce, and press Recompute. Change the nonce to step through bets on the same seed.

Post-quantum signatures, in your browser.

The same ML-DSA-87 (NIST FIPS 204) keys and signatures as the vantax command line, compiled to WebAssembly. A key made here verifies with the CLI and back.

ML-DSA-87 playground Keys stay in this tab

Generate a key, sign the message, then edit one character and verify again.

For demonstrations: a key made in a web page lives in that page's memory. Keep keys that guard value in the CLI, an HSM or a vault.

For operators.

Casinos, sportsbooks, lotteries and game studios can settle every bet this way with the Vantax Fairness Engine, a licensed service that runs on your own servers.

Signed receipts on every betML-DSA-87 signatures bind you to each outcome before the seed is revealed. Players verify with free tools, including this page.
Seeds you can't lose or reusePer-player committed seeds derived from one master secret, sealed with AES-256-GCM. Rotation publishes a signed reveal.
An audit log that restarts you exactlyEvery state change is hash-chained and stored before the engine answers; replaying the log rebuilds its state after a crash.
Round games and RNG reportsSeed chains commit to millions of crash rounds with one hash. Signed, reproducible chi-square and RTP reports for every game.
Talk to us on X Read the specification

Open, specified and checkable.

The fairness algorithm is specified in full, with test vectors, and four implementations check each other (Rust, this WebAssembly build, the CLI and a stand-alone Python script). None of it has had an independent third-party audit yet. A passing check proves the outcome followed the published rules; it says nothing about an operator's licence or solvency.