Plinko guide
Titan Plinko: verify a drop yourself
Titan is the page's name and says nothing about the board. This is an exercise page: you take a set of example seeds and rebuild a 10-row drop on your own computer, step by step.
What you need
- The revealed server seed. For this exercise:
titan-check-seed-e47b. - Your client seed:
my-own-client-seed. - The nonce of the drop you want to check: 7.
- The row count: 10.
- Any tool that computes SHA-256 and HMAC-SHA256. Python's standard library is enough.
The steps
- Hash the server seed with SHA-256. Compare the result with the commitment that was shown before the drop. They must match exactly, character for character.
- Build the message
my-own-client-seed:7:0(client seed, nonce, round number). - Compute HMAC-SHA256 of that message, using the server seed as the key.
- Split the 32-byte result into eight 4-byte chunks. Turn each into an integer and divide by 2^32.
- You need 10 floats but the first digest gives 8. Repeat steps 2 to 4 with round 1 and take the first 2 floats from it.
- For each float, write R if it is 0.5 or more and L otherwise. Count the R entries; that count is the slot.
- Look up the slot in the pay table that was in force and confirm the payout.
| Server seed (revealed later) | titan-check-seed-e47b |
|---|---|
| Commitment shown before play: SHA-256(server seed) | 44f87c8404d9f009c721a41c752aa086014294cec6df738d95619071011a3ae9 |
| Client seed : nonce : round | my-own-client-seed:7:0 |
| HMAC-SHA256(server seed, message) | 95d36b59fa791c0a8961a279dcde9f3df5fcf13980233e024e0551a48421cecd |
| First 4 bytes (8 hex digits) | 95d36b59 = 2,513,660,761 |
| Float = value / 2^32 | 0.5852572529 |
| 10 floats, one per row (>= 0.5 goes right) | RRRRRRLRLR |
| Final slot = number of R | 8 |
One common construction, shown for teaching. Real services document their own message format; check theirs before verifying.
A short script
import hashlib, hmac
server, client, nonce, rows = "titan-check-seed-e47b", "my-own-client-seed", 7, 10
print(hashlib.sha256(server.encode()).hexdigest())
floats, rnd = [], 0
while len(floats) < rows:
d = hmac.new(server.encode(), f"{client}:{nonce}:{rnd}".encode(), hashlib.sha256).digest()
floats += [int.from_bytes(d[i:i+4], "big") / 2**32 for i in range(0, 32, 4)]
rnd += 1
path = "".join("R" if f >= 0.5 else "L" for f in floats[:rows])
print(path, path.count("R"))
Run it and compare the output with the figure above. The commitment should start with 44f87c8404d9, and the slot should be 8. If you change a single character of either seed, the path changes completely.
If your result does not match
Most mismatches come from formatting, not foul play. Check the separator characters, whether the nonce starts at 0 or 1, whether the round counter exists, and how bytes become floats. A service that supports verification documents its own format; this exercise shows one common construction. If everything follows the documented format and the result still differs, that drop cannot be verified.