{benefit_1_title}
{benefit_1_text}
{article_author} {article_updated} {article_read_time}
{hero_eyebrow}
{hero_title}
{hero_subtitle}
- {hero_stat_1_value} {hero_stat_1_label}
- {hero_stat_2_value} {hero_stat_2_label}
- {hero_stat_3_value} {hero_stat_3_label}
{hero_badge_1_title} {hero_badge_1_text}
{hero_badge_2_title} {hero_badge_2_text}
{benefits_title}
{benefits_subtitle}
{benefit_2_title}
{benefit_2_text}
{benefit_3_title}
{benefit_3_text}
{benefit_4_title}
{benefit_4_text}
{benefit_5_title}
{benefit_5_text}
{benefit_6_title}
{benefit_6_text}
{comparison_title}
{comparison_subtitle}
| {comparison_col_feature} | {comparison_best_tag}{comparison_col_1} | {comparison_col_2} | {comparison_col_3} |
|---|---|---|---|
| {comparison_row_1_label} | {comparison_row_1_col_1} | {comparison_row_1_col_2} | {comparison_row_1_col_3} |
| {comparison_row_2_label} | {comparison_row_2_col_1} | {comparison_row_2_col_2} | {comparison_row_2_col_3} |
| {comparison_row_3_label} | {comparison_row_3_col_1} | {comparison_row_3_col_2} | {comparison_row_3_col_3} |
| {comparison_row_4_label} | {comparison_row_4_col_1} | {comparison_row_4_col_2} | {comparison_row_4_col_3} |
| {comparison_row_5_label} | {comparison_row_5_col_1} | {comparison_row_5_col_2} | {comparison_row_5_col_3} |
| {comparison_row_6_label} | {comparison_row_6_col_1} | {comparison_row_6_col_2} | {comparison_row_6_col_3} |
| {comparison_footer_label} | {comparison_col_1_cta} | {comparison_col_2_cta} | {comparison_col_3_cta} |
{comparison_note}
{faq_title}
{faq_subtitle}
{faq_help_title}{faq_help_link}
{faq_1_question}
{faq_1_answer}
{faq_2_question}
{faq_2_answer}
{faq_3_question}
{faq_3_answer}
{faq_4_question}
{faq_4_answer}
{faq_5_question}
{faq_5_answer}
{faq_6_question}
{faq_6_answer}
{faq_7_question}
{faq_7_answer}
What provably fair means, and what it does not
Fairness of the shuffle, not of your strategy
Where certification replaces seed pairs
Provably fair is a commitment made before the bet, not a promise about the result. EarnBet3 publishes a hashed server seed before a round begins, mixes it with a client seed you supply, and lets you recompute the outcome afterwards. The method proves the shuffle was fixed in advance and left unchanged in hindsight. It does not raise your odds, does not predict the next round, and does not govern slots supplied by outside studios.
- Fairness of the shuffle, not of your strategy: the outcome was locked before your bet was accepted.
- The operator cannot swap the result once your stake is placed.
- Any single round can be re-checked later with the same inputs, by you, offline.
- Where certification replaces seed pairs: third-party slots and live tables carry studio or lab audits instead.
| Game type | Fairness method | Who verifies it |
|---|---|---|
| Crash, dice, plinko (in-house) | Seed pair, SHA-256 | You, with the published verifier |
| Certified third-party slots | Audited RNG from the studio | Independent lab report |
| Live dealer tables | Physical cards, studio recording | Studio dispute process |
Does provably fair mean I cannot lose?
No. It proves the round was decided before your bet and unchanged afterwards; house edge and outcomes stay the same.
Why are some games missing from the fairness panel?
In-house originals use seed pairs. Third-party slots and live tables follow their provider's certification, and those reports sit with the studio.
The seed pair, component by component
Server seed and its published hash
Client seed and nonce
Every verifiable round at EarnBet3 rests on two strings of data and one counter. The server seed is generated by the platform, hashed with SHA-256, and the resulting hash is shown to you before you place a bet. The client seed is yours — type any text or accept the generated one. The nonce rises by one with each bet made under the same seed pair, so identical seeds still produce different rounds.
- Server seed and its published hash: generated before play, the hash appears in the fairness panel immediately, the plaintext only when you rotate.
- Client seed and nonce: you choose the text, the counter advances automatically, and editing the client seed resets the nonce to zero.
- Rotation: revealing the retired server seed lets you verify every past round placed under that pair.
- Round history: each bet stores its own nonce and hash, so verification is per round, not per session.
| Component | Who sets it | When it is visible | What resets it |
|---|---|---|---|
| Server seed (plaintext) | EarnBet3 | After you rotate the seed | Manual rotation |
| Server seed hash | EarnBet3 | Before the first bet | Same rotation |
| Client seed | You | Always, editable | Your own edit |
| Nonce | Automatic | In round history | Rotation or seed edit |
Can I reuse the same client seed?
Yes, but the nonce keeps moving, so the same client seed with a new nonce gives a different result.
What happens if I never rotate the server seed?
You can still track your own rounds, but the plaintext seed stays hidden, so you cannot recompute the published hash until it is revealed.
A worked round, hash included
Inputs and hashing order
Matching the output to the round
The round below is illustrative: every value is a labelled placeholder, not a real bet. Take a client seed you typed, quiet-harbor-19, a nonce of 1, and a server seed the platform already hashed and committed to. Join the client seed and nonce, hash the joined string with the server seed as the HMAC key, then read the leading hex characters. That single number decides the outcome.
| Input | Example value (illustrative) | Role |
|---|---|---|
| Server seed | 9c1f4b...a7e2 | HMAC key, revealed on rotation |
| Server seed hash | sha256: 4d8b0c... | Commitment published before the bet |
| Client seed | quiet-harbor-19 | Player-supplied entropy |
| Nonce | 1 | Bet counter inside the seed pair |
| Joined message | quiet-harbor-19:1 | String passed to HMAC-SHA256 |
| Result hash | HMAC-SHA256(server seed, quiet-harbor-19:1) | Feeds the outcome mapping |
- Join client seed and nonce with a colon: quiet-harbor-19:1.
- Compute HMAC-SHA256 with the server seed as key and that string as message.
- Take the first eight hex characters of the digest, for example 5b1e0c7a.
- Convert them to an integer and divide by 4,294,967,296 to get a value between 0 and 1.
- Map that value to the game range: a 1-in-2 game returns one side above 0.5, the other below.
Change any input and the result hash changes completely, which is the point. A one-character edit to the client seed, or a nonce moved from 1 to 2, produces an unrelated digest and a different outcome. If a rotated server seed no longer reproduces the hash published before the bet, that mismatch is the failure the method exists to expose.
Verifying a round in the verifier
Reading the bet history entry
Pasting seeds and nonce into the tool
Every settled bet keeps a record you can re-check later. Open Bet History, pick the round, and the entry shows four values: round ID, server seed hash, your client seed and the nonce. Those four are all the verifier needs — no login token, no API key, no message to support.
- Bet History, settled round: copy the server seed hash exactly as it was displayed before the round.
- Paste it into the verifier with your client seed and the nonce printed on the entry.
- Run the check: the tool hashes the seed pair plus nonce and rebuilds the round hash.
- Compare the rebuilt hash, character for character, against the round hash shown on the entry.
| Bet history field | What it is | Verifier input |
|---|---|---|
| Server seed hash | The commitment published before the round | Top field, pasted unchanged |
| Client seed | The value you choose and can change any time | Second field |
| Nonce | Counter of bets placed under one seed pair | Third field |
| Round hash | The output the operator published for that bet | Compared with verifier output |
A match is the confirmation signal: identical inputs produced identical output, so the round was not rewritten after you bet. If the strings differ, re-copy the four values instead of editing them — a truncated hash or trailing space causes most false alarms. Readers who prefer to check outside the platform can follow the manual method on this page and hash the inputs in any SHA-256 tool.
Seed rotation and changing your client seed
When a server seed is retired
Effects of changing the client seed
A seed pair stays live until you rotate it or the operator retires the server seed. On rotation, the old server seed is published in full and the hash displayed at the top of the fairness panel is replaced by a new commitment. That reveal is the purpose of the model: the seed your bets were drawn against becomes checkable, so finished rounds can be verified after the fact.
- Rotate on demand from the fairness panel; a new server seed hash appears before your next bet.
- Automatic retirement is tied to a published bet count per pair; the counter is visible in the panel.
- After retirement the previous server seed is shown unhashed and stays in your rotation history.
- Changing the client seed starts a new pair and resets the nonce to 1 for the next round.
| Action | What happens next | What happens to past rounds |
|---|---|---|
| Change client seed | New seed pair, nonce restarts | Unchanged; original inputs still verify |
| Server seed retired | Commitment replaced by a fresh hash | Old seed revealed and verifiable |
| Manual rotation | Nonce returns to 1 under the new pair | Both seeds stay in your history |
Changing your client seed never rewrites history. The nonce restarts, the pair is new, and every bet placed earlier can still be checked with the seeds that were live at that moment. Verification works because the inputs are frozen per bet, not because the record is kept current.
Provably fair questions
Can a client seed be set per game
What if a verification fails
Support questions about fairness tend to repeat. Two come up most: whether one client seed covers every game, and what to do when a hash does not match. The answers below set out the seed model used here and the evidence support needs before a round can be investigated.
- One global client seed covers casino and sportsbook unless you set a per-game override.
- Per-game seeds keep their own pair and nonce, listed in that game's fairness panel.
- Before reporting a mismatch, re-copy all four values from the bet history entry.
Can I set a different client seed for each game?
Yes. The fairness panel allows a per-game override, so slots and live tables can run on separate seed pairs with separate nonce counters. Switching back to the global seed resumes the counter for that original pair where it stopped. Past rounds keep whichever seed was live when they were placed.
What if a verification fails?
Re-copy the four values from the entry before assuming a mismatch — a truncated hash or a stray space accounts for most failures. If the rebuilt hash still differs, export the bet entry, note the round ID and timestamp, both hashes, and the seed pair, and send them to support. A round can only be re-checked if all four inputs are supplied.