Safety archive
Commit before revealing
A typical design publishes a cryptographic commitment to a hidden server seed before the round, combines it with a client seed and nonce, then reveals enough information for reproduction. If the server can choose or replace inputs after learning the desired result, the commitment loses its purpose. Seed rotation and nonce ordering should be documented.
- APre-round commitment
- BClient contribution
- CDeterministic nonce order
Safety archive
Independent reproduction is stronger than a green tick
The formula that converts a hash into the displayed outcome should be public and precise. A user should be able to reproduce the result outside the platform checker using the same inputs. A checker that merely announces ‘verified’ without exposing the calculation asks the reader to trust the system it claims to audit.
- APublic formula
- BExternal reproduction
- CVisible inputs
Safety archive
Verification does not make a game favourable or available
The protocol can confirm consistency with committed inputs; it does not remove the house edge, detect every implementation flaw, protect a wallet or guarantee account withdrawals. It also does not override Australian law. No verifier or game link on this page enables casino play for Australian readers.
- AHouse edge remains
- BPlatform risks remain
- CNo Australian access