Verification roadmap#
Player-verifiable fairness is Planned. The implementation and review sequence should be explicit before the claim changes.
1. Freeze the mathematical specification#
Publish a versioned specification for:
- reel weights and without-replacement selection within each visible reel;
- the 20 line paths and paytable;
- WILD, SCATTER, and BONUS behavior;
- free-spin and fixed-jackpot tier selection;
- Collect 12 tier selection and meter rollover;
- payout flooring and the 2,000× regular cap; and
- progressive contribution, trigger, payout, reserve, and reset rules.
2. Define the random transcript#
Every random decision needs a stable position in a deterministic transcript. The specification must define how bytes are expanded, consumed, rejected to avoid modulo bias, and mapped to symbols or weighted tiers.
The transcript must remain deterministic even when a spin awards a variable number of free spins or collection prizes.
3. Commit before play#
Publish a cryptographic hash of an unrevealed server seed before accepting spins. Associate each settled spin with:
- a server-seed identifier and prior commitment;
- a player-controlled client seed;
- a monotonic nonce;
- an algorithm version; and
- a result digest.
4. Reveal and verify#
Rotate server seeds under a published policy, reveal retired seeds, and provide an open verifier that can reproduce the complete historical outcome and payout from the saved inputs.
The verifier should run independently of the Afterlife server and show failures clearly.
5. Handle the shared progressive separately#
A shared, hidden must-hit trigger spans many players and spins. Its commitment must be fixed before relevant contributions and remain verifiable after a hit without exposing the active trigger early. The design must specify reset ordering, pool versions, concurrent contributions, and what happens after failed or retried settlements.
6. Bind source to deployment#
Document the reviewed build, deployed artifact, configuration, and change process. A correct open-source verifier does not prove that an unrelated deployment used it.
7. Independent review#
Before making a provable-fairness claim, obtain scoped review of:
- theoretical game math;
- random construction and transcript;
- server and verifier implementation;
- progressive concurrency and accounting;
- build and deployment controls; and
- player-facing disclosure accuracy.
Decision required — verification standard: Select the construction, hash and derivation primitives, seed-rotation policy, client-seed behavior, progressive commitment design, reviewer, published artifacts, remediation process, and acceptance criteria.
An audit statement must identify the reviewer, scope, version, limitations, and date. See Roadmap.