A provably fair site commits to every roll before you bet: it shows you a hash of its secret server seed, then reveals the seed afterwards so you can recompute the roll and see it was not changed.
We read the public fairness pages of the 41 CS2 and Rust gambling sites in our fairness check (3 of them, RustChance, RustReaper and Bandit.camp, are Rust skin sites). 8 explain their system in full and let you check past rolls, 7 do so for some games only and 8 say they are provably fair without publishing a formula you can re-run. We could not read 13 of them. Our checker recomputes the actual result for 11 of them and for PandaSkins, which we do not list, and each of its 21 formulas reproduced results or examples the site itself published.
41 gambling sites checked8 fully documented21 game formulas recomputed13 unreadable
How the 41 CS2 and Rust gambling sites in our fairness check prove their rolls
8738213
8 Documented on the site: seeds explained and a way to check past rolls
7 Documented on the site, but only for some games
3 Described by csdb.gg (the site blocked our visit)
8 Says it is provably fair, but publishes no formula you can re-run
2 No provably fair system found
13 Could not check (bot check, sign-in or region block)
Before you play, the site creates a secret server seed and shows you its hash, usually SHA-256. The hash works like a fingerprint: it cannot be turned back into the seed, but any change to the seed changes the hash. So the site is committed to that seed before you bet.
You add a client seed, which on most sites you can change to any text you like, so the site cannot know the full input in advance. A nonce counts your bets with that seed pair (0, 1, 2 and so on), so every roll gets a different input.
The roll is usually HMAC-SHA256 (some sites use HMAC-SHA512) of the server seed with "client seed:nonce" as the message. The site turns the first characters of the result into a number, for example a ticket from 1 to 100,000 that picks the item in a case.
When you change seeds, the site reveals the old server seed. Hash it and compare it with the hash you were shown, then re-run the HMAC for any past nonce: you get the same rolls. A changed roll would not match.
Battles and coinflips, where several players share one result, often use public randomness instead of a client seed: the hash of a future EOS blockchain block, or a signed Random.org draw.
Try it
Check a server seed or a site's result yourself
Paste the server seed a site revealed and the hash it showed you before you played. Your browser hashes the seed and compares; nothing is sent to us or anyone else. Pick a site and game to get that site's actual result: 21 site and game formulas, each one checked against results or examples the site itself published. "Load a real example" fills in one of them.
The HMAC line is the raw value most sites turn into a roll; each site then converts it its own way (see the method per site below). A site and game is only in the list once our formula reproduced the site's own published results or the examples in its own verifier code. A different result means a typo in a seed, a roll made under an older formula, or a site that changed the result. A seed that does not match its hash means the site changed the seed after you played.
My result does not match: what to check
Copy the seeds exactly. No spaces at the ends, no missing characters; some client seeds contain symbols, and every character counts.
Revealed, not hashed. The server seed must be the unhashed one the site reveals after you rotate seeds (or the next day for roulette). The hash only proves the commitment.
The right nonce. Most sites count from 0 or 1 and add 1 per bet with the same seed pair. Run a range to find the bet.
The right game and version. Each game has its own formula, and sites change them (CSGOEmpire roulette changed on 17 Dec 2024). Rolls from before a change need the old formula.
The site's own verifier says otherwise? Go with the site's current code: it may have changed its formula after the date shown under each result here.
Case item ranges change. A ticket maps to the item ranges the case had when you opened it; sites that reprice a case publish new ranges.
Worked example: from seeds to the skin won
A real case battle on PandaSkins, room 30000. The room page publishes the game seed, the client seeds of both players and the SHA-256 hash the site showed before the battle; PandaSkins' fairness page prints the formula. Round 1, player 1 is nonce 1.
Join the inputs with "|": game seed, clients seed, nonce. 66da2ed4565a60b1bdf50f5807a1f69a40f0002d7790112f35b5e153119d8fbb72fa046db9|94400f1a59,ee426f63c0b30b43f582f14302|1
SHA-256 of that text: ee28ce25f02cdcb715e1a37046e02b9b31be7474e65187710f2cd1b02adc3e8c
First 8 hex charactersee28ce25 as a number: 3,995,651,621.
Modulo 100,000, plus 1: 51,621 + 1 = ticket 51,622.
Find the item: the case's odds page lists a ticket range for every item. 51,622 falls in 49,852-52,661, which is AWP | PAW (Field-Tested). That is the drop the room page shows for player 1 in round 1.
Pick "PandaSkins case battles" in the checker above and press "Load a real example" to run the same numbers. Every site and game in the checker has one such example from the site's own published results.
Best documented first
How each CS2 site proves its rolls
From each site's own fairness page, help centre or docs, read logged out. Where a site blocked our visit we used csdb.gg's write-up and say so. "Could not check" does not mean a site is unfair, only that we could not read how it works.
Site
Method
What you can verify
Reproduced by us
Fairness page
Checked
Documented on the site: seeds explained and a way to check past rolls (8)
Seed hash + client seed + nonce; future EOS block (Roll, Crash, PvP)Covers: roll (roulette), crash, dice, case opening, plinko, cluck'n'boom +6 more
Seed hash shown before the roll · Your own client seed · Nonce per bet · EOS block hash mixed in · Checker on the site · Public verify script · Formula published
RecomputedOpen in the checker: Dice, Roll, Cases, Crash, Case battlesPlinko: how the roll maps to a slot is not published. Arms Dealer: its code link returns 404. Coinflip and dice duel: no longer on the site.
Seed hash + client seed + nonce; Random.org ticket (battles)Covers: cases, king cases, upgrade, case battles, battle royale, RPS
Seed hash shown before the roll · Your own client seed · Nonce per bet · Random.org draw mixed in · Checker on the site · Public verify script · Formula published
RecomputedOpen in the checker: Case battlesCases and upgrade: no revealed seeds are public, so not reproduced. Battle royale reproduced (8 rolls) but not in the checker yet.
Seed hash shown before the roll · Nonce per bet · Random.org draw mixed in · Checker on the site · Public verify script · Formula published
RecomputedOpen in the checker: Crash, RouletteJackpot and coinflip: Go math/rand code that a browser cannot run as published; mines, tower and plinko: no public round history.
HMAC-SHA512 seeds + nonce, public hash with a salt; validator code on GitHubCovers: cases, upgrader, case battles
Seed hash shown before the roll · Your own client seed · Nonce per bet · Beacon (battles) mixed in · Checker on the site · Public verify script · Formula published
RecomputedOpen in the checker: Cases, Case battlesChecked against the sample rounds in its own validator code; no real revealed round was readable logged out.
HMAC-SHA256 + future EOS block (battles); separate case and dice tabsCovers: case battles, cases, catch the chicken, dice, rob mode, terminal +1 more
Nonce per bet · EOS block hash mixed in · Checker on the site · Public verify script · Formula published
RecomputedOpen in the checker: Case battlesCases, dice and chicken: same formula keyed with your own server seed, which is revealed only to you; not reproduced.
SHA-256 of server seed + first three bettors’ seeds (Wheel, Double)Covers: wheel, double, crazy wheel
Seed hash shown before the roll · Your own client seed · Checker on the site · Formula published
RecomputedOpen in the checker: Wheel, DoubleCrazy Wheel: the published calculator does not give the site's numbers; cases, upgrade, crash and mines: no published method.
SHA-224 hash of a secret drawn first (Classic only); other modes: checker by game IDCovers: cases, case battle, double, seasons, quests, classic (jackpot)
Seed hash shown before the roll · Checker on the site · Formula published
Seed hash shown before the roll · Your own client seed · Nonce per bet · drand beacon (Crash, Castle Roulette) mixed in · Checker on the site · Public verify script · Formula published
RecomputedOpen in the checker: Crash, Castle RouletteDice, mines, plinko and the other player-seeded games: the server seed is revealed only to the player, so not reproduced.
Seed hash + client seed + nonce; page and checker need a sign-in; formula only on CodeSandboxCovers: cases, case battles, upgrader, contracts, exchanger
Seed hash shown before the roll · Your own client seed · Nonce per bet · Checker on the site · Public verify script
Claims onlyThe formula is only on CodeSandbox, which refused our requests; public battle data has no nonce or roll.
Server seed, client seed, nonce + EOS block (own fairness page)
EOS block ID mixed in
Claims onlyRead on 17 Nov 2026: the page names a server seed, client seed, nonce and EOS block, but we did not record a formula. A re-read on 18 Nov 2026 was refused (HTTP 403), so whether it prints one is not confirmed.
"What you can verify" lists only what the source shows; a blank does not mean the feature is missing, only that we could not confirm it. "Reproduced by us" says whether our checker recomputes real results for the site (each formula was tested against rounds the site published), whether the site publishes a formula we could not test, or whether it only claims to be provably fair. "Tried" marks the date we tried and failed to read a site. The other 19 sites in the check (TRADEIT.GG, SkinOut, Skincashier, SkinsMonkey, SkinSwap, ShadowPay, WHITE MARKET, HaloSkins, Swap.GG, Mannco.Store, Skinport, WaxPeer, DMarket, LOOT.Farm, SkinBaron, BUFF163, Market.CSGO, SkinThunder, CS.MONEY) are marketplaces or trade sites with no games of chance, so there is no roll to prove.
What provably fair does not prove
That the odds are good. It proves a roll was not changed after the fact. A case can be provably fair and still return, on average, much less than it costs; see CS2 case site house edge.
That item values are fair. Case sites set their own skin values. A fair roll on an overvalued item is still worth less than it looks.
That the site pays out. Seeds say nothing about withdrawals, limits, KYC holds or whether the site will still be there next month (see closed CS2 gambling sites).
Games outside the scheme. Third-party slots and live casino games run on their providers' RNGs, not on the site's seeds. Several sites in the table cover only their own games.
Anything, unless someone checks. The protection only works if players verify rolls. It is weaker if the seed hash is shown only after you bet, or if you cannot set your own client seed.
Gambling with skins is gambling, and the expected result is a loss. 18+ only.
Questions
What does provably fair mean on a CS2 gambling site?
The site fixes the result of each roll before you bet, using a secret server seed it commits to by showing you its hash, plus a client seed and a counter (the nonce). After you change seeds it reveals the server seed, so you can recompute every roll and confirm none was changed after the fact.
How do I verify a CS2 case opening?
Note the hashed server seed, your client seed and the nonce of the opening. Rotate your seed pair so the site reveals the old server seed, check that its SHA-256 hash matches the hash you were shown, then run the site’s published formula (or its checker or public script) with the same seeds and nonce. You should get the same ticket number and the same item.
Which CS2 sites are provably fair?
Of the 41 CS2 and Rust gambling sites in our fairness check, CSGO.NET, CSGOEmpire, CSGORoll, DatDrop, RustChance, RustReaper, Skin.Club and SkinFans document a full system on their own site with a way to check past rolls (checked 18 November 2026). ChickenGG, CSFail, CSGOFast, CSGOPolygon, Duel, Gamdom and Howl.gg document it for some games only. The table above shows every site, what it uses and what you can check.
Is a provably fair site safe to use?
Not by itself. Provably fair only shows that a roll matches seeds fixed before you bet. It says nothing about the odds or house edge, the values the site puts on its skins, or whether it pays out withdrawals. Check the site’s licence, withdrawal record and terms as well.
Why do case battles use an EOS block or Random.org?
In a battle several players share one result, so one player’s client seed cannot be trusted to mix in randomness. Sites use public randomness nobody knows in advance instead: the hash of a future EOS blockchain block, or a signed Random.org draw with a serial number, so missing or repeated draws would show.