How to Rotate Your Seed on Duel.com
When and how to rotate your seed pair on Duel.com: record the hash, reveal the server seed, run the SHA-256 check, and verify past rounds in Duel's verifier.
On this pageShowHide
Quick answer
A provably fair server seed has to stay hidden while it is in use, or you could calculate future results. Rotation is how it gets revealed: you end the current seed pair, the casino discloses the server seed behind it, and a new pair begins. Until you rotate, the fairness of your bets is a commitment you have not yet checked.
Duel documents the role rotation plays: past rounds can be checked in its verifier at duel.com/fairness/verify only after the seed has been rotated. What Duel does not document is where the rotate control sits or what it is called, so treat the button names below as approximate and ask the 24/7 live chat if you cannot find it.
What rotation does
Step 1
Active pair
Server seed hidden, its hash shown
Step 2
You bet
Nonce rises with each wager
Step 3
Rotate
Old server seed revealed
Step 4
Check
SHA-256 of seed equals old hash
Step 5
New pair
New hash shown, nonce reset
| After rotation | Changes? |
|---|---|
| Server seed | Yes. The old one is revealed, a new hidden one takes over |
| Server seed hash on screen | Yes. It now commits to the new seed |
| Client seed | Yes if you enter a new one |
| Nonce | Starts again for the new pair. Duel does not document the first value, so read it from the bet detail |
| Bet history | No. Old bets stay, and become verifiable |
| House edge and win probability | No |
One seed pair serves all the Originals that use a client seed: Duel documents that the nonce rises by 1 for every round across all house games. Rotating therefore closes the pair for Dice, Mines, Plinko, Blackjack and the rest at once.
Many sites show the hash of the next server seed in advance. That is the commitment for the pair you are about to start, which is what makes it safe to pick a new client seed at the same moment. Whatever the layout, the rule Duel itself states is the one to hold on to: the hashed server seed must be visible to you before you commit to a client seed.
Before you rotate
Find the active seed pair
Open the fairness or provably fair settings for an Original. They should list the active client seed, the hashed server seed and the current nonce.
Copy the server seed hash out of the site
Paste it into a note or take a screenshot with the time visible. If you only ever read the hash from the site after the reveal, you are trusting the site to show you the same hash it showed before.
Finish any open round
Games with multi-step rounds, such as Mines or Blackjack, usually need the round to be finished before a pair can be rotated.
Rotate and check
Enter a new client seed
Type your own random string for the next pair. See the guidance below.
Confirm the rotation
The previous server seed is now displayed in full, and a new server seed hash replaces the old one.
Hash the revealed seed
Run it through SHA-256 with a tool you control and compare the output with the hash you saved.
Record the new hash
Save the new server seed hash, so the next rotation can be checked the same way.
Duel's server seed is a 64-character hex string. Duel documents that it is hashed with SHA-256, but not whether the hash is taken over those 64 characters as text or over the 32 bytes they represent, and its published examples include no hashed seed. So compute both and see which one equals the hash you saved. Try the text form first.
On macOS, Linux or Git Bash this takes two commands. Use printf so that no line break is added to the seed. On macOS, replace sha256sum with shasum -a 256. The seed shown is the one from Duel's published Dice example; paste your own in its place.
printf '%s' "e8c83961a3961baee67cc08da34ada1c00a4515450a3cdbd2b1db81a35ca7f72" | sha256sum
printf '%s' "e8c83961a3961baee67cc08da34ada1c00a4515450a3cdbd2b1db81a35ca7f72" | xxd -r -p | sha256sum
The first line hashes the text and prints 8150149e80274b32391fd1fdf80f0f2bda11705a462a1c17737104996aac772e. The second hashes the bytes and prints 6205003b9efc5f676a4471bb7316f544d4f7cc10d346aa09f1e492f015a13339.
With Node.js installed, on any operating system, this script computes both and compares them with your saved hash:
// Commitment check: does the revealed server seed match the hash you saved before betting?
const crypto = require("node:crypto");
const sha256 = (data) => crypto.createHash("sha256").update(data).digest("hex");
const revealedSeed = "e8c83961a3961baee67cc08da34ada1c00a4515450a3cdbd2b1db81a35ca7f72"; // seed from Duel's published Dice example
const savedHash = "PASTE_THE_HASH_YOU_SAVED_BEFORE_BETTING";
const asText = sha256(revealedSeed); // the 64 characters hashed as text
const asBytes = sha256(Buffer.from(revealedSeed, "hex")); // the 32 bytes the hex stands for
console.log("SHA-256 of the seed as text: ", asText);
console.log("SHA-256 of the seed as bytes:", asBytes);
if (savedHash === asText) console.log("MATCH: the published hash is of the seed text");
else if (savedHash === asBytes) console.log("MATCH: the published hash is of the hex-decoded bytes");
else console.log("NO MATCH with either form");
As written it prints the two hashes above and NO MATCH, because the saved hash is a placeholder. With your own seed and saved hash, a match in either form means Duel fixed that seed before any bet on the pair, so every result on it was already determined.
To go one step further and recompute individual results, follow how to verify a bet, or enter the round in Duel's verifier at duel.com/fairness/verify. After rotation, the verifier also lets you raise the nonce for the old pair to see what your next rounds would have been. They were fixed from the moment the pair was created.
Choosing a client seed
The client seed protects you because of when it is chosen, not because of what it contains. Duel commits to its server seed first; a client seed you set afterwards could not have been known when that seed was generated. Duel describes the client seed as a string chosen by the player, or generated automatically if you do not choose one.
- Use a random string of 16 or more characters, for example from a password manager
- Set it yourself instead of keeping a default you did not choose
- It does not need to be secret; it appears in your bet details
- Stick to plain letters and digits to avoid copy and encoding problems when you verify
- No client seed is luckier than another
When to rotate
| Situation | Rotate? | Why |
|---|---|---|
| After your first session | Yes | Proves the process works on your account |
| A result looks wrong | Yes | The seed is needed to recompute it |
| Before a session with larger stakes | Reasonable | Starts a pair whose hash you have recorded |
| After a losing streak, to change luck | No | Odds are identical on every pair |
| After every few bets | Pointless | One check covers the whole pair, however long |
Rotating in the middle of a losing run deserves a specific warning. It feels like doing something, and it changes nothing about the next result. If the urge to rotate comes from wanting the session to turn around, that is a signal to stop, not to reseed. See deposit and loss limits.
What rotation does not do
- Improve or reset your odds
- Erase or hide past bets
- Apply to third-party slots or live dealer games, which do not use your seed pair
- Prove anything until you run the hash check
- Tell you about the house edge, withdrawals or the operator's solvency
Crash and Castle Roulette are a separate case. They are shared rounds, and Duel documents that they use a public drand randomness value in place of a client seed, with the nonce fixed at 0. Your personal seed pair plays no part in them, so there is nothing to rotate. Each round has its own hashed server seed and drand round ID, shown before the round starts. See provably fair explained.
A simple routine
- Before your first bets, save the hashed server seed and set your own client seed.
- After the session, rotate and run the hash check.
- Recompute two or three results from that pair, in Duel's verifier or with your own script.
- Save the new hash. Repeat only when you want to audit again.
Summary
Rotation closes a seed pair, reveals its server seed and starts a new pair. Save the hash beforehand, hash the revealed seed afterwards and compare. Choose your own client seed for the new pair. The odds do not change; what you gain is proof that the results you already had were fixed in advance.
Frequently asked questions
When should I rotate my seed on Duel.com?
Rotate when you want to audit the bets you have just made, because the server seed is only revealed on rotation. A sensible routine is once after your first session and again whenever a result looks wrong. There is no need to rotate on a schedule, and no benefit to doing it often.
Does rotating seeds change my odds?
No. A new seed pair gives a new sequence of results with exactly the same probabilities and house edge. Rotation is an audit step. Using it to escape a losing run does nothing, because past results on one pair have no bearing on the next.
What happens to my old bets when I rotate?
They become fully verifiable. The revealed server seed, together with the client seed and each bet's nonce, reproduces every result on that pair. Duel's verifier at duel.com/fairness/verify accepts past rounds once the pair has been rotated, and you can recompute them with your own code.
Can I choose my own client seed?
Yes. Duel's documentation describes the client seed as a string chosen by the player, or generated automatically if you do not choose one. Use a random string, for example from a password manager. It does not need to be secret. What matters is that you set it after the hashed server seed was shown.
What if the revealed seed does not match the hash?
First rule out input errors: a trailing space or line break, or hashing the seed as text when the hash was made from its hex-decoded bytes. Try both forms. If neither equals the hash you recorded before betting, stop playing, save the evidence and contact Duel.com live chat and support@duel.com.
Do Crash and Castle Roulette use my seed pair?
No. Crash and Castle Roulette are shared rounds. Duel documents that they use a public drand randomness value in place of a client seed, with the nonce fixed at 0, so rotating your personal seed pair does not affect them. Each round has its own hashed server seed and drand round ID shown beforehand.
Duel.help Games Desk
Casino games, sportsbook & provably fair
The games desk documents game rules, house edge, RTP concepts, provably fair verification and sportsbook mechanics in plain English.
- Published
- Last reviewed
Independent and unaffiliated with Duel.com. Read our editorial policy to see how these guides are researched and reviewed.
Was this page helpful?
Feedback stays on your device and helps you track what you have already read.
Parent category
Provably Fair · 4 articles
Seeds, hashes and step-by-step verification of individual bet results.
Related articles
Next steps and adjacent topics chosen from the same part of the help center.
How to Verify a Bet on Duel.com (Step by Step)
Verify a Duel.com bet with Duel's verifier or your own code: the documented HMAC-SHA256 scheme, runnable Node and Python scripts, and fixes for mismatches.
Server Seed, Client Seed and Nonce Explained
What the server seed, client seed, nonce and cursor do in a Duel.com bet, how HMAC-SHA256 combines them, and Duel's own Dice example worked through.
Provably Fair Explained: How Duel.com Verifies Game Results
How provably fair works on Duel.com Originals: the SHA-256 commitment, Duel's HMAC-SHA256 formula for each game, drand for Crash, and what the proof does not cover.
Dice on Duel.com: Rules, Payouts and House Edge
How Duel Dice works: setting win chance, reading the payout multiplier, the exact maths of the house edge, how Duel's Zero Edge makes dice 100% RTP within the daily allowance, how each roll from 0.00 to 100.00 is generated and verified, and why dice is the best game for learning casino maths.
House Edge and RTP Explained for Crypto Casino Players
What house edge and RTP actually mean, how they relate, why short sessions diverge from the average, how Duel.com's Zero Edge 100% / 99.9% RTP model works, and what a 0% edge does and does not change.
Duel.com Help: Independent Help Center
Duel.com help hub: how to reach official 24/7 support (live chat and support@duel.com), what Duel.help can and cannot do, dispute escalation, and fixes for the 10 most common problems.