BC.Game Plinko verifier

Replay a revealed Classic drop from its seeds, nonce and row count. Your inputs stay in your browser.

Verified Four captured rounds with a pre-bet seed commitment · seven additional replays · Classic tables captured October 20, 2026.

BC.Game · algorithm v1 · table 2026-10-20 · verified

Normal Classic mode only. Choose Regular, High or Nightmare as recorded for your bet. Lightning and Left/Right side bias are not supported.

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

Classic table captured on 2026-10-20. Four recorded rounds matched a pre-bet commitment and later seed disclosure. Confirm the mode and table match your bet.

From seeds to the result

  1. Enter the revealed server seed, client seed and exact nonce for the completed bet. The hashed active seed cannot reproduce an outcome.
  2. The official scheme computes HMAC-SHA512 with the server seed as a UTF-8 key and clientSeed:nonce as its message. It uses one 64-byte block, without a round suffix.
  3. Each four-byte group becomes a fraction between 0 and 1. A value strictly greater than 0.5 means right; all other values mean left.
  4. The number of right turns gives the zero-based slot. The selected Classic table supplies the multiplier.
  5. Enter a server seed hash saved before play to compare the revealed seed with that commitment.

Evidence and limits

Four captured 12-row Regular/Classic rounds, with nonces 0-3, matched the full paths, slots and payouts. The complete server seed hash and client seed were recorded at 12:25:03 UTC on October 20, 2026, before the first captured bet at 12:25:24 UTC. After rotation, the disclosed seed matched that saved hash. This evidence supports Verified status for this Classic replay adapter.

Seven additional captured outcomes matched with 11, 13 or 16 rows and High risk. Their commitment provenance is weaker and is documented separately in the test vectors; they are not treated as pre-bet evidence. Verified describes our replay checks for the named adapter, not a casino endorsement, proof of real-money settlement or verification of every operator game.

The payout snapshot covers 27 normal Classic configurations: 8-16 rows with Regular, High or Nightmare risk. These are BC.Game’s labels. Lightning, Left and Right side bias, and legacy payout tables are excluded. Choose the exact mode and version recorded for your bet; older bets may have used different tables.

See what provably fair checks can establish, calculate this table’s RTP or simulate its distribution.

Sources and reproducible tests

BC.Game: 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.
BC.Game adapter status: verified. Four captured Classic rounds matched a pre-bet seed commitment, full paths, slots and payouts. Seven additional outcomes replayed.

FAQ

Which BC.Game modes are supported?
Normal Classic mode with 8-16 rows and Regular, High or Nightmare risk. Lightning and Left/Right side bias require separate replay and payout rules and are not supported here.
Can I enter the hashed server seed?
Use the revealed server seed in the server seed field. A saved pre-bet hash belongs in the optional hash field. A matching hash alone does not verify the path or payout.
What does Verified mean here?
Four recorded Classic rounds matched their complete paths, slots and multipliers using a server seed whose hash and client seed were captured before play and checked against the later disclosure. The label applies to this replay adapter. It does not certify the casino, withdrawals, real-money settlement, Lightning or biased modes.
Why might my multiplier differ?
Check the row count, exact risk label, Classic mode and table version. BC.Game has other modes and legacy tables; this tool only uses the explicit Classic table snapshot from October 20, 2026.
Are my seeds sent to a server?
No. Hashing and replay run in your browser. Seeds, nonces and paths are not sent to our API or analytics.