₿Hookedin
Online casino lotto

Add a lotto revenue stream without building a lotto.

Hookedin gives online casino operators a Bitcoin lotto that drops into an existing site as an iframe. Players get a recurring jackpot loop; operators get incremental ticket revenue, retention, and order-level house edge.

Create partner siteView live demoPlatform docsTestnet4
IntegrationIframe embed
Commercial control0-15% order house edge
Player loop1,000-block rounds
Why operators add it

A jackpot product that earns while it keeps players engaged

The product is designed for casinos that want another monetized game loop without owning lottery math, Bitcoin address generation, ticket ledgers, or public draw verification.

RevenueA new paid game without a new game team

Add ticket sales to your casino lobby with per-order house edge and partner payout address.

RetentionA weekly reason to come back

Every open round gives players a jackpot to watch, share, and revisit until the Bitcoin draw closes.

IntegrationIframe first, API behind it

Pass partner ID, uname, and identifier values from your existing player system. Hookedin handles the lotto flow.

TrustPublic proof for every draw

Rounds, ticket ranges, block hashes, and verifier tools are public so support teams can point to evidence.

Operator model

You own the player relationship. Hookedin runs the lotto machinery.

Partners keep their player account system and pass only public display text plus an opaque identifier into the iframe. Hookedin creates orders, watches Bitcoin payments, assigns ticket blocks, publishes round records, and keeps the verification surface open.

The operator configures the site title and payout Bitcoin address. The player sees a focused lotto experience that can sit beside slots, sportsbook, live dealer, or rewards pages.

Launch sequence
  1. Create a partner site with display name and payout address.
  2. Embed the lotto iframe in your casino and pass house edge, player display name, and opaque account identifier.
  3. Players buy tickets, Hookedin generates deposit addresses, and confirmed payments become public ticket blocks.
  4. The closing Bitcoin block hash selects the winning ticket, then the payout workflow records the winner.
How the lotto works

Fixed round terms, one jackpot, and a public Bitcoin draw

Round 26

Each round opens with a fixed ticket supply, fixed base ticket price, and fixed jackpot. The jackpot is locked as ticket supply multiplied by base ticket price. Round terms can change for the next round, but they stay locked once the current round is live.

All partner iframes sell tickets into the same round. Unsold ticket numbers are held by the house: if the draw lands on one, no player wins; if it lands on a sold ticket, the house pays the fixed jackpot.

Rounds close every 1,000 blocks, roughly weekly at the normal 10-minute Bitcoin cadence. After the closing block is mined, the winner is derived from that public block hash so the result can be independently verified.

Fixed terms per round

Ticket supply, base price, jackpot, and block window are locked once a round is live.

Shared liquidity

Every partner sells into the same current round, giving players a larger visible market than a single-site pool.

House-side downside control

Unsold ticket numbers remain with the house. If the draw lands there, no player payout is due.

Current round exampleRound 26
Jackpot
Jackpot100 BTC (~$7.4M USD)
Tickets sold1,200,000
Blocks left847about 5d 21h left
at ~10 min/block
Provably fair draw

Closing block 138000 provides the public hash used to pick the winning ticket.

Block window137001to138000
Embedded experience

The casino integration is a URL, not a platform rebuild

Partner FAQ

The iframe URL carries only public player context: partner ID, order house edge, player-facing uname, and opaque identifier from your own product. API keys stay server-side for trusted calls to the API server.

Use the hosted iframe or fork the standalone client if you need a deeper casino-specific skin.

<iframe
  title="Hookedin Lotto"
  src="http://localhost:4002?partnerId=018f58d2-2802-7000-8000-000000000002&houseEdge=0.05&uname=player-42&identifier=account-9f22"
  style="width:100%;max-width:560px;height:760px;border:0;"
  loading="lazy"
  referrerpolicy="strict-origin-when-cross-origin"
></iframe>

partnerId selects the partner site configuration and payout destination.

No API key belongs in the iframe URL. API keys are only for trusted server-side calls to the API server.

houseEdge is copied into each order and must be between 0 and 0.15.

uname is visible display text for player ledgers and orders.

identifier is public opaque data for partner records and win lookup. It is not authentication.

Open Hookedin demo
Live shared round

Real market data makes the product concrete

View round
Current roundRound 26Blocks 137001 to 138000
Jackpot100 BTC (~$7.4M USD)100,000,000 tickets at 0.000001 BTC (~$0.07 USD).
Ticket availability1,200,000 sold98,800,000 left to buy.
Block 13700115.3% completeBlock 138000
Public record

Every settled round stays available for review

View all rounds
Round 25settled100,000,000 tickets soldTotal jackpot100 BTC (~$7.4M USD)Round 24settled18,000,000 tickets soldTotal jackpot100 BTC (~$7.4M USD)Round 23settled400,000 tickets soldTotal jackpot100 BTC (~$7.4M USD)Round 22settled100,000,000 tickets soldTotal jackpot100 BTC (~$7.4M USD)Round 21settled0 tickets soldTotal jackpot100 BTC (~$7.4M USD)