What is Hookedin's partner model?
Hookedin uses partner sites. A partner site is a B2B configuration owned by a logged-in user account and exposed to players through an iframe.
Partner platform FAQ
Answers for partner owners, integrators, support teams, and operators working with the B2B iframe model.
Partner Model
Does each partner get its own jackpot pool?
No. Every partner shares the same round and the same fixed jackpot. Ticket ranges from all partners are assigned in one continuous public ledger.
Can one account own multiple partner sites?
Yes. The data model allows a user account to own multiple partner sites, each with its own slug, site title, theme, house edge, status, and payout address.
Are organizations or team roles part of the product?
No. The current product stays simple: one authenticated user account owns partner sites. Organization membership can be added later if the product needs it.
Iframe and Users
Do embedded players log in to Hookedin?
No. Embedded players do not have Hookedin accounts. The partner is responsible for its own player system. The iframe can show public round information without player IDs, but buying tickets requires the parent site to pass a public player ID plus a private account ID into the iframe.
What are the public player ID and private account ID?
The public player ID is a display-safe value shown in public ledgers. The private account ID is kept on receipts and partner win records so the partner can reconcile a winner to its own account system. Both values must be 120 characters or fewer and may contain only letters, numbers, spaces, periods, underscores, and hyphens.
Should partners pass real names or emails as public IDs?
No. Partners should pass display-safe opaque IDs. Do not pass passwords, session tokens, email addresses, real names, wallet addresses, or anything that should remain private as the public player ID.
Can the iframe work without cookies?
Yes. The embed flow must work without a Hookedin session. The private receipt is accessed through the generated receipt secret, not a cookie.
Can partners style the iframe with custom CSS?
No. Partners can configure the supported theme values, currently the accent color. Arbitrary CSS is intentionally excluded so the player flow remains predictable and testable.
Payout Address and House Edge
Why is the partner payout address public?
The payout address is where partner-level winnings are paid. It must be public so players and partners can verify the payout destination attached to a ticket.
Where is the payout address shown?
It can appear in partner settings, the iframe before purchase, private receipts, winning slip details, round records, and payout records.
Can a partner change their payout address?
Yes. A new address applies to future orders. Existing orders keep the payout address snapshot that was shown when the deposit address was created.
How does house edge work?
House edge is shown to players as a whole percentage and inflates that partner's ticket price. The round jackpot is fixed from the locked ticket supply and base ticket price; house edge does not change it.
Does nonzero house edge change odds?
It changes how many tickets a payment buys because the player ticket price is higher. It does not change winner selection once tickets are assigned.
Tickets, Rounds, and Winners
Does partner metadata affect winner selection?
No. Partner site, house edge, payout address, theme, and player IDs do not affect the winning ticket algorithm.
How is the winner chosen?
After the round closes, Hookedin starts from the Bitcoin closing block hash, advances a SHA-256 chain, records TICKET_DIGITS decimal digits from right to left, and reads that number as the winning ticket.
How is the partner told about a winning user?
Settlement creates a durable partner win record containing the round, winning ticket, slip, public player ID, and private account ID. Partners can see it in the dashboard.
What happens if a player sends more Bitcoin to the same deposit address?
The scanner credits confirmed top-ups into the first open round that can hold the whole ticket range. If the target round is settled or lacks enough remaining tickets, the assignment moves to the next eligible round.
What is public and what is private?
Ticket ranges, round totals, partner display metadata, and public player IDs can be public. Private account IDs and private receipt secrets are not public verification data.
Verification and Utilities
Can partners verify the draw themselves?
Yes. Partners can use /verify, the Bitcoin hash draw tool, or the public standalone utility to calculate the winning ticket from the ticket digits and closing block hash.
Do the utilities need the Hookedin repository?
No. The public utility script is served as a standalone Node.js file and uses only built-in Node.js modules.
What can the utilities prove?
They can check the closing block hash input, draw digits, and winning ticket calculation. They do not prove that a partner credited its internal player account.
Does verification require trusting Hookedin?
The utility depends on the ticket digits and closing block hash shown by Hookedin, but the winning ticket calculation is performed independently from those inputs.
Payout warning
The dashboard requires partners to acknowledge this before saving a live payout address:
This Bitcoin address will be public. It can appear in embeds, receipts, round records, and payout records. Do not use an address that links to private funds or identity unless you are comfortable publishing it.