₿Hookedin
Partner platform

Hookedin partner docs

Hookedin is a B2B partner platform. A logged-in user creates a partner site, configures theme and commission, sets a required public payout Bitcoin address, and embeds an unauthenticated lotto iframe on their own website.

Read architectureRead technical referenceOpen FAQ
Platform ArchitecturePartner entities, lifecycle, product rules, embed contract, and the shared-pool model.Technical ReferenceEntities, embed contract, APIs, data model, payout rules, partner wins, and testing surface.Partner FAQPlain-language answers for partner sites, public payout addresses, users, commissions, and verification.Public UtilitiesHow to fetch round JSON, calculate the winning ticket, and verify the winning slip with standalone scripts.Verify RoundsUse the browser verifier and download the public utility source files served by this Hookedin site.

Model

EntityUserThe authenticated account that owns and manages partner sites. Login remains email-only.
EntityPartner siteThe B2B embed tenant with display name, theme, commission, status, and required public payout address.
EntityPlayer identifierThe partner-supplied player identifier passed through the iframe URL. It is attribution, not authentication.
EntityShared roundThe global lotto round. Every partner site contributes tickets to the same prize pool and ticket ledger.

Core rules

Partner payout Bitcoin addresses are required before a site can go live, and they are public. The dashboard must warn partners before saving or changing that address.

The iframe does not use Hookedin authentication. The partner passes public/private user identifiers. Hookedin shows the public identifier in ledgers and keeps the private identifier so the partner can identify a winning casino account.

Commission is stored as a number from `0` through `1` and shown as a rounded percentage. Tickets are calculated from confirmed payment; commission determines the player-facing winner payout shown in the embed.

Partner metadata never changes the winner algorithm. Public verification remains based on the round number, closing block hash, sold ticket count, and ticket ranges.

Implementation

  1. Authenticated users create and manage partner sites.
  2. Each partner site has theme settings, commission, status, and a required public payout address.
  3. The dashboard generates an iframe snippet and shows a live demo.
  4. The embed flow is unauthenticated and accepts partner-supplied user attribution.
  5. Scanner math records gross prize contribution while payout pages use partner commission snapshots.
  6. Settlement creates durable partner win records and keeps public verification independent.