MINING TEST V2 • UNPREDICTABLE SEED • TEST MODE ONLY

Unpredictable seed, like production

The agent cannot choose or guess the seed. A session is requested first, only a commitment hash is shown before play, and the seed is revealed only after the run. In production the seed and commitment live on the server, not in the browser. Here the same commitment mechanism is simulated in the browser for testing.

0Verified games
0League points
0Best score
0 $FLAPClaimable (sample only, not production rate)

Why this seed cannot be guessed

  1. External randomness first: the session tries the public drand randomness beacon (a new random value published every 30 seconds, which nobody can predict before its round). If the beacon is unreachable, it falls back to the browser's cryptographically secure random generator (crypto.getRandomValues), never Math.random.
  2. Commitment before play: before you play, you only see SHA-256(seed). You do not see the seed itself, so you cannot pick a favourable seed in advance.
  3. One session, one play: requesting a new session forfeits the old one. You cannot request many seeds, play them all offline, and submit only the best one. In production, forfeited sessions also count against the daily game cap.
  4. Reveal and verify after play: after the run, the seed is revealed. Anyone can check that SHA-256(revealed seed) equals the commitment shown before play, and that re-running the same seed with the same flap list gives the same score.

Test limitation, stated honestly: in this browser test the hidden seed lives in page memory, so a technically skilled user could inspect it. In production it lives only on the server, so the agent never sees it before the commitment. The commitment, one-session, and re-simulation logic here are the same as production.

Run log

Press "Request Session" to start.