Test environment · No-value assets · UMA sandbox · Real Chainlink VRFChecking service versions…
WORLD LOTTO DOCUMENTATION

Draws and verification

Result confirmation and prize settlement are separate states. Prizes are not claimable while an UMA decision or settlement is pending.

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

Lotto3D · Chainlink VRF

Lotto3D uses Chainlink VRF for its draw. Ticket ownership, ticketId values, match rules, and settlement remain represented by onchain events and contract state.

World Lotto · optimistic assertion

The UMA version builds its seven-digit result from seven designated official lottery sources. Each digit uses the last digit of the final main number; special and bonus balls are excluded. Canada Lotto 6/49 and Brazil Mega-Sena are used as left-to-right fallbacks for one or two unavailable sources. Three or more failures enter the round exception flow. The asserted number is not final merely because it was submitted; the challenge period and the deployed settlement contract determine the next state.

BTC 5M · design preview

The BTC 5M market is currently a blocked preview. The production deployment does not yet have the approved BTC/USD verifier configuration, so no BTC position can be opened through this interface.

The intended design uses signed BTC/USD reports, strict observation-time checks, a verification delay, and a refund path for oracle failure. Those rules must be finalized and audited before activation.

The next version is a binary ERC-1155 condition market: users sign orders, WF's matcher proposes complementary/mint/merge fills, and the WFExchange contract verifies the fill onchain. The browser receives executable YES/NO quotes and aggregated WF depth; it does not consume Polymarket's CLOB.