Stake Plinko Verifier
Recompute the ball path and landing bucket for one bet on Stake 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.
Plinko Result
Paste the server seed and client seed from the bet. The plinko result appears here as you type.
Read from the Wayback snapshot of 2025-07-19 (the live page challenges non-browser fetches); saved at research/casinos/stake/evidence/provably-fair-game-events-wayback-20250719.txt. Crash is verified on its per-seed curve only: live multiplayer Crash rounds come from a public hash chain, not your seed pair.
How Stake derives a Plinko 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 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 does the ball rarely reach the edge buckets?
Reaching the leftmost bucket needs every row to go left, a 1 in 65,536 event at 16 rows. The distribution is binomial, which is why the centre pays least.
Does the risk level change the path?
No. Risk only changes the payout table under the buckets. The path is the same for the same seeds and nonce.
Which Stake algorithm does this use?
Stake, Provably Fair: Game Events, read 2026-09-20. The byte stream is HMAC-SHA256 of clientSeed:nonce:round keyed by the server seed, converted to 4-byte floats, then mapped to the ball path and landing bucket.
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.
