two sites I've been poking at lately take different approaches to provably fair and I figured it's worth a side by side because people throw the term around without checking what's actually under it.
setup A: lets you rotate your client seed whenever you want and shows the hashed server seed up front. standard model. you set a client seed, they commit to a hashed server seed, you play, you can verify each result against the hash after.
setup B: same commit step, but it forces a full server-seed reveal and rotation after a fixed number of bets, then publishes the old seed so you can batch-verify a whole block of results at once.
A gives you control on demand. B gives you a clean auditable block but on their schedule. I lean B for actually catching funny business because you can replay a chunk of history in one go, but A feels better day to day.
which do you trust more, and why
client-seed rotation vs full server-seed reveal, which fairness setup do you trust
- ledger_mott
- Posts: 12
- Joined: Mon Jun 01, 2026 2:34 pm
- nonce_nick
- Posts: 8
- Joined: Mon Jun 01, 2026 2:34 pm
Re: client-seed rotation vs full server-seed reveal, which fairness setup do you trust
B, easily, and it's not close from a verification standpoint.
the whole point of provably fair is the server commits to a seed via the hash BEFORE you bet, then you check the reveal matches. with A you control your client seed but you're verifying one result at a time, which is tedious and honestly most people never do it. so the guarantee exists but nobody exercises it.
B forcing a reveal on a schedule means the old server seed becomes public and you can hash it yourself and replay every result in that block. one script, whole block verified. that's a real deterrent. the nonce sequence has to line up too or the math breaks, and that's exactly what catches a rigged shuffle.
the whole point of provably fair is the server commits to a seed via the hash BEFORE you bet, then you check the reveal matches. with A you control your client seed but you're verifying one result at a time, which is tedious and honestly most people never do it. so the guarantee exists but nobody exercises it.
B forcing a reveal on a schedule means the old server seed becomes public and you can hash it yourself and replay every result in that block. one script, whole block verified. that's a real deterrent. the nonce sequence has to line up too or the math breaks, and that's exactly what catches a rigged shuffle.
-
seedphrase_sasha
- Posts: 13
- Joined: Mon Jun 01, 2026 2:34 pm
Re: client-seed rotation vs full server-seed reveal, which fairness setup do you trust
I'll push back a little on nick. both are fine cryptographically, the difference that actually matters is buried in the bonus and bet terms, not the seed model.
I ran setup A for a couple weeks. rotated my client seed, verified a handful of results by hand, all clean, hash matched every time. then I read the fine print and the wagering requirement on their bonus quietly excluded half the games I was verifying. so the dice were provably fair and the promo was provably useless.
my point: people obsess over which seed scheme is purer and ignore that a fair RNG attached to predatory terms still takes your money. check both. verify the seed AND read the terms.
I ran setup A for a couple weeks. rotated my client seed, verified a handful of results by hand, all clean, hash matched every time. then I read the fine print and the wagering requirement on their bonus quietly excluded half the games I was verifying. so the dice were provably fair and the promo was provably useless.
my point: people obsess over which seed scheme is purer and ignore that a fair RNG attached to predatory terms still takes your money. check both. verify the seed AND read the terms.
- degen_dana
- Posts: 11
- Joined: Mon Jun 01, 2026 2:34 pm
Re: client-seed rotation vs full server-seed reveal, which fairness setup do you trust
real talk, high volume here, A is the only one I'd actually use day to day.
B sounds great on paper but forced rotation every X bets screws up my flow when I'm grinding fast. and let's be honest nobody at my volume is replaying "a whole block" by hand. the audit feature is theater for 95% of players.
fair point from sasha though, the terms are where they get you, not the dice.
B sounds great on paper but forced rotation every X bets screws up my flow when I'm grinding fast. and let's be honest nobody at my volume is replaying "a whole block" by hand. the audit feature is theater for 95% of players.
fair point from sasha though, the terms are where they get you, not the dice.
- blockchain_bri
- Posts: 12
- Joined: Mon Jun 01, 2026 2:34 pm
Re: client-seed rotation vs full server-seed reveal, which fairness setup do you trust
methodically, I'd say they're solving two different problems so the "which is better" framing is a bit off.
A optimizes for player control and trust on demand. B optimizes for auditability after the fact. a thorough operator would offer both, on-demand client rotation plus a periodic server reveal, and the ones that only do one usually picked the cheaper one to implement.
the tell for me: does the reveal actually publish the old seed somewhere you can pull it, or do they just say they reveal it. mott, on setup B can you actually grab the historical seed and replay, or is it a claim in a help doc. that's the line between provably fair and marketing-fair.
A optimizes for player control and trust on demand. B optimizes for auditability after the fact. a thorough operator would offer both, on-demand client rotation plus a periodic server reveal, and the ones that only do one usually picked the cheaper one to implement.
the tell for me: does the reveal actually publish the old seed somewhere you can pull it, or do they just say they reveal it. mott, on setup B can you actually grab the historical seed and replay, or is it a claim in a help doc. that's the line between provably fair and marketing-fair.