I have some problem verifying my bet, and I would like to know if I did something wrong in the process.
Hash: FA0CDD2ADE57124373BF56A3F13F60E1DB2201FDAA2FA0A4C3567583F3095AC1
Number: AA67C03CC2B48EC04C2C61D30068A46DC449D808D14736DAFC680A6C76492F20
Server Seed: 0111001111
The "Hash" is supposed to be calculated as SHA256(SHA256(Ticket Number + '-' + Server Seed)), but SHA256(AA67C03CC2B48EC04C2C61D30068A46DC449D808D14736DAFC680A6C76492F20-0111001111) is b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d and
SHA256(b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d) is 6ee32217ef397baeacc6f04a3024f4b06bac56777bf56bf93a5bc1c25c078fee
Hash: FA0CDD2ADE57124373BF56A3F13F60E1DB2201FDAA2FA0A4C3567583F3095AC1
Number: AA67C03CC2B48EC04C2C61D30068A46DC449D808D14736DAFC680A6C76492F20
Server Seed: 0111001111
The "Hash" is supposed to be calculated as SHA256(SHA256(Ticket Number + '-' + Server Seed)), but SHA256(AA67C03CC2B48EC04C2C61D30068A46DC449D808D14736DAFC680A6C76492F20-0111001111) is b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d and
SHA256(b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d) is 6ee32217ef397baeacc6f04a3024f4b06bac56777bf56bf93a5bc1c25c078fee
Sorry I was busy last week and did not have the time to make an update on this. In fact, I received a PM from OP a week ago (just shortly after I raised the question).
Hey, thanks for verifying bets!
After first SHA256 everything is right as you use UTF8 and result is b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d, but for second SHA256 no need to use UTF8 as there is no string separator, so input of second SHA256 will be just binary representation first hash.
You can try it in Bitcore playground http://bitcore.io/playground/#/units bitcore.crypto.Hash.sha256(bitcore.util.buffer.hexToBuffer('b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d'))
After first SHA256 everything is right as you use UTF8 and result is b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d, but for second SHA256 no need to use UTF8 as there is no string separator, so input of second SHA256 will be just binary representation first hash.
You can try it in Bitcore playground http://bitcore.io/playground/#/units bitcore.crypto.Hash.sha256(bitcore.util.buffer.hexToBuffer('b765049511c7ee93d6ae9dcc9bd9125504cd90925f4ea04cff74b7767f1af76d'))
And that gives me the exact same hash I received before playing the game. Another way to do that is to use http://www.fileformat.info/tool/hash.htm to do the first hash as string and do the second hash as binary data.
TL;DR: The site is provably fair. The bet verification can be done easily. The OP is helpful and answers my question promptly.
Thanks for the update! So it looks like the site is worth trying.
As far as I understand the site works with Testnet Bitcoins which you can get free and with real bitcoins which you can deposit there right? So, no faucet with real bitcoins?
Website now works with real bitcoins, we updated it Yesterday, and preparing it for the final bug fixing and launch later this week. We will have "Demo Ticket" to try it for free.
) 
