Snapshots & fairness
How holders, excluded accounts, commitments, and randomness are recorded.
Take a complete snapshot
Eligibility uses a finalized holder snapshot for the launch mint. Token accounts are aggregated by wallet, and the snapshot is checked against mint supply. Incomplete or inconsistent scans are rejected.
Program-owned pools, burn addresses, configured treasury wallets, and additional configured reserve accounts are excluded. A top-holders list is not a substitute for a complete eligibility snapshot.
Commit before randomness
A round commitment binds the mode, eligible-wallet snapshot, prize assets, purchase signatures, and selected randomness round. The stored hash makes later changes detectable.
The reward implementation verifies a future drand beacon against its expected network and round. It uses that verified randomness to select weighted raffle winners or distinct airdrop winners.
Inspect the proof
Collection links each delivered card to its draw record. The round API exposes the committed round data and proof needed to compare the snapshot, prizes, and selected recipients. Transaction signatures provide separate evidence for purchase and delivery.
The app must preserve the same committed draw through retries. A network timeout is not a reason to discard an unfavourable result or draw again.