Those methods are from the README in the gamebetr/provable repository, which is just for verifying bets and unrelated to whatever order the code actually uses. I do hope that they are setting the server seed before somehow randomly generating a client seed. Most sites prove this by having client side javascript randomly generate a seed on site load, but since GameBetr's dice seems to be created in Unity, I don't think it's possible. Unfortunately you'll have to trust them on that or set your own seed.


The 'independent 3rd party site' also sends a request to the server to get a result, rather than generating it on client side. I strongly suspect that it isn't exactly independent either, so GameBetr could technically cheat by faking results on the verification site as well and just hoping that players won't verify it themselves. It's pretty annoying to verify too, since it relies on PHP's specific implementation of Mersenne Twister.

Since they seem to use a unique approach to provably fair (it would have been much nicer if they just copied the standard nonce based method instead of trying to reinvent the wheel), I wrote a open source, and truly independent verifier that players can use if they want using purely client side JS. Here's an example of a verified bet.

I still wouldn't recommend playing their dice just because it seems to be pretty poorly made in general.