Provably fair

How verification works

Every day we publish a SHA-256 commit hash of a freshly generated server secret before any pack opens against it. Once the day's epoch closes, we publish the original secret. Anyone can re-hash the secret and confirm it matches the original commit — proof that the secret existed before any rip and was never altered.

The same secret feeds into the per-pack RNG, alongside the on-chain pack_config_hash and your client seed. That means the entire result chain — odds, randomness, outcome — can be replayed independently.

Openings on the OPENv2 protocol go one step further: the RNG also mixes in a public randomness beacon from drand — specifically, the first beacon published after your payment settled. That value didn't exist when your purchase was locked in, so no one — not even Gacha Arcade with the server secret in hand — could compute your outcome in advance. Each opening's receipt shows which protocol version it used, and the beacon is independently verifiable against drand's public network.

Read the deeper walkthrough on How it works, or run a verification yourself in the standalone verifier:

• Open the public verifier

Provably fair

Before any pack opens on a given day, we publish a fingerprint of the secret that will decide its results. Afterwards we publish the secret. Anyone can hash it and see that it matches the fingerprint from before, so the secret cannot have been chosen to suit your pull.

The commitment is published before a single pack in that day opens. Your result is then computed from that secret, and on the current protocol from a public randomness beacon that only exists after your payment settled. Afterwards the secret itself is published: hash it yourself and you get the commitment from before.

Verifiable randomness

Each pack opening uses a verifiable randomness source, a pre-committed daily server secret and, on the OPENv2 protocol, a public drand randomness beacon published only after your payment settles, to produce an unpredictable result.

Locked pack configuration

Pack contents and odds are committed before you rip, so they cannot be adjusted based on who is buying.

Deterministic selection

The random result is applied to the committed configuration to select your pull.

Public verification

Verification data is available so results can be audited and checked for consistency.

Key guarantees

• Odds are locked before you rip
• Outcomes cannot be predicted ahead of time
• Results are tamper-resistant and verifiable