₿Luckotto
Docs and verification

Luckotto is one monolithic app.

Pages, partner APIs, the embeddable player UI, scanner jobs, and public verification all live in the root Next/Node program.

Platform modelTechnical referenceVerify draw
Verification inputsLuckotto order settlement
  • round number
  • closing block hash
  • full draw order
  • winning ticket id
  • public allocated numbers
Overview

Runtime responsibilities

01One app owns everything

The root monolith serves pages, JSON APIs, the embed UI, scanner jobs, reset commands, and wallet tooling.

02Partner access is in Next

Partner and player JSON routes live under /api/luckotto in the same app as the dashboard.

03Embed is /embed

Partners embed /embed with public query params for partner ID, playerUname, and playerIdentifier.

04Jobs are root scripts

The same package scans Bitcoin, allocates tickets, settles rounds, and resets development data.

Verification tools

Public audit surface

VerifierLuckotto Round Verification

Inspect a settled round's closing block hash, full draw order, winning ticket, and winning claim numbers.

Open toolAddress toolHash Tweak Address

Inspect the deterministic derivation used by player deposit addresses.

Open toolPricing toolTicket Calculator

Pick weighted Luckotto numbers and inspect weighted claim prices.

Open tool
Guides

Implementation references

Platform Architecture

The monolith runtime, partner lifecycle, player identifiers, and deposit address visibility.

Technical Reference

API boundaries, database shape, route surfaces, and validation rules.

Game Model

The canonical weighted draw, weighted pricing, claim allocation, non-overlap rule, and settlement explanation.

FAQ

Plain-language answers for partner owners, integrators, and operators.