Docs
Browse documentation

Start here

Product

Trust and safety

Reference

DocsProduct

What is and is not player-verifiable#

The current MVP exposes rules and results, but not enough cryptographic evidence to reproduce how an outcome was selected.

What a player can inspect#

  • The published 20 paylines and scaled paytable.
  • Symbol behavior, free-spin rules, feature tiers, collection rules, and regular cap.
  • The 92% regular and 2% progressive targets.
  • The returned grid and frame timeline for a settled spin.
  • Line wins, SCATTER and BONUS counts, awarded features, payout, and balance change.
  • Recent server ledger entries for the active session.
  • Whether retrying the same request ID returns the stored outcome.
  • Public simulation progressive state, including visible value, bounds, version, and hit history.
  • On-chain mainnet transaction effects when the relevant public signature is available.

These observations can reveal an arithmetic or disclosure mismatch.

What a player cannot prove today#

A player cannot currently prove:

  • which random bytes were selected before a spin;
  • that the server committed to those bytes before receiving the wager;
  • that a hidden progressive trigger was fixed before contributions approached it;
  • that an operator could not regenerate or discard an outcome;
  • that the deployed server exactly matches the reviewed repository source;
  • that all historical spin records are complete and unaltered; or
  • that the theoretical return has received independent certification.

Missing proof material#

The MVP has no player-facing:

  • server-seed commitment hash;
  • client-selected seed;
  • monotonically increasing fairness nonce;
  • retired seed reveal;
  • versioned seed-to-random-byte algorithm;
  • unbiased range-conversion specification;
  • result digest;
  • progressive-trigger commitment;
  • downloadable transcript; or
  • one-click verifier.

The server ledger is application-controlled SQL state, not a public or tamper-evident fairness proof.

Claim boundary#

Afterlife must be described as server-authoritative and not yet player-verifiably provably fair. “Uses cryptographic randomness,” “replay-safe,” and “published math” each describe a useful but narrower property. None is a substitute for a complete verification system and independent review.

No current documentation should claim that Afterlife is provably fair, audited, certified, or guaranteed fair.

Next: Verification roadmap.