Same provably-fair seed for every player. Pure bankroll-management skill ranks the field. New game every Monday 00:00 UTC.

Weekly challenge · ISO week 22 2026

Plinko · same committed sequence

Every player gets the same provably-fair sequence and the same starting bankroll (1,000.00). Up to 100 bets. The leaderboard accepts only scores replayed and verified server-side.

Time remaining
3d 07h 00m
Server seed
hidden in REST; browser beta uses it locally
Seed hash
100207ed2e85d3bb4454322f...
Client seed
0225f8e8f2c92943
Starting bank
1,000.00
Max bets
100

Play

The widget below auto-uses this week's challenge state. This browser-play beta exposes the active seed to the game client so the simulator can run; public REST keeps the seed hidden until close, and ranking still comes only from server replay. The next hardening step is a server-play API that never sends active seeds to browsers.

Plinko

Drop the ball through rows of pegs. Each row consumes one HMAC float (<0.5 = left, ≥0.5 = right).

Bankroll
Bets0
Win %
Net P/L
Streak
Biggest win
Pick rows + risk profile, drop a ball.
Presets
Auto-bet
How dishonest operators rig this game 4 documented tricks
01 Path animation ≠ actual bucket

Mechanism. Operator decides the bucket up-front, then animates a "convincing" path to it. The visual path you watched is fake — bets are bound to the final bucket only.

Red flag. Each row should consume exactly one HMAC bit/byte deterministically. Replay the bytes and trace L/R yourself — visual must match.

02 "Lucky bucket" pre-highlight

Mechanism. Before the drop, a "hot" bucket is highlighted to tempt you to bet bigger. The highlight is randomized, not predictive.

Red flag. Hot buckets that "happen" to land on your bigger bets disproportionately are statistical fingerprints of rigging.

03 Multiplier ladder swap

Mechanism. Same risk profile shows different multipliers session-to-session. Heavy session = lower multipliers; cold session = higher (to keep you hooked).

Red flag. Screenshot the payout table at start of session. Compare to end. Any change = silent recalibration.

04 Ball weight bias

Mechanism. Animation uses a "ball" that visibly drifts toward outer (low-mult) buckets in slow-motion replay. The float-determined path is honest; the WEIGHTING ad displayed differs.

Red flag. Same algorithm describes ball physics — there should be no operator parameter "weight" or "elasticity" that the player can't see.

For the full compendium across all games, see The Book of Casino Dirty Tricks.

Server seed hash
Server seed (revealed after rotation)— pending rotation —
Client seed
Next nonce

Submit your score

Pick a nickname (2+ chars). One verified submission per browser/IP per week - re-submit to overwrite if the server-replayed score improves.

Leaderboard

  1. Loading…

Why “same seed for everyone” is the only honest leaderboard format

Every other gambling leaderboard mixes two things that should never mix: luck and skill. When two players gamble on different rounds and one wins more than the other, you can’t tell whether that’s because they made better decisions or because their RNG was kinder. The leaderboard is meaningless.

Our weekly challenge fixes that by giving every participant the same provably-fair seed. The outcomes are identical for every player. The dice rolls, crash multipliers, mine positions — bit-for-bit the same. The only thing that varies between players is decisions: bet sizing, stopping rules, target multipliers. Whoever finishes the week with the highest bankroll didn’t get lucky. They made better decisions against an identical opponent.

How the verification works

The week’s server seed is revealed on the dashboard from day one. That’s not a security hole — it’s the entire point. You can re-derive every single outcome the simulator would produce, sketch out an optimal strategy on paper, and then play the actual sequence. The challenge is a deterministic strategy puzzle, not a guessing game.

After the week ends, every submission is verifiable:

  1. The published server seed plus the (also-public) client seed define the exact byte stream.
  2. The player’s nonces 0 through N define which outcomes their N bets used.
  3. Their bet sizes are submitted alongside their final bankroll.
  4. Re-deriving the outcome at each nonce and applying the submitted bet sizes must produce the submitted final bankroll. If not, the submission was fabricated.

For v1.1 we’ll auto-verify every entry. For now, all submissions are marked unverified until an admin spot-checks. Submissions that don’t reproduce get removed.

Strategic considerations

Since the outcome sequence is fixed, you can game-plan in advance. Some thoughts:

  • The optimal strategy for a deterministic Crash sequence is trivial if you know the future: bet the entire bankroll on each round and cash out one penny before each bust. The game becomes finding that strategy mentally as you play.
  • Real strategy comes from bet-sizing constraints: you don’t have infinite reaction time. Pre-committing to cashout targets and bet sizes that survive the worst run in the sequence is the dominant approach.
  • Use the Monte Carlo simulator to test sizing strategies against your bankroll. The challenge gives you ONE sequence — but the best strategies are robust across many sequences.

Frequently asked questions

Why doesn’t the operator hide the server seed like a real casino?

Because this isn’t a casino — it’s a strategy lab. Hiding the seed would turn the challenge into “guess the outcomes correctly”, which is impossible (the seed is genuinely random). Revealing it makes the puzzle about optimal play against a known sequence — that’s the entire point.

Can I submit multiple times?

You can re-submit, but only your highest final bankroll is kept per browser per week. Submissions are tied to a hash of your IP address. Use a different network if you want to try with a fresh slate.

What happens to my localStorage state at week’s end?

Nothing — your bankroll and bet history stay in your browser. The week’s challenge state is keyed by challenge ID. When a new challenge starts, you get a fresh bankroll for the new sequence.

Why does the game rotate?

Different games reward different strategy types. Crash rewards risk discipline. Dice rewards bankroll sizing. Mines rewards stopping rules. Rotating through all nine over time exposes the full strategy surface — and prevents any single optimal strategy from dominating the leaderboard forever.