What you need for a Plinko fairness check
A Plinko verifier checks the chain from disclosed inputs to directions, from directions to a final slot, and from the slot to a selected payout table. The exact conversion is operator-specific. Select the adapter corresponding to the operator and game mode used for the recorded bet; a visually identical board is not enough to choose the algorithm.
For the balanced adapters supported here, each row contributes a left or right direction and the slot is the count of right turns. Risk changes the table lookup rather than the generated path. The row count still matters because it determines how many directions the replay consumes.
Collect the inputs from the same bet and seed pair
Use the revealed server seed, recorded client seed and exact nonce. If you recorded a server seed hash before playing, keep that value for the commitment check. The active seed counter shown in settings may already have advanced beyond the nonce of the bet you are checking, so use the bet record rather than guessing the previous counter.
Record rows, risk and any special mode separately. The multiplier explorer shows the captured tables, but an older bet may need a different snapshot. A correct path with a different payout should prompt a configuration check rather than an immediate conclusion about randomness.
| Field | Use | Avoid |
|---|---|---|
| Server seed | The revealed seed for the completed seed pair. | Pasting only its active hash. |
| Client seed and nonce | The exact recorded strings and whole-number nonce. | Guessing whether a missing nonce means zero. |
| Rows, risk and mode | The settings used for that round. | Substituting a similarly named configuration. |
| Commitment and result | Saved hash, path or slot, and payout where available. | Treating a newly calculated hash as pre-bet evidence. |
Understand the adapter's evidence label
BCH.games and BC.Game have independently captured replay evidence within the scopes documented by their adapters. BC.Game coverage is for Classic normal mode; Lightning and directional-bias modes are outside the current implementation. Stake uses a documented reference implementation with historical community examples and remains Reference.
Those distinctions concern the evidence for replaying the supported algorithm. They do not assign an overall trust score to an operator. The operator profiles and methodology explain where the recorded data ends.
Read a successful replay in context
A replay match says that the supplied inputs produce the displayed outcome under the selected implementation. A matching saved pre-bet hash also ties the revealed seed to that recorded commitment. These checks are useful because the full result can be recomputed rather than accepted from an animation or a screenshot.
The same checks do not predict the next seed, remove the house edge or verify account settlement. Use Plinko odds for probability questions and the comparison for captured payout configurations. The verifier addresses a different question: whether the recorded round is consistent with its stated inputs and algorithm.