Client Seeds

What a client seed is for

A client seed is the player-controlled string in CSGOEmpire’s documented case-opening, bonus-case and daily-case fairness recipes. Official help describes it as user-defined, or random by default. Its job is to be mixed into the hashed message so the ticket is not computed from operator-held inputs alone.

That is a fairness feature, not a loot feature. You cannot type a lucky phrase and force a knife. The algorithm still maps a digest onto a ticket range the case already published. What you can do is contribute entropy that was not chosen solely by the server, then later replay the same string when you check an open.

Where you edit it

Help articles for cases, bonus cases and daily cases all point at the same control: https://csgoempire.com/fairness, Info tab. The server seed is hashed there until you regenerate it; the client seed is the field you are allowed to replace.

Only change it on the official hostname. A “fairness” page on a lookalike domain is a phishing pattern, not a seed editor. This website has no seed field and will not add one.

Which games use it

Documented client seeds belong to inventory-style opens:

• Paid cases — server seed, nonce, client seed, ticket quantity. Help’s current recipe also mixes in the length of the client seed.
• Bonus cases — the same family of inputs plus a case-number variable that increments with tier.
• Daily cases — server seed, nonce, client seed, quantity, without the bonus case-number field.

Roulette’s second seed is a public seed generated daily (five pairs of numbers from 01 to 39 in the help example), not a string you type. Coinflip’s public seed is an EOS block id. Calling those “client seeds” will send you to the wrong help article.

Defaults and changes

If you never touch the Info tab, official help still treats the client seed as an input — typically a random default. Verification still requires the actual string that was in force for that nonce, not a seed you invented later.

Edits apply going forward. Opens already recorded were hashed with the old client seed, the nonce at that time, and the server seed then committed. Changing the field does not reroll a spinner you already watched. Official case help is explicit that the spinner was visual anyway; the ticket existed when you clicked open.

How it combines with other inputs

Help’s current case and daily-case outline builds a message from the client seed, the client seed’s length, and the nonce, then uses HMAC-SHA256 with the unhashed server seed as the key. Bonus cases substitute a case-number into that message instead of the length field. The digest is turned into a number in the ticket range (help uses a six-byte-style conversion into a 0–1 value, then multiplied by quantity, then plus one).

You do not need to memorise that arithmetic to use the site. You do need to know that omitting the client seed, using the wrong nonce, or verifying with a server seed from a different rotation will not match history. Full operator scripts live in Help Centre articles; this page will not paste them.

Ticket quantity is a property of the case, not of your seed. Help’s case article uses the example of 10,000 tickets per item. Battles currently document 100,000 tickets and do not use a player client seed at all.

Misconceptions

A custom client seed is not an edge. It does not cancel the documented 8.8% house edge on cases. It does not mean CSGOEmpire.help verified your open. It does not apply to match betting. And it is not a password — still, do not paste it into untrusted “verifiers” that also harvest session cookies.

For the operator-held half of the pair, read server seeds. For the counter that walks with each open, read nonces. Mode walkthroughs: case fairness.