Stake Plinko verifier

From seeds to a Plinko path

1. Use the revealed server seed and the client seed, nonce and row count recorded for your bet. A hash of an active server seed cannot reproduce its outcomes.
2. The reference implementation computes HMAC-SHA256 using the server seed as a UTF-8 key and clientSeed:nonce:round as the message, starting at round 0.
3. Each group of four bytes becomes a number between 0 and 1. Below 0.5 means left; 0.5 or above means right. After eight directions, the next HMAC block supplies the remaining rows.
4. Count the right turns to get the zero-based slot. Compare the displayed path and slot with your recorded bet.
5. If you saved the SHA-256 server seed hash before play, enter it in the optional hash field. A match confirms the revealed seed matches that saved commitment.

What reference status means here

We reproduced Stake’s documented scheme and matched the full paths of three user-reported rounds published on October 9, 2018, with 8, 11 and 16 rows. Those reports have no recorded pre-bet hash, and they were not independently captured by ProvablyHero. They do not establish today’s Stake implementation or payout tables.

This tool checks a hash, path and slot, then looks up a multiplier in Stake’s payout tables captured on October 20, 2026. All 36 configurations are available: 8-16 rows and low, medium, high or expert risk, using the API’s original risk names. Risk affects the multiplier, not the path. This snapshot does not establish which table applied to an older bet or confirm real-money settlement. Read what provably fair checks can establish.

Sources and reproducible tests

• Stake’s random-number generation and byte-to-float conversion.
• Stake’s Plinko direction mapping.
• Historical community reports from 2018.
• Engine test vectors and provenance.