Provably fair algorithms by platform
No two of these platforms compute an outcome the same way. The hash function, the order the seeds are joined in, the separator, how much of the digest is read and the final outcome range all differ, which is why a verifier built for one site usually returns a wrong answer on another. Every row below is taken from the operator's own published material and drives the verifier on this site.
Verified: our implementation reproduces a real result
9platforms. "Verified" means we ran the operator's own published algorithm and reproduced an actual outcome, not that we trust the documentation.
| Platform | Hash | Seed format | Commitment | Source |
|---|---|---|---|---|
| Ripster.gg | HMAC-SHA256 | clientSeed:nonce | SHA-256 | operator page |
| PackDraw | SHA-512 | clientSeed:serverSeed:nonce | SHA-512 | operator page |
| HypeDrop | HMAC-SHA256 (combined seed as key, empty message) | key = GAME-serverSeed-clientSeed-nonce | SHA-256 | operator page |
| CSGORoll | HMAC-SHA256 (combined seed as key, empty message) | key = GAME-serverSeed-clientSeed-nonce | SHA-256 | operator page |
| JemLit | HMAC-SHA512/256 | clientSeed-nonce | SHA-512 | operator page |
| Skin.club | HMAC-SHA512 (inverted key/message) | key = clientSeed-nonce, message = serverSeed | SHA-256 (salt-keyed HMAC) | operator page |
| CSGOEmpire | SHA-256 | serverSeed-publicSeed-round | SHA-256 | operator page |
| Clash.gg | seedrandom v3.0.5 PRNG | serverSeed:clientSeed:round | SHA-256 | operator page |
| RustClash | seedrandom v3.0.5 PRNG | serverSeed:clientSeed:round | SHA-256 | operator page |
Not verifiable today, and why
8 platforms we cover but cannot confirm. This half of the table is the part most sites leave out, and it is the more useful half if you are deciding where to play.
| Platform | Status | What is missing |
|---|---|---|
| Cases.gg | Implemented, unconfirmed | The operator does not publish enough for an outsider to reproduce a result. |
| LuxDrop | Implemented, unconfirmed | The operator does not publish enough for an outsider to reproduce a result. |
| DatDrop | Implemented, unconfirmed | Battles and Battle Royale draw from random.org beacons and are not covered by this tool. The seed-promise check needs both the revealed server seed and the secret salt. |
| Pullbox.gg | Not fully published | States HMAC-SHA512 over server seed, client seed, salt and nonce, but the exact order, separators and conversion live in a CodePen behind the login-gated Verify button. Adapter blocked until that code is obtained. |
| Boxed.gg | Not fully published | Published sandbox covers the HMAC-SHA512 step (client seed + salt + nonce, no separators) but omits the hex-to-ticket conversion to the documented 0-999,999 space. Adapter blocked on that step. |
| Supabox | Not published | No published algorithm; accessible descriptions are partly self-contradictory (seed commit vs crypto.randomBytes). Unsupported until the operator publishes the formula. |
| RillaBox | Cannot be verified | Publishes a five-step narrative (SHA-256 commitment, 0-100 result at 4 decimals) but no formula, no combination string, no nonce, and no public seed access. Cannot be independently verified as implemented. |
| ArenaClub | Cannot be verified | Not provably fair: no seeds, no hashes, no verification tool. The only randomness claim is a Fisher-Yates shuffle statement in a marketing blog post, which cannot be independently verified. |
Common questions
Do all provably fair sites use the same algorithm?
No, and the differences are large enough that a verifier built for one platform usually returns a wrong answer on another. Across the platforms on this page the hash function, the order the seeds are joined in, the separator, how much of the digest is used and the final outcome range all differ.
Why do some platforms show as not verified?
Because they have not published enough to reproduce a result, or because we have implemented what they publish but have not yet confirmed it against a real outcome. We only mark a game verified once our implementation reproduces an actual published or operator-produced result.
What does the seed format column mean?
It is the exact string a platform hashes, including the order of the values and the separator between them. Hashing is order-sensitive, so clientSeed:serverSeed:nonce and serverSeed:clientSeed:nonce produce completely unrelated results. Seed-format mismatches are the most common cause of a failed check.
Does a verified algorithm mean a site is safe?
No. Verified means a specific outcome can be recomputed from values committed before play, and that ours reproduces it. It says nothing about whether withdrawals are honoured, whether the odds are generous, or whether the business is sound.
The honest fine print
A verified algorithm proves a specific outcome came from values fixed before play. It does not prove an operator will honour a withdrawal, that its odds are generous, or anything else about the business: how we verify and what it means.