Case Opening Fairness

Generated when you click open

Official case-opening help is timed to the click, not to a UTC day and not to a future blockchain block. The result is generated as soon as a customer clicks to open a case. That is a different fairness shape from roulette (pre-generated daily tape) and from coinflip (EOS after join).

Because the draw happens immediately, the commitment has to live in seeds that were already hashed on the fairness page before the click: a server seed you have not yet rotated, a client seed you already set or left default, and a nonce that will increment because this seed pair was just used.

Odds, XP and the documented 8.8% house edge are in the cases game guide. This article is the ticket recipe.

Paid cases: four inputs

Help currently lists four generation variables for paid openings:

• Server seed — a cryptographically secure pseudo-random string, hashed until you regenerate it.
• Nonce — incremented every time the seed is used.
• Client seed — user-defined or random by default.
• Quantity — tickets available in the case. Help’s example: 1 item = 10,000 tickets, so an eight-item illustration is 80,000.

The current documented combination HMAC-SHA256-hashes a message built from the client seed, the length of that client seed, and the nonce, using the unhashed server seed as the key. The digest is converted through a six-hex-pair fractional value, multiplied by ticket quantity, then incremented by one to produce a ticket number. That is a summary of the Help Centre method, not a script you should copy from this website.

The spinner is visual only

Help states that the result is given out using the spinner, and that the spinner has no say over the actual result: it is a purely visual way of displaying the pre-generated outcome. If the animation feels “close” to a better item, that is presentation. The ticket was already fixed at click.

Complaints that the spinner “should have landed” on a neighbour are not fairness bugs under this documentation. If the ticket does not fall in the published range for the item you received, that is a different question — check the case’s ticket table on CSGOEmpire, then official support. Case-issue troubleshooting covers the practical checks.

Info tab: seeds you control

Both the hashed server seed and the editable client seed live on https://csgoempire.com/fairness under Info, according to case, bonus-case and daily-case help. Regenerating the server seed is how prior opens become checkable with an unhashed secret. Editing the client seed changes future messages, not past tickets.

Details: server seeds, client seeds, nonces.

Tickets and item ranges

After you have a ticket number, help says you click the case type to see quantity and to confirm that the ticket falls in the range for the item you received. Fairness here is two layers: the hash produced ticket 87,664 (help’s worked example), and 87,664 sits inside the published band for that skin.

A matching hash with the wrong item band would be a catalogue problem, not a seed problem. A matching band with the wrong hash is a seed or algorithm-version problem. This site will not classify your screenshot.

Bonus cases

Bonus-case help uses five variables: server seed, nonce, client seed, case number, and quantity. The case number increments depending on the case tier. That extra field is why two bonus tiers can share a seed pair without sharing a ticket. The hashed message in current help is client seed, case number and nonce — not the length-of-seed construction used for paid cases.

The spinner is again documented as visual only. Seeds are still managed on the same Info tab. XP, keys and cooldowns belong in the XP and bonus cases guide.

Daily cases

Daily-case help (February 2025 article) lists four variables: server seed, nonce, client seed, quantity. The result is generated when the customer opens the case. Ticket quantity is on the case type. Client seed and hashed server seed are the same Info-tab controls. The documented HMAC outline matches the paid-case family (client seed, length, nonce) rather than the bonus-case number field.

Accrual of daily cases from house edge is a rewards topic, not a fairness primitive. Do not confuse “how many dailies you earned” with “which ticket this open produced.”

Algorithm versions

Case help notes that openings before 18 April 2024 used a different published method. Bonus-case help lists still older cutovers (including dates in 2023 and 2019). If you are checking a historic open, the current article’s recipe may be the wrong one. Official help links those legacy runners; this site will not archive them as if they were current.

What a matching ticket proves

It proves that the documented function, with those seeds, nonce and quantity, yields the ticket attached to the item you were shown. It cannot prove you will profit on cases, that match betting is in scope, or that CSGOEmpire.help audited the open. We do not run verifiers. House edge remains 8.8% in the current cases article until CSGOEmpire changes it.

Multi-player opens of the same crates use a different EOS pipeline: case battle fairness.