Independent explainer · not Duel.com

Duel Crash Provably Fair

Provably fair lets you confirm a round's result was locked in before your bet. Here is the commit-and-reveal flow, a live hash demo, and an honest note on what it cannot do.

Fairness is not prediction. A provably fair check confirms a result was committed in advance and not altered. It does not reveal the next crash point or help you forecast a round.

The commit-and-reveal flow

Duel's house games publish a standard provably fair scheme built from a server seed, your client seed and a per-round nonce, combined and hashed. The hashed server seed is shown before the round so the outcome is locked in.

Before the roundYou receive a SHA-256 hash of the server seed. The result is committed, so it cannot be changed after you bet.

During the roundThe server seed, your client seed and the nonce together determine the crash point. None of them can be altered once the hash is published.

After the roundThe server seed is revealed. You re-hash it, confirm it matches the earlier commitment, then reproduce the result.

See a commitment hash

This runs SHA-256 in your browser to show what a Duel Crash server-seed commitment looks like. It illustrates the hashing step only — it does not reproduce Duel's exact crash-point algorithm, which you should verify in the live game.

Sample server seed Type anything. Change one character and the whole hash changes.

SHA-256 commitment

—

Because one tiny change rewrites the entire hash, an operator cannot publish a commitment and then quietly swap the seed for a different result. That is the whole point of the commitment.

What it proves — and what it doesn't

It can prove

That a single round's crash point was fixed before you bet, that the revealed seed matches the earlier hash, and that the result was not edited after the fact.

It cannot prove

The long-run RTP on its own, that future rounds are predictable, or that any pattern exists. Verifying a round confirms integrity, not a forecast.

Integrity, not odds. A passing Duel Crash check shows the round was honest, not what the next one will be.
Per round, not aggregate. One verification covers one round; long-run fairness is a separate, statistical question.
Verify in the live game. Use the exact seeds, nonce and verification steps shown in the current interface, not a guide.

Across the toolkit

Main toolSingle-target risk calculator

Hit chance, bust risk and EV for one cashout target.

AllowanceZero-edge allowance & cost

How long the allowance lasts and what play costs after it.

ReferenceCompare cashout targets

Hit rates and bust risk from low to high multipliers.

Frequently asked questions

What does provably fair actually prove?

That a round's result was committed before your bet and not changed afterwards. You re-hash the revealed server seed and confirm it matches the hash shown earlier.

Can provably fair predict the next crash point?

No. The commitment hides the result until it is revealed. It guarantees the result was fixed in advance, which is the opposite of letting anyone forecast it.

What are the server seed, client seed and nonce?

The server seed is the operator's secret value, the client seed is yours, and the nonce counts the round. Combined and hashed, they produce a result neither side can rig alone.

Does a passing check mean the game is 100% RTP?

No. Verification proves a Duel Crash round was not tampered with. The return rate is a separate question — see the allowance and calculator pages for the RTP model.

Why does the hash change completely from a tiny edit?

SHA-256 is designed so any input change produces an unrelated output. That is what stops an operator from swapping the seed after committing to a hash.

Is this official Duel fairness documentation?

No. duelcrash.com is an independent information site. It is not Duel.com and does not operate the game. Always verify the exact steps in the live interface.