Stake.us Diamonds Verifier
Recompute the 5 gems dealt for one bet on Stake.us from the server seed, client seed and nonce. Same HMAC-SHA256 stream the operator publishes, run in your browser.
Verification Inputs
Recomputes as you type. Nothing leaves your browser.
Diamonds Result
Paste the server seed and client seed from the bet. The diamonds result appears here as you type.
The byteGenerator, float conversion and every per-game event mapping were confirmed identical to Stake.com (14 of 14 claims, research/platform/tools/tool-finesse-audit/STAKE_COM_VS_US_2026-08-17.md). Roulette is not in that confirmation set, so it has no Stake.us route yet.
How Stake.us derives a Diamonds result
From float to result
What to compare
Where the seeds are
bytes = HMAC_SHA256(key = serverSeed, msg = clientSeed:nonce:round) // round starts at 0float = b0/256 + b1/256^2 + b2/256^3 + b3/256^4 // 4 bytes per floatresult = game event mapping applied to the floats, in orderOther Stake.us games
Keep what you worked out.
A free account saves your bankroll plans, sessions and the results you run here, on every device. No card, no upsell.
Frequently Asked Questions
Why are pairs so common?
With 7 gem types and 5 independent draws, most hands contain at least one repeat. The payout table is built around that.
Does the order of the gems matter?
Not for the payout, which counts matches. It matters for verification, because the order is the order the floats were consumed.
Which Stake.us algorithm does this use?
Stake.us, Provably Fair: Game Events (identical scheme to Stake.com), read 2026-08-17. The byte stream is HMAC-SHA256 of clientSeed:nonce:round keyed by the server seed, converted to 4-byte floats, then mapped to the 5 gems dealt.
Do my seeds leave the browser?
No. The HMAC and SHA-256 run with the Web Crypto API on your device. The share link carries the seeds only because you copied it.
