Resolved rounds expose the final CSV hash and downloadable ticket CSV.
Start with the game, then verify the system.
Luckotto docs are organized around the actual flow: how a ticket works, what the embed shows players, how public verification works, and where the partner/API details live.
- game basics
- embed player flow
- public verification tools
- round verification
- partner integration
- technical reference
The useful reading order
Plain-language ticket, jackpot, draw, payout, and verification flow.
EmbedPlayer embed flowThe same player-facing help shown inside the embeddable Luckotto UI.
AuditRound verificationRead the CSV commitment, draw block, winner, and payout proof model.
IntegratePartner platformPartner accounts, iframe URL contract, player identifiers, and API-key boundaries.
Tools for draws, addresses, and proof
Run the weighted elimination draw and inspect the final draw tiles.
Open toolCommitmentCommitment calculatorDerive a round commitment address and inspect its first outbound OP_RETURN transaction.
Open toolAddressHash tweak address calculatorInspect the deterministic derivation used by player deposit addresses.
Open toolRounds verify by CSV commitment and slow draw.
A Luckotto round publishes the final CSV hash, OP_RETURN commitment transaction, commitment block, draw block, weighted slow-hash elimination proof, final draw tiles, winning ticket, and payout evidence.
The first outbound commitment transaction commits the raw CSV hash in output 0.
The draw block is 2 blocks after the commitment confirms.
The draw calculator replays the weighted elimination draw from the draw block hash.
Round pages keep the winning ticket and payout transaction linked for review.
Player-facing pages available inside the iframe
Partner and implementation details
High-level proof path, pseudocode, tradeoffs, and security assumptions.
Platform architectureThe monolith runtime, partner lifecycle, player identifiers, and iframe contract.
Game and settlement rulesTicket allocation, paid-sat weighting, elimination settlement, and verification in one reader flow.
API and database referenceAPI boundaries, database shape, route surfaces, and validation rules.
FAQPlain-language answers for partner owners, integrators, and operators.