FAQ
Search practical answers about tickets, partners, draws, and verification.
Basics
What a ticket represents and how the draw ends.
What is Luckotto?
A Bitcoin lottery ledger whose tickets and draw can be independently replayed.
Partners buy Luckotto tickets and sell them through their own customer experience. Each ticket is a public funded receipt; Core aggregates receipt contributions into one exact draw allocation per partner.
How is a winner picked?
One unbiased sample selects the no-winner interval or exactly one partner allocation.
SHA-256 hashes the protocol domain, round secret, delayed draw seed, and an attempt counter. Exact rejection sampling removes modulo bias. Intervals are ordered with no winner first, then positive-allocation partners in ascending deposit account index.
Can partners add their own ticket experience?
Yes. Partners build any customer game over their public funded receipts.
Luckotto commits ticket UUIDs, contributions, partner assignments, and desired prizes snapshotted when the round locks. Core draws a partner; that partner runs its own customer winner selection and prize tiers. Public ticket metadata is display data, not part of the manifest and never part of the odds. Private values must be encrypted before storage.
Fairness
How the public commitment, delay, reveal, and replay fit together.
When is the round fixed?
Before the draw block exists, Luckotto commits the round manifest and secret hash on Bitcoin.
The manifest fixes each partner's aggregate contribution and desired prize, the prize bankroll, secret hash, and VDF iteration count, and it pins every individual receipt through per-partner manifest hashes. The draw block is exactly 3 blocks after the commitment confirmation.
Why use a VDF?
It binds the manifest and unpredictable draw block into a publicly verifiable delayed seed.
One Chia 1024-bit class-group evaluation starts from element 08. Anyone may race the proof; Core accepts the first valid canonical solution and records its own acceptance time. The iteration count is positive and may increase, but never decrease, from one round to the next.
Why is the result hidden for 30 minutes?
The accepted VDF solution starts a fixed suspense window before the committed secret is published.
During reveal pending, the public UI shows only the reveal deadline and generic suspense copy. It exposes no winner-derived clues. After the deadline the worker atomically publishes the secret and outcome.
Can I verify it myself?
Yes. Verify the commitment, one VDF proof, and one interval selection.
Use the browser verifier or the standalone Go calculator. The full rules are on the provably fair page.