Result verification
Commit, reveal, verify
A case-opening request records the server seed commitment and client seed. The receipt preserves the case version, prize pool, recorded roll and revealed seed. The browser checks the result against that record. Game and battle receipts use their own versioned rules.
A reproducible example, not a player opening
This public sample uses invented inputs and an unavailable synthetic case. It is not a player receipt, a real prize or a financial transaction. Its three example outcomes have weights 750, 200 and 50: 75%, 20% and 5% of a total weight of 1,000.
The sample server seed is “blyatdrop-public-example-not-a-private-seed-v1”, the client seed is “public-example-client-v1” and the command key is “synthetic-example-not-a-player-command”. SHA-256 of the server seed is 53207ffbf3f4728d2fccca81f9f2d10dc426b2177179faea07968ae8ec0b5693.
HMAC-SHA-256 signs the exact JSON array [clientSeed, commandKey, counter], starting with counter 0. Its first unsigned 32-bit big-endian word is 961509436. Words at or above 4,294,967,000 are rejected to avoid modulo bias. This word is accepted; its remainder modulo 1,000 is 436. The ranges are 0–749 for A, 750–949 for B and 950–999 for C, so the selected outcome is Example A.
The downloadable JSON includes the exact frozen case and its catalogue hash. The opening verifier checks the seed hash, the saved pre-opening commitment when provided, the hash of the canonical case snapshot, total weights, reproduced roll and the complete selected outcome. A different seed, case weight, roll or selected outcome fails those checks.
Save the commitment before opening
A hash shown only in a completed receipt proves internal consistency, not that it was fixed before your request. Keep the server-seed commitment from before the opening. Compare that saved value when verifying the revealed seed. The verifier explicitly reports when no saved pre-opening commitment was provided.
What verification covers
Verification checks the recorded result and the rules used to produce it. It does not guarantee a profit, supplier stock, payment approval or delivery. Read the odds and availability separately. An animation shows a result; it does not choose one.
Keep the original request
If confirmation is interrupted, keep site data and use the recovery action for the original opening or wager. If verification fails, preserve the ID and contact support rather than treating the result as confirmed.
Sources and content checks
The numerical example was reproduced by the opening calculation and receipt verifier. Changed inputs fail verification. The sample is synthetic, not a player transaction.
Sources checked on 17 October 2026. The review record identifies rule versions, source fingerprints and the limits of this check.
About Fairness
Check a recorded outcome
The fairness checker recalculates supported case-opening, Mines, shared Slide and case battle proofs in your browser. Use the complete JSON downloaded from the original result or account history. A seed on its own is not a complete outcome proof.
Compare the original commitment
If you saved the server seed hash before playing, add it to compare the revealed seed with that original commitment. Without an independently saved hash, a matching calculation checks the supplied record but cannot establish when its seed was committed.
Verification checks the supported calculation. It does not authenticate a file’s origin, prove a wallet payment or guarantee a future result. An unfinished round needs its completed proof before its outcome can be checked.
Keep the original record
If a check fails, keep the proof and original request or round ID. Recover an interrupted request before starting another, and contact support if the original record still cannot be checked.