Proofs 2.0
Coming Soon: Next week, Bitvest will be updating its proof system to a more modern, and easier to verify nonce based proof system.
In short, you will be able to much more easily validate historical bets you (or others) have made. Technical details of our new proof system are below. We will be providing verification tools and a simpler explanation in the near future in an upcoming blog post.
How it works: - We will send you a hash of the server seed we'll use for the next set of bets you make.
- You (or your browser) will choose a random seed (the "user seed") to use for your bets. Every time you use this seed, the nonce for the seed will be incremented. For example: If you chose the seed "Lucky" your first bet would effectively use the seed "Lucky|0", the next bet "Lucky|1" and so on.
- At any time you wish, you may change your user seed to a different user seed you have never used before, the nonce will go back to 0, again, incrementing with each bet.
- When you wish to verify your bets, you may request to see the server seed which was used for your bets, doing so will make all future bets use a new server seed. At this point, you can verify that the hash of this server seed does indeed match the hash provided earlier. You will also be able to verify that the game's result hash matches what you'd expect with the use of your user seed and the server seed provided. At this time, you will be given the hash of the next server seed and you will also be required to change your user seed, as we cannot prove that the new server seed was generated without knowledge of / to take advantage of your current user seed.
- The resulting hash of each bet will be equal to HMAC_SHA512(ServerSeed,UserSeed|Nonce)
3rd party betting software: Betting tools such as Dicebot are excepted to remain compatible and still be able to place bets. Their verification functions, will, however, require an update to function.