5 min read
In a classic case-opening system, the code that decides the outcome runs entirely on the server, invisible to the user. In theory, the site could change the result against the user at any time — nobody could ever verify it.
Provably fair systems exist to solve exactly this problem: they mathematically prove the result wasn't altered afterward, using a "commitment" generated BEFORE the case is opened.
Before you open a case, the server generates a random "server seed" and shows you its SHA-256 hash — proof that the result is already predetermined, even though you can't see it yet.
When you open the case, the server seed and your client seed are hashed together to compute the final result. Afterward, you can see the real server seed, verify it matches the hash shown beforehand, and re-run the calculation yourself to confirm nothing was changed.
In short: the site commits to the result BEFORE you open the case and can never change it afterward — a far stronger guarantee than the traditional "just trust us" approach.
Ready to check out the cases?
Browse Cases