Our website is 100% fair.
It's basic maths.
We will wait for a trusted member to check the probability fair.
Im still waiting for that basic math. Surely if its that simple of math then its just as simple to explain how you get the roll number just using the server seed and server seed hash. Right?
You said on your chat that you do not have to prove anything to anyone, will you say the same on bitcointalk to the hundreds of people who have a right to know before they deposit money on your site?
Because some people seem to fail at understanding the various "Provably Fair" techniques... here is a quick run down:
1. "Nonce" method:
Server seed is "fixed" (server seed hash shown as proof) and Client Seed is "fixed" and has a nonce (basically an incrementing counter) added to end. Once you reveal the server seed, you can then validate all previous rolls, and server seed will then be changed and a new server seed hash provided.
Roll result is (usually) calculated by combining server seed, client seed and nonce and generating a HMAC-512 hash and then taking first X digits from the hex result (converted to decimal)
Server can theoretically calculate all future roll results (for the current server seed + client seed pair),
BUT CAN'T CHANGE THEM... That would break the server seed hash result.
DuckDice uses this method.
2. random Client Seed + random Server Seed method
Server seed changes every roll (server seed hash shown prior to each roll as proof), client has the option to change the client seed every roll if they want...
Roll result calculated by combining server seed + client seed and generating a HMAC-512 hash and then taking first X digits from the hex result (converted to decimal)
Server cannot know what any given roll result will be in advance unless the client is using a static seed and never changes it.
Crypto-Games.net uses this method
3. Server seed + Roll result method.
Server seed can change every roll or be fixed.
Roll result is pre-generated by the site before bet is made (method for generating roll result may be unknown/unpublished, but it is in the best interests of the site if it is properly random, otherwise someone could predict the patterns and ruin them)
Server seed + roll result are combined, SHA256/512 hash calculated and provided prior to bet being made as proof. NO Client Seed is used or required.
Once bet is submitted the server seed + roll result are shown (along with the previous hash for verification purposes)... new hash for next seed/roll result is generated and provided.
Server knows reach roll result BEFORE you place a bet,
BUT CANNOT CHANGE IT, because that would break the server seed hash.
ParaDice.io is using this method.
In my opinion, ParaDice.io probably shouldn't call the hash that they generate from the combined Server Seed + Roll Result, a "Server Seed Hash"... as technically, it isn't just a result of hashing the Server Seed... it is the result of hashing the Server Seed AND the pre-generated roll result combined. This may be causing some confusion.
Additionally, their provably fair system, is pretty cumbersome for the players... You can't go back and check historical bets and view the provably fair data for them... you would need to manually copy and save each "Server Seed Hash" prior to placing a bet... and double check it after each roll, which is just annoying
In any case, in ALL of these methods, even the ones where the server is pre-generating the result like ParaDice.io... the server cannot possibly change anything that the hash is related to, after it has been provided to the player. The maths of SHA256 (and 512 as applicable) make it, for all intents and purposes, impossible for them to modify anything... as (ironically) pointed out by MafiaCoin in his "Scam" accusation, if they change anything, it breaks the hash calculation.
