Commit · settle · rotate · reveal

Fairness verifier

Pascali commits to the seed behind each batch of rounds, called an epoch, by publishing its hash. Every round in it, from any player in any game, takes the next number on one public ledger before the seed from that player's browser is revealed, so handing a round a number that loses would take knowing that seed in advance. Settled or void, every number stays on the ledger. Once the epoch ends and its seed is published, anyone can recheck every round in it. The checking runs in your browser and does not reuse the code Pascali settles with.

  1. Pascalicommits one seed per epoch — its hash published stands before your roundseed disclosed 24 h after the epoch retires
  2. Your browsermints a fresh random seed for every roundcommitted with the wager, disclosed at settlement
  3. The ledgernumbers the round with the next nonce, one count for every game and every playeraudited 0…N−1 against the count the service declares

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? Six signed test rounds with every transcript, so you can check it against something other than this page. sha256 a9cb93e0cc99be35c7ed000d5ce763cf7efa8ed4e30381b38d26e4bcfb0e26e7

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 87cbcea14a8deae7cab9048651af02d820e48958e23491dea8abecd0ec67f4f1

Active epoch

Loading…

Queued commitment

Loading…

Personal seed input · 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 entropy is caught rather than assumed away.

It does not make this page trustworthy. The code that stores your entropy 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.

Revealed chain

Recent epochs

Independent recomputation

Select an epoch

not checked