Plinko guide
Eagle Plinko: commit, reveal and rotate
Eagle is the name on this page and has no meaning for the game itself. The topic is the commit-reveal scheme that lets a plinko drop be checked after the fact, and why seeds get rotated.
The problem commit-reveal solves
A drop's path is fixed by a secret server seed. If the service could choose that seed after seeing the bet, it could steer results. If it showed the seed before the bet, a player could compute every drop in advance. Commit-reveal avoids both problems. The service picks the seed first, publishes only its SHA-256 hash (the commitment), and reveals the seed itself later. Anyone can then hash the revealed seed and confirm it matches.
| Server seed (revealed later) | eagle-serverseed-5c19 |
|---|---|
| Commitment shown before play: SHA-256(server seed) | ad0d1fc3ac2781cedf1098cce0effdf4f63f04ce44f0c93b1a0f9cd1fde9dbb7 |
| Client seed : nonce : round | eagle-client-x7:3:0 |
| HMAC-SHA256(server seed, message) | d050d09441f8f5deae1af90620c6c8b9d8118e0beb736c4f1de9d8bf0eefb516 |
| First 4 bytes (8 hex digits) | d050d094 = 3,494,957,204 |
| Float = value / 2^32 | 0.8137331354 |
| 8 floats, one per row (>= 0.5 goes right) | RLRLRRLL |
| Final slot = number of R | 4 |
One common construction, shown for teaching. Real services document their own message format; check theirs before verifying.
The three inputs and what each guards
- Server seed
- Secret while in use. Its hash is the commitment. It stops players from predicting drops, and the commitment stops the service from changing it.
- Client seed
- Chosen or changeable by the player. Because it enters the HMAC message, the service cannot have tuned the server seed against it in advance.
- Nonce
- A counter that goes up by one per drop. It makes every drop under the same seed pair different, without needing a new seed each time.
| Nonce | Bounces (8 rows) | Slot |
|---|---|---|
| 0 | RRLLRLRL | 4 |
| 1 | RLRRLRLL | 4 |
| 2 | RLRRRLRR | 6 |
| 3 | RLRLRRLL | 4 |
| 4 | RLLRLLLR | 3 |
The figure shows five drops from the same server seed and client seed. Only the nonce differs, yet the bounce strings bear no relation to one another. That is the job of the hash: a one-character change in the message gives an unrelated output.
Rotation: ending one commitment and starting the next
A server seed cannot be revealed while it is still in use, or every later drop would be predictable. So services rotate. When a player asks for a new seed pair, the service reveals the old server seed, publishes the hash of a fresh one, and resets the nonce to 0. For example, the next seed in this demo, eagle-serverseed-next-90ad, would be announced only by its hash, which starts ba81d79265122b07. The old seed, now revealed, lets every past drop be checked.
What the scheme does not do
- It does not change the odds. The slot chances and the pay table's return stay exactly as they were.
- It does not prove the pay table is generous; it only shows that the drop was not altered after the bet.
- It relies on you actually checking. The hash fairness guide has the general steps.