Parium.

Verify any round yourself.

Every round is committed before it is played and provable after it settles. This page explains the check in plain language, then runs it in your browser, on a committed round, right now. Nothing on this page asks you to trust us.

How the check works

Commit, reveal, re-derive

  1. Commit

    Before any round is played, the game publishes the terminating hash of a chain of seeds. Hashes are one-way, so the entire sequence of crash points is fixed from that moment. Nobody can reorder it afterwards, including us.

  2. Reveal

    When a round settles, its server seed becomes public. Hashing it forward, step by step, must reach the published tip. That proves this exact seed was part of the committed sequence all along.

  3. Re-derive

    Your browser recomputes the crash point from the revealed seed and the client seed. If it reproduces the recorded outcome, the round was fair, and you never took anyone’s word for it.

Running now, in your browser

A committed round, re-proven on this page

Below is vector #1 of the committed golden corpus, a real committed round the engine’s own tests are held to. Your browser is checking it with the same open verifier module the game links after every round. The module itself, not a copy.

Chain bindingChecking SHA-256​999(seed) against the published tip…
Crash point re-derivedRecomputing the crash point from the seeds…

The inputs are pinned in this page’s source; the corpus they come from is public.

What this is worth

For a dispute, this page is the whole conversation

When a player questions a round, there is nothing to escalate: the round’s verification link re-runs the same checks you just watched, on their phone, against the commitment published before the round was played. Support agents run the identical check. An independent auditor inside the engine already ran it too, for every settled round, before anyone asked. One round, one link, three parties, the same answer.

What is open

Exactly what you can read, run, and keep

  • The verifier module verifier_core.mjs — the whole check in one file, about 3 KB compressed: chain walking, HMAC derivation, the crash formula. Zero dependencies, readable in minutes. MIT licensed. View source
  • The round-page driver verifier.mjs — the page logic that runs the module against any settled round’s revealed seeds. View source
  • The golden corpus golden.json — 1,000 committed vectors the engine and this verifier are both tested against, including the one this page just re-proved. If the engine and this module ever disagree on a single vector, the build fails. The game cannot ship ahead of its own proof. Download

That is the complete list. The engine itself is not open source, and the whole point of the design is that you don’t need it: the commitment, the revealed seeds, and this module are enough to check any round.

In the game

Verifying a live round

Every settled round in the game links to its own verification page, /verifier?round_id=…, with the seeds revealed and the same checks run on the spot. In the game, tap any entry in the round history. The link is already there.