BCH.games Plinko verifier

Paste the revealed server seed, your client seed and the nonce. We replay the drop in your browser.

BCH.games · algorithm v1 · table 2026-10-17 · verified

Paste the revealed server seed and your client seed to replay the drop.

How BCH.games turns seeds into a drop

  1. Before you play, BCH.games shows the SHA-256 hash of its server seed. The seed itself stays hidden.
  2. For each bet it computes HMAC-SHA256 with the server seed as the key and client seed:nonce:round as the message, for round 0, 1, … Each result gives 32 bytes.
  3. Every four bytes make one float between 0 and 1: b0/256 + b1/256² + b2/256³ + b3/256⁴. One float per row: below 0.5 the ball goes left, from 0.5 it goes right.
  4. The slot is the number of rights. The multiplier is the table value for your rows, risk and slot.
  5. When you rotate the seed pair, BCH.games reveals the old server seed. Its hash must match the one you saw before play, or the seed was changed.

What a match proves, and what it doesn’t

A replay match shows that the supplied seeds and nonce produce the displayed result under this adapter. If the revealed seed also matches a hash you saved before the bet, that ties the replay to the recorded commitment. It doesn’t establish anything about bets you haven’t checked, or confirm the historical payout table: compare the multiplier with what you were paid. More in what provably fair actually proves.

Save the configuration with the bet record

The nonce identifies a bet within a seed pair; it is not a count to guess from the visible history. Use the recorded client seed and nonce of the completed bet. Seed spelling and case matter. An active server seed hash belongs in the optional commitment field, not in the revealed server seed field. A hash alone cannot recreate the hidden input.

Match the row count and risk as well. The slot is determined by the path, while the payout is looked up in the selected table. A historical bet can require a different snapshot from the one currently captured. The multiplier explorer and BCH.games profile show the source context behind the current calculation.

Use the replay for the question it answers

This check is retrospective and local to your browser. It does not predict the next path, assess account settlement or remove the house edge. If the question is how likely a result is, use the calculator. If it concerns a session balance, use the simulator. Those tools model probabilities and sessions rather than reconstructing a particular casino bet.

BCH.games: separate the replay checks
StageCompareLimit
CommitmentRevealed seed against your previously saved hash.A hash created after disclosure is not a saved pre-bet commitment.
OutcomeReproduced path and slot under adapter v1.Only the documented mode and input format are covered.
PayoutThe recorded multiplier against the applicable captured table.A snapshot lookup is not confirmation of real-money settlement.
BCH.games adapter status: verified. Matched independently captured disclosed rounds. Path, slot and payout-table lookup.

FAQ

Do you store my seeds?
No. The replay runs entirely in your browser; the seeds are never sent to our servers.
Where do I find the revealed server seed?
In BCH.games' fairness settings. Rotate the seed pair: the old server seed is revealed and its bets become verifiable. Bets on the current seed can't be checked yet.
The result doesn't match. What now?
Check that you pasted the revealed (not hashed) server seed, the client seed of the same pair, the exact nonce of that bet, and the rows and risk you played. If it still doesn't match, send the details to hey@provablyhero.com.
Does the nonce start at 0?
Yes. The first bet on a new seed pair has nonce 0, and each bet adds one.