A partner-owned product can show the iframe publicly, then passes a public player ID and private account ID when the player buys tickets.
Docs and verification
Build, inspect, and verify Hookedin rounds.
One workspace for the partner model, embed contract, public audit tools, calculators, and verification FAQ. Start with the tools when you need proof; use the references when you need implementation detail.
Verification checksClosing hash to winning ticket
- closing block hash input
- configured-width draw digits
- ticket digit count
- winning ticket calculation
Overview
Platform modelOne partner platform, one public audit path
Confirmed payments from every partner are assigned into the same shared round ticket sequence.
The closing block hash expands into the configured ticket digits; that number is the winning ticket.
The browser calculator and standalone script let partners reproduce the winning ticket from public draw inputs.
Calculators and tools
Utility guideStart with the proof surface
Draw calculatorBitcoin Hash Draw
Convert a Bitcoin closing block hash into the configured-width draw digits.
Open calculatorAddress calculatorHash Tweak AddressDerive a deterministic Bitcoin address from a payload and xpub.
Open calculatorOffline auditStandalone UtilityDownload the Node.js script that reproduces the draw without the app.
View scriptAudit workflow
Open calculatorWhat the calculator does
Open a round page and copy the closing block hash.
The calculator recomputes the configured-width draw digits from the closing block hash.
The draw digit string is already the zero-indexed ticket number.
The recomputed ticket number should match the displayed round result.
Bitcoin hash draw
Open calculatorWhy the draw fills from right to left
Verification needs the configured ticket digits and the Bitcoin closing block hash. The block hash is converted into a 8-digit decimal value, and that value is the winning ticket number.
The hash work is meant to make block-withholding attacks harder. A miner who bought tickets and finds the closing block should not be able to instantly check whether they won and discard the block if they lost. The sequential hash work adds time pressure while a withheld Bitcoin block can be overtaken by another miner.
after k completed digits: H = P * 10^k + S_k winner = H
The right-hand suffix S_k is visible as progress, but the unknown left-hand prefix P still controls the final ticket bucket. That is why the string is constructed right to left: people can watch progress without revealing the winning ticket early.
Reference library
Read by task
Platform ArchitecturePartner entities, lifecycle, embed boundaries, fixed jackpot rules, and payout disclosure.Technical ReferenceRoutes, APIs, data model, validation rules, settlement, payout logic, and test surface.Utility GuideOffline verification workflow, command examples, JSON fields, and verification limits.Full FAQPlain-language answers for partners, players, support teams, payout addresses, and audits.
FAQ
Full FAQCommon verification questions
Which tool should I use first?
Use the Bitcoin hash draw calculator to inspect the block-hash-to-ticket step.
Does verification require trusting partner metadata?
No. Partner slug, theme, house edge, payout address, and player IDs do not influence winner selection. The draw depends on the closing block hash and the configured ticket digits.
What does the verifier prove?
It proves that the configured ticket digits and closing block hash reproduce the draw digits and winning ticket.
What does it not prove?
It does not prove that a partner credited an internal casino account, that a payout address belongs to the partner, or that a pending payout transaction has confirmed.