Snowballin' · POWDER DAY (1,000× top)

All-time

first round 20d ago · last 20d ago

How it's built

A 6×6 cluster tumble where snowballs roll the slope, grow a size for every cell of snow they cross, and pay the frozen cash they collect times their size; three lift passes open a hold-and-win feature that ends in one roll across the whole board. The round is the whole bet: base spin and feature settle as ONE leaf. The trees were measured from the forward engine (40M base spins, 4M snowball spins, 1.5M of each POWDER DAY); every leaf is a total the engine pays exactly (the natural mass between committed awards is split onto its neighbours with the mean kept), then winning outcomes are scaled together, or a bought feature tilted, until the root lands on exactly 985000ppm. Leaves nest into chance nodes of at most 32 by probability, so rare awards sit deeper. Four ladders from one engine: the base spin at 4000× / 2500× / 1000× / 500× / 250× / 100× tops, a 5× snowball spin, and the 100× and 200× feature buys; the stake plays the deepest tree the pool seats. The screen performs the settled leaf with a seed whose whole bet pays exactly it. The 191–207 trees are an earlier engine, retired before any round was played.

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 game tree

The whole game as the contract holds it, reconstructed from the sealed on-chain words at render time. Hover any node: green-filled nodes are chance (the seed decides), outlined nodes are decisions (you decide), colored endpoints are payouts. This object is what was submitted for edge-checking — the contract never learned the rules, only this shape.

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.