Dicey Originals verifier
Paste a revealed Dicey hex server seed, client seed and nonce. This page recomputes the selected Original with Dicey’s published HMAC-SHA256 construction (Coinflip is HMAC-SHA512). It is not on the unified /verify page yet. After the page loads, nothing is sent to a server.
What this page implements
Hex-decoded HMAC key
Dicey keys HMAC-SHA256 with the bytes of the revealed hex server seed, not the UTF-8 characters. The message is clientSeed:nonce, plus a cursor where the official View algorithm says so.
Uint32 rejection sampling
Each digest is walked as 8-hex-char unsigned values. Chunks at or above 2³² − (2³² % range) are discarded. Dice is 0–9999 then shown as (n+1)/100. Limbo is 0–999,999 / 1,000,000 through the published inverse-CDF curve.
Coinflip is SHA-512
One HMAC-SHA512 of clientSeed:nonce. Each coin is a bit, low bit of each byte first. 0 is Heads, 1 is Tails. Everything else on this page is SHA-256.
Not the unified calculator
Stake, Shuffle, BC.Game and the other live tabs stay on /verify. This URL is Dicey-only so you can check the numbers against dicey.com before any tab is added there.
Does any of my data leave this page?
No. After the page loads, hashing runs through the browser Web Crypto API. Seeds are not posted anywhere.
Why must the server seed be hex?
Dicey’s official verifier hex-decodes the revealed server seed before using it as the HMAC key. A nickname or UTF-8 string will not match. The commitment hash is SHA-256 of those decoded bytes, not of the hex text.
Why is Limbo a v1 / v2 toggle?
Current Dicey Limbo (v2) puts the 1% house edge in the curve: 0.99 / (1 − r). The older v1 curve used 1 / (1 − r). The default here is v2. Bet Chat always uses the v2 curve.
What about Black Holes start cell?
The hole draw only uses cells outside a safe disc around the start cell. Current Dicey rounds use the v3 131×131 board. Paste the start cell from the bet’s fairness panel if you have it; 0 is only a placeholder.