Calculate the published ticket algorithm with disclosed inputs.
Reference
Reference implementation of the published algorithm. We have not yet obtained a revealed server seed for a captured round, so recorded rounds have not been cryptographically replayed.
Enter the full hash saved before play. A hash copied afterwards does not establish earlier timing. Why timing matters
All calculations run in your browser. Seeds are not submitted, placed in the URL or included in replay analytics. This is not a payout, cashback or currency-settlement check.
How the published Plinko algorithm works
Duelbits hashes the UTF-8 text serverSeed:clientSeed:nonce with SHA-256. The first eight hex digits become an unsigned 32-bit integer. Modulo 65,535 gives a ticket from 0 to 65,534. The saved commitment is SHA-256 of the server seed text.
Plinko v2 scope
The published algorithm calculates a ticket, not a left/right path. Current v2 path, slot and payout mapping have not been validated with disclosed seeds. Observed API paths alone do not establish that mapping.
What you can check today
Enter a revealed server seed, client seed and nonce to calculate the published ticket and compare the seed with your saved hash. The verifier stops there: it does not map the ticket to a slot or payout. We have not yet obtained a revealed server seed for a captured round; independent reference tests are not disclosed-round evidence.
The published algorithm is implemented and tested, but our captures do not contain revealed server seeds needed to replay recorded rounds. A successful synthetic example does not supply that evidence.
Can the saved server hash reveal the original seed?
No. The operator must disclose the previous seed. A hash alone does not allow a result to be reconstructed.
