How to verify a Crash bet yourself, step by step

01Save the complete round record

This walkthrough follows Duel’s audited Crash implementation. Other operators may use different inputs and formulas. Always use the verifier for the game and version you actually played.

For a completed Duel round, collect its round ID, revealed server seed, earlier server-seed hash, drand round number, drand signature and displayed crash point. Keep your bet amount, cashout and payout alongside them.

Preserve the original record before copying values into a tool. A missing input means the check is incomplete; it does not establish that the result passed or failed.

02Check the seed commitment

The revealed seed must match the hash committed before the round. Duel hashes the seed’s decoded hexadecimal bytes:

A matching hash links the revealed seed to that commitment. To establish when the commitment existed, you also need the earlier record. A hash shown only after a round cannot establish that timing by itself.

03Reproduce the crash point

Duel combines that seed with a drand quicknet beacon signature. It does not use a player client seed or nonce for Crash. Match the recorded beacon signature to the public chain for the specified drand round.

Open the published Duel bet verifier and use its Crash check with the revealed inputs. For an independent code check, use the published Crash implementation: its byte encoding, HMAC message and rounding all matter.

Compare the reproduced crash point with the recorded result exactly. Do not replace missing values with examples or round a mismatch away.

04Read the result in context

Matching the crash point checks outcome reproduction. Cashout and payout are separate checks: compare the correct record fields with the rules in the audit’s payout section, including its distinction between displayed and settled amounts.

If a check disagrees, first confirm the round, game version and copied inputs. Keep the original record and the verifier output so someone else can reproduce the same comparison. You can send the evidence for review.

A completed-round check cannot predict future rounds or prove every part of an operator’s service. The report explains the timing evidence, checks and limits of the audited implementation.