@RHAvar The client seed in compare to the server seed only looks like hashed, in fact, it is definitely not.
Obviously..
As you can notice in a provably fair checker, the client seed is public as well as a nonce. Simple saying the client seed is just a random generated string that works equally to the manually provided string by a user.
It doesn't matter if it's public, it's exclusively picked by and controlled by the server (which knows the unhashed server-seed). Your website description of a client seed is correct, and the the very name "client seed" makes it clear that it's a seed set by the
client after seeing the hashed server seed. Yet your site doesn't work that way. It can be done automatically (via client side random generation) but it should be set by the client, and absolutely must be allowing user input.
As it stand, the site clearly doesn't meet the standard threshold of "provably fair" and is imho engaging in pretty deceptive conduct by trying to explain away a major problem with technobabble.
---
Put another way, if you simply removed the "client seed" the player would have
exactly the same guarantees -- which just makes the whole client-seed as implemented by your site purely smoke-and-mirrors.
