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 prize pool?
No. Every partner shares the same round and the same prize pool. 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 name, display name, theme, commission, 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 and passes public/private user identifiers into the iframe.
What are the public and private user identifiers?
The public identifier is a display-safe value shown in public ledgers. The private identifier 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 identifiers?
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 identifier.
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 Commission
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, partner pages, and payout records.
Can a partner change their payout address?
Yes. A new address applies to future orders and slips. Existing orders and slips keep the payout address snapshot that was shown when the ticket was created.
How does commission work?
Commission is stored as a number from 0 to 1 and shown to users as a rounded percentage. It determines the player-facing winner amount shown in the embed, not the number of tickets assigned from a confirmed payment.
Does nonzero commission change odds?
No. Ticket counts come from confirmed payment and ticket price. If commission is 0.1, users see 10% commission: the player share is 90% of the prize pool, the partner payout is 95%, and the partner needs to distribute 90% to the player.
Tickets, Rounds, and Winners
Does partner metadata affect winner selection?
No. Partner site, commission, payout address, theme, and user identifiers do not affect the winning ticket algorithm.
How is the winner chosen?
After the round closes, Hookedin hashes the round number and Bitcoin closing block hash, converts the digest to an integer, and maps it into the sold ticket count.
How is the partner told about a winning user?
Settlement creates a durable partner win record containing the round, winning ticket, slip, and public/private user identifiers. Partners can see it in the dashboard.
What happens if a player sends more Bitcoin to the same deposit address?
The scanner can credit confirmed top-ups while the target round remains eligible. Once a round is settled, late payment recalculation is rejected for that settled round.
What is public and what is private?
Ticket ranges, round totals, partner display metadata, and public user identifiers can be public. Private user identifiers and private receipt secrets are not public verification data.
Verification and Utilities
Can partners verify the draw themselves?
Yes. Partners can use the /verify page or the public standalone utilities to fetch round JSON, calculate the winning ticket, and verify the winning slip.
Do the utilities need the Hookedin repository?
No. The public utility scripts are served as standalone Node.js files and use only built-in Node.js modules.
What can the utilities prove?
They can check the closing block hash input, winner calculation, ticket-range continuity, and winning slip. They do not prove that a partner credited its internal player account.
Does verification require trusting Hookedin?
The utilities consume public round JSON served by Hookedin, but the winner calculation and ticket-range checks are performed independently from that JSON.
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, partner pages, and payout records. Do not use an address that links to private funds or identity unless you are comfortable publishing it.