Provably Fair

Caserandom aims to provide transparent randomness for CS2 case opening style entertainment. This page explains what “provably fair” means, what information you may see in the interface, and how you can independently verify outcomes when verification data is available. Provably fair does not change the fact that results are random. It is designed to let you check that the platform followed the stated process and did not alter outcomes after the fact.

What provably fair means

In a traditional system, users must trust that the operator generated results fairly. A provably fair system adds cryptographic commitments that can be checked by users. The core idea is that Caserandom commits to a secret value before play, then later reveals it. If the revealed value matches the earlier commitment and the result matches the published algorithm, the outcome can be verified.

Key components you may see

Depending on the game mode, Caserandom may display some or all of the following:

Server seed, a secret random value generated by the platform.
Server seed hash, a published hash of the server seed used as a commitment.
Client seed, a value set by you or assigned to your account for additional transparency.
Nonce, a counter that changes each round so the same inputs cannot produce the same result repeatedly.
Algorithm description, an explanation of how the final outcome is derived.

How the commitment protects users

The server seed hash is shown before outcomes are determined for a sequence of rounds. A cryptographic hash function is designed so that you cannot practically reverse the hash to get the server seed, but you can easily confirm later that a revealed seed matches the earlier hash. This prevents changing the seed after seeing the result, because any change would produce a different hash.

How outcomes are derived

While exact mechanics can differ by game mode, a common approach is to combine the server seed, client seed, and nonce into a single string, run it through a hash function, and then map the hash output to a number range used by the game. That mapped number can determine an item selection, a roll, or another outcome. If the mapping is published and stable, you can reproduce the same number independently.

What provably fair does and does not guarantee

Provably fair helps you verify process integrity. It does not guarantee that you will win, that you will receive a high-value item, or that results will be profitable. Randomness can produce short streaks or unlucky runs. A fair system can still feel harsh because probability does not balance out in the short term.

Step-by-step verification guide

The steps below describe a general verification workflow. The interface wording may differ, but the logic remains similar.

Open your history and select the round or case opening you want to verify.
Copy the server seed hash that was shown before the round was played.
Locate the revealed server seed for the same round or seed period.
Hash the revealed server seed using the stated hash function and confirm it matches the previously displayed server seed hash.
Copy the client seed and nonce shown for the round.
Combine the inputs in the order specified by the platform and run the stated algorithm to compute the verification output.
Compare the computed output to the recorded result shown in your history.

Common verification mistakes

Using the wrong nonce, especially when verifying multiple rounds in sequence.
Copying inputs with missing characters or extra spaces.
Verifying a round from a different seed period than the one that produced the result.
Applying a different encoding than the one specified, such as using a different case or separator.

Client seed control

Where the platform allows it, you can change your client seed to introduce a user-controlled element to the randomness. Changing the client seed does not let you predict results. It helps ensure the final output depends on both platform and user inputs. If client seed controls are available, you should only change the seed through the official settings and keep in mind that verification requires the exact seed used at the time of the round.

Seed rotation and transparency

For practical security, server seeds are typically rotated. A rotation means the platform stops using one server seed and begins using another, publishing a new commitment hash. Once rotation occurs, the previous seed can be revealed so users can verify rounds that used it. This approach balances transparency with security by not revealing the active server seed while it is still in use.

Fairness and platform integrity

Provably fair verification is one part of integrity. Caserandom may also use monitoring and controls to detect automation, multiple-account abuse, and other behaviour that can harm fairness. If you believe you have found a technical issue affecting fairness, contact support and provide the round identifiers and any relevant screenshots from the verification screen.

Responsible play reminder

Caserandom is intended for adults and outcomes are random. If you are in Australia, consider setting personal limits and taking breaks if play stops being enjoyable. If you need help, seek independent support services available in your state or territory.

Contact us

Questions about verification can be sent to support@case-random.com. Include the specific round or case opening reference so we can assist more efficiently.