Fairness verifier

Every round of every game, whoever plays it, takes the next number from one shared count before any result is known. Your browser rechecks each of your rounds the moment it settles, and one tap on “Proof” under the result shows why it came out that way. Check a round from its copied data the same way.

  1. The ledgergives every round the next number — one count for every game and every playerevery number from #0 up can be checked here once the epoch's seed is published: none skipped, none used twice
  2. Pascalifixes one seed per epoch and publishes its commitment before your roundpublishes the seed 24 h after the epoch retires
  3. Your browsermakes a fresh random seed for every roundsealed when you place the round, shown when it settles

Active epoch Loading…

Your phrase · optional

Browser-generated by default

Your browser generates a fresh random seed for every round. You can mix in a phrase of your own; it stays in this browser.

Make up something new. Never type a wallet recovery phrase, a private key, or a password you use anywhere else.

What this does, and what it does not

Your value is folded into the random seed, not used in its place — the seed this browser mints still does the hiding, so you lose nothing by typing something ordinary. What the fold adds is a check: every settled round shows whether the seed it published recomputes from what you gave it, so a generator that stopped folding your phrase is caught rather than assumed away.

It does not make this page trustworthy. The code that stores your phrase and the code that checks the fold are both served by us, so a service willing to change what it serves could read one and fake the other. What that costs is secrecy: it has to ship a bundle that does it, in public. To audit without trusting this page, skip it and drive the reserve and reveal endpoints yourself, with a seed we never see — the current commitment API is the entry point, and the test vectors on the fairness page carry the exact bytes each hash is taken over.

Published

Recent epochs

Your browser's check Select an epoch

not checked
For auditors and developers

Round key = HMAC(epoch seed, epoch id, nonce). The result folds that key with your seed and the round's terms — and this browser recomputes both.

Writing your own verifier? The current commitment API is the entry point. Signed test rounds with every transcript, so you can check it against something other than this page. sha256 07fe9cbabd00123208ef642a39c64893abccb5a63e7df795e0e1ed676e804163

Not taking our word for the recomputation either? Save the verifier — one file, no network, opens from your own disk and checks a round with nothing loading from anywhere. sha256 ab1d01db2c41bdca88f7018c8b77c4606268c72f6b2ddb36cca557de81f2a5e0

Queued commitment Loading…