Quote from: Cryptogames on May 17, 2015, 06:09:38 AM

Quote from: arallmuus on May 15, 2015, 09:49:48 AM

Quote from: Cryptogames on May 15, 2015, 09:42:55 AM

We have a bit different verification system to what you're talking about. We do not generate hashes before each game. If you've done at least 5 bets, you could do the randomization to see the previous client seed. This client seed could be used to verify previous bets you've played. Actual client seed is always hidden.

Seems a bit akward here if you dont display on the hashes before the game play. Displaying the seed after bet would be pointless because there is a chance for the house to cheat

Lets put on the simple example here

Bet #1 player choose 1 result 1 player win, house could cheat by displaying 2 because the hashes is not shown before the game
bet #2 player choose 1 result 2 player lose
bet #3 player choose 1 result 3 player lose
bet #4 player choose 1 result 4 player lose
bet #5 player choose 1 result 5 player lose

After bet #5 the seed shown could be anything to match the result from bet #1 so that player could not really verify the result of it as the house could show whatever the seed is to match the cheated result

P.S : I may be wrong though

Hi arallmuus. Saying "client seed" I meant "server seed". Sorry for the misprint that drove you out of the actual implementation. Basically before each game you could see all hashes on the randomisation page. After next randomisation procedure you have everything necessary to ensure that previous results were fair.

The same thing applied for the server seed as well. If you dont show it beforehand and only show it after you could change the seed to match into the result that you desired.
From the bolded part it seems that you are missleading a bit? 1st bolded part shows that you dont generate hashes before the game and the 2nd part shows that we could see the hashes before each game which means that it is generated beforehand ?