Protocol overview
World Lotto brings participation, public verification and funding records together. World Lotto verifies public results through UMA; Lotto 3D uses Chainlink VRF.
Actions and states
How do I participate?
Connect your wallet, fund your platform balance, choose numbers and confirm your purchase.
When can I claim?
After results are confirmed and prizes settled, claim winnings in your account.
What happens during a dispute?
The round awaits UMA resolution. A countdown ending does not confirm the result.
What are public records?
The result sources, draw transactions and settlement records for a round.
Read full technical documentation
What WF is
WF combines a unified six-decimal USD ledger with separate games and proof systems. In standalone V4, users fund their ledger balance and authorize each purchase through a wallet transaction or an EIP-712 purchase signature. Purchases, draws, claims, and withdrawals can be verified from public chain data.
The protocol separates the user, contract, oracle, indexer, and automation boundaries. An operator can run an interface and liveness workers without holding user funds or having authority to rewrite a finalized result; the active deployment still publishes its remaining operational roles and release gates.
What the contracts enforce
- Ledger debits, credits, prizes, and refunds use the deployed contract state.
- Each game has its own lifecycle, limits, and proof mechanism.
- Claims and withdrawals are user-initiated wallet transactions.
- Oracle failures and cancelled rounds follow contract-defined refund paths.
What is not guaranteed by the interface
- The indexer is a query cache. A disagreement is resolved by the chain and deployed contract state.
- A wallet connection does not guarantee that a game is open or that an oracle response is available.
- Testnet and preview features are not a promise of production availability or legal availability in your location.