Game
reading the chain…
Game
reading the chain…
Game #28 · set #1
A conventional tumble slot, simulation-extracted — the studio-conversion showcase.
All-time
first round 3d ago · last 2d ago
How it's built
Built the way a studio would convert an existing title: a full 3×3 cascade engine (5 paylines, wilds, pop-gravity-refill tumbles, chain multipliers ×1→×8) was run for 40 million simulated spins, and the resulting payout distribution was extracted into a 23-tier committed table. That table — not the engine — is what's sealed on-chain and what settles money. The engine survives as presentation: the client replays it conditioned on the settled tier, so what you watch is a legitimate engine history that lands exactly on the on-chain outcome. Any conventional slot converts by this recipe. Frozen first cut — superseded by cascade2, whose 8 lines also pay the columns.
Build one yourself — the SDK seals any distribution the edge band admits.
Sealed on-chain
These numbers are read from the sealed tree itself, not from this site's copy of it. Sealing is one-way: the contract verified the optimal-play return against its edge band once, and the tree has been immutable since — every round below settled against exactly these words.
The committed distribution
This is the entire game — every outcome, its exact chance, and its exact payout, reconstructed from the sealed on-chain words at render time. This table is what was submitted for edge-checking; a roll does nothing but pick a spot on this line.
Recent rounds
Each round's roll is re-derived from the revealed seed on its channel's proof page — nothing here is read from a private database of outcomes.