Start with a ticket
Every ticket has exactly 6 tiles. Ordinary users buy tickets from resellers, who fund Luckotto tickets from confirmed Bitcoin balance; at draw time, Luckotto chooses the winning tile set.
- 01Fund reseller balance
Resellers deposit Bitcoin before they can buy Luckotto tickets.
- 02Create ticket
The reseller API creates a ticket and spends sufficiently confirmed balance into that ticket atomically.
- 03Pick 6 tiles
At draw time, 6 tiles are drawn from public checkpoints, then the winner checkpoint selects the winning live ticket by weight.
The jackpot is cumulative: every ticket grows the current open round's jackpot. It keeps growing until the weekly draw resolves the winning ticket.
At the weekly draw, Luckotto uses the draw block hash and committed entries to draw 6 tiles from public checkpoints. Each eligible tile bucket is weighted by the total funded amount of live tickets containing that tile.
The selected ticket wins. Larger confirmed deposits increase that ticket's weight; the tile numbers themselves do not change odds.
The reseller that owns the winning ticket is paid exactly the sum of all ticket weights, with Bitcoin payout fees paid outside the jackpot amount.
The committed CSV, round secret hash, and CSV HMAC are public as soon as the round locks — before the on-chain commitment confirms. The resolved proof reveals the round secret, winning ticket, and draw tiles, publicly replayable from the on-chain commitment and delayed draw block, alongside the admin-recorded jackpot txid.
A player buys through a reseller. The reseller chooses or receives 6tiles, then funds the ticket with confirmed Bitcoin balance. The funded sats enter that round's jackpot and set the ticket's draw weight.
Luckotto records the Bitcoin amount the reseller spends on the ticket. The reseller may sell it externally at whatever price and terms it chooses.
After sales close, the worker seals the entry-number-ordered round CSV under an HMAC keyed by the round secret hash and immediately publishes the CSV, hash, and HMAC — before the on-chain commitment confirms. It commits the HMAC on-chain, waits 2 blocks after confirmation, then stores checkpoints and resolves the weighted draw. The resolved proof reveals the round secret, winning ticket, and draw tiles in checkpoint order together.
Reseller deposits can appear as confirmed before they are safe enough to spend; ticket creation only uses sufficiently confirmed balance.