Show Posts
Warning, Site operator refuses to back up their claims of "provably fair".
My outstanding concern is that the client side RNG is not easily verifiable for the end user and the user cannot set their own seed.
The site can easily insert a predictable client side RNG every N refreshes to take advantage of players.
My outstanding concern is that the client side RNG is not easily verifiable for the end user and the user cannot set their own seed.
The site can easily insert a predictable client side RNG every N refreshes to take advantage of players.
Regarding our game being probably fair anyone is free to refresh the page as many times as they'd like to check whether the client-side seed is being sourced from anywhere other than a locally seeded RNG. This is all independently verifiable, just like every other provably fair system.
If SatoshiCircle were to be influencing the spins, we would have a very high risk of being caught by anyone doing a simple audit of the Javascript. We encourage anyone to audit our code. It's out there for anyone to see.
Instead of requiring a high level of technical knowledge and auditing javascript why not the following which I have suggested several times to you before:
I suggest providing a hash of the client side RNG and allowing users to provide their own seeds.
Providing a hash of the client side RNG generator itself and a verification method is also recommended.
Yeh something like what Bitzino does with client seeds. It'd also make me feel a lot safer as well tbh.
Your post isn't gonna help you lower the price xD
