Fairness you can verify yourself.
Every Apex round is built on cryptographic commitments — seeds, hashes and nonces that let any player, operator or auditor reproduce the result independently.
How outcomes are generated
Each round combines a server seed (committed in advance via SHA-256 hash) with a client seed contributed by the player and a per-round nonce. The result is deterministic and reproducible.
Verification process
After every round, the server seed is revealed. Players can verify the hash matches the pre-committed value and re-compute the outcome with the public verifier — independently of Apex.
RTP philosophy
RTP and volatility ranges are documented per title and operator-configurable within certified bounds. No hidden hold, no opaque adjustments mid-session.
Security principles
Round seeds are generated in HSM-backed environments. Hashes are committed before any player action. All round data is signed and tamper-evident.
Player trust systems
Every player sees the active seed hash, can rotate their client seed at any time, and can export full round histories for independent verification.
Transparency commitment
We publish round verifiers, RTP audit summaries and incident reports. Any disputed outcome can be reproduced byte-for-byte.
- Step 1CommitServer generates a seed, publishes SHA-256 hash
- Step 2PlayPlayer contributes a client seed; round runs
- Step 3RevealServer seed is published after the round
- Step 4VerifyAnyone can re-compute the outcome offline