Recompute the Plinko path and landing bucket from your revealed seeds. Set the row count to exactly what the round used.
Computed locally via the Web Crypto API (HMAC-SHA256) — no server call. Your seeds and nonce never leave your device. It's the same code we test against Stake's own calculator.
In Plinko a ball drops through rows of pegs, bouncing Left or Right at each one; the bucket it lands in is simply the number of Rights. One float decides each row, so an 8-row drop uses 8 floats, a 16-row drop uses 16.
The result comes from the standard Stake-style byte stream:
HMAC-SHA256( key = server_seed , message = "client_seed:nonce:round" )
For each of the rows floats: f < 0.5 → Left, otherwise Right. The bucket index is the count of Rights (0 … rows):
path = [L/R for each row]
bucket = number of R's → 0 … rowsThis count-of-Rights is algebraically identical to Stake's slot index for rows 8–16.
Each row consumes one float: below 0.5 is Left, at or above 0.5 is Right. The landing bucket equals the total number of Rights.
Almost always the row count. You must set exactly the same number of rows the round used — a different row count gives a different (but still correct) result.
Yes. More rows means more floats consumed and a different path, so always match the round's row setting.
Any Stake-style casino — Stake, Rainbet, Roobet, BC.Game, Shuffle and others share the same Plinko engine.
Formula verified bit-for-bit against Stake's reference calculator (Aug 2026). Other games: Dice · Limbo · Plinko · Mines · Keno · all verifiers. Open methodology: /methodology/. © FairPlay Audit — independent, free, open-source.