MISTBOXBACK TO TRUST

TECHNOLOGY · PROVABLY FAIR

THE RESULT IS LOCKED
BEFORE YOU OPEN.

MISTBOX uses a cryptographic commit–reveal mechanism so neither the platform nor the user can unilaterally manipulate an opening. After reveal, anyone can independently reproduce and verify the result.

01 · THREE INPUTS

SERVER SEED

Generated by MISTBOX

Platform-side source of entropy

CLIENT SEED

Chosen or refreshed by you

A user-controlled counterbalance

NONCE

Increments for each opening

Prevents a result from being replayed

02 · COMMIT → OPEN → REVEAL
01

COMMIT

MISTBOX generates a random server seed and publishes SHA-256(Server Seed). You then confirm or refresh your client seed.

02

OPEN

The opening uses HMAC-SHA256 with the server seed as the key and Client Seed : Nonce as the message.

03

REVEAL

The original server seed is disclosed. You compare its hash and run the same inputs to reproduce the result.

Random Bytes = HMAC-SHA256(
  key: Server Seed,
  message: Client Seed + ":" + Nonce
)

The first four bytes are mapped to a number in [0, 1), then matched against the probability table published for that opening.

03 · SECURITY PROPERTIES

Platform changes the result afterwards

✓ NOT FEASIBLE

The published hash commitment would no longer match.

Platform preselects a winning seed

✓ NOT FEASIBLE

The HMAC output is unpredictable before the client seed is known.

User controls the result alone

✓ NOT FEASIBLE

The client seed cannot determine an output without the server seed.

A prior result is replayed

✓ NOT FEASIBLE

A strictly increasing nonce makes every opening unique.

04 · VERIFY IT YOURSELF

DON’T TRUST.
REPRODUCE.

Copy the server seed, client seed and nonce shown for your opening into the verification tool to reproduce the output locally—without trusting MISTBOX services.

SERVER SEEDrevealed-after-openCLIENT SEEDyour-seed-8f2aNONCE1
OPEN-SOURCE VERIFIER · COMING WITH THE DAPP