In OP I only said "
- The user probably wants the hashed audit seed in advance, but this could be possible I think." but I will explain that further.
1. The dice site generates a server seed, he will request a server-seed-hash-specific audit seed HASH too. And shows it to the player.
2. The player makes a bet with his client seed.
3. Dice site sends bet information (with server HASH and other details including amount,chance,etc so this can't be changed after the result) to the audit server. Audit server uses nonce (and checks if it's sequel) + audit seed to calculate the SHA512 of that combination. And returns that.
4. Dice site uses: client seed, server seed, nonce, SHA512 of audit seed + nonce > to calculate outcome.
5. Gives result to player and repeat.
In the end the player can request a new server+audit seed. So this will:
1. Player generate new seeds.
2. Dice site requests the audit seed with the original audit HASH and the server seed. Audit server gives audit seed and makes that seed invalid for future bets. With the server seed the audit server could recalculate all bets of this session.
3. Dice site returns the server + audit seed to the player.
4. Player can recalculate all bets with those seeds. He can also check the audit website with his audit seed to check all recalculated bets.
Still I think the "site profit" could be faked. So there would have to be a daily, weekly or monthly verification.
1. Dice site generates new server seeds.
2. Dice site sends old server seeds to audit site.
3. Audit site recalculates all rolls and can even calculate the site profit this way.
It helps against:
- skipping nonces / changing seeds etc
- easier verification for players
- fake whales and/or profit (loss)
- hackers cannot win with a server seed or cheat unnoticed
Would that work?
Obviously, once again, players+investors would need to trust the audit server. But it's better because BOTH the dice site and audit site would need to collude/cheat together. Is it worth the trouble? Not sure