One public draw beneath your product.
Luckotto is a Bitcoin lotto sold wholesale. Partners create funded receipts, sell their own customer experience, and keep every sat of markup. Luckotto runs the shared weekly draw, provides the prize bankroll, pays the selected partner, and publishes evidence anyone can replay.
- Your markup
- 100% yours
- Default ticket fee
- 100 sats
- Draw cadence
- Weekly
Holding a ticket? Its receipt link is the starting point. You can also browse the round ledger, replay a draw in the verifier, or find your partner.
You run the customer product. Luckotto runs the draw.
Own the customer loop
- Choose the brand, retail price, currency, and promotions.
- Create one funded Luckotto receipt for each entry you sell.
- Define any customer numbers, tiers, prizes, or secondary draw.
- Settle your customers under the rules you publish.
Owns the public draw
- Records funded tickets and aggregates them by partner.
- Commits the exact round and bankroll terms on Bitcoin.
- Runs one unbiased draw over every partner allocation.
- Pays the selected partner and publishes the complete proof.
Three phases, each with a public artifact.
- 01Continuous · at your pace
Create and sell
Fund a partner balance with Bitcoin, then create tickets from trusted server-side code. Every ticket has one permanent UUIDv4, a contribution, and public metadata. Creation is idempotent: the same id and fields return the same receipt.
Customers buy from you, not Luckotto. You may also use an auto-ticket deposit address when a confirmed customer BTC payment should create the ticket directly.
Public artifactA funded ticket receipt - 02Weekly · exact and immutable
Commit and draw
At close, one manifest freezes every partner's aggregate contribution, desired prize, exact receipt list, the prize bankroll, a secret hash, and the VDF iteration count. Luckotto anchors the manifest hash in a Bitcoin transaction before the draw block exists.
The draw uses a later Bitcoin block, at least 3 blocks after commitment, then a public VDF with a positive iteration count that can only ratchet upward from one round to the next, plus a 30-minute reveal delay.
Public artifactBitcoin commitment and canonical draw evidence - 03Verifiable after operator reveal · independently replayable
Pay and prove
One exact sample selects the no-winner interval or one partner. Luckotto pays the selected partner's fixed address; Core never chooses or pays an individual customer.
The round page publishes the manifest, delayed seed, revealed secret, selected interval, and payout state. Anyone can recount the entries and replay the result in the browser or with Luckotto Calc. If the operator does not reveal the committed secret, that is a sign of cheating rather than a valid cancellation.
Public artifactA resolved round and, when applicable, payout transaction
The price, the prize, and the draw edge are separate.
Your customer price never enters the Luckotto round. Core only sees funded contributions and the partner's desired prize.
You set the customer price
Charge in any currency and keep every sat of markup above the contribution and flat ticket fee.
Every contribution joins the round
Contributions form the ticket-funded pot. A pot-backed desired prize adds no bankroll shortfall.
Luckotto can support a larger prize
When the desired prize exceeds the pot, the bankroll covers the possible shortfall and the published draw edge prices that exposure.
Six things your implementation must preserve.
- 01You mint permanent UUIDv4 ticket ids.
Keep unfunded ids private and reuse the same id for retries.
- 02Ticket metadata is public and immutable.
Encrypt sensitive values before storing them; metadata never changes draw odds.
- 03Ticket creation follows the accepting round.
You cannot target a round or create a between-round retry race.
- 04The Luckotto draw stops at the partner.
Your customer winner selection and prize distribution remain your responsibility.
- 05The desired prize freezes at close.
The committed round uses the partner value in force when sales lock.
- 06Every claim must recount from public evidence.
Link the round, receipt, manifest, and verifier when a result is questioned.