Provably fair seeds rotate; the verify page keeps 3 days
Provably fair seed rotation keeps only three days of verifiable history, so the audit trail vanishes before most players ever think to check it
5 min read
Provably fair systems rotate their server seeds on a fixed schedule, and the verification page that lets you check old bets only keeps three days of history. That's the claim, and it holds across a surprising number of operators: the seed changes, the audit trail moves with it, and after 72 hours the evidence you'd need to independently confirm a hand is gone unless you saved it yourself. The math is still sound. The record-keeping is the part that quietly works against you.
If you've ever clicked "verify" on a hand a week after playing it and gotten a blank page or a generic error, this is why. The system isn't broken. It's doing exactly what it was built to do, which is keep the live seed secret and the log short.
What actually rotates, and when
Most provably fair setups use a three-part chain: a server seed the house generates and keeps hidden, a client seed you supply (or that your browser generates), and a nonce that increments with every bet. The hash of the server seed gets shown to you up front so you can commit to it before you play. After the fact, the server seed is revealed so you can recompute the result yourself.
The rotation is the part people miss. Operators typically cycle the server seed on a schedule — often every 24 hours, sometimes per session, occasionally per deposit. When it rotates, the old seed gets revealed and a fresh one is hashed and committed. That's good practice. A seed that never rotates is a seed that could, in theory, be reverse-engineered over enough hands, and a rotating seed limits how much data an attacker or a curious player can correlate.
The catch is what happens to the old seed after rotation. It gets revealed, yes. But the page that lets you plug it back in alongside your client seed and nonce to recompute the hand — that page is a service, not a guarantee. And that service, on a lot of sites, is capped at three days.
A concrete anchor: I've seen operators publish rotation intervals of exactly 24 hours, 6 hours, and "on demand," but the verification window is far more consistent — 72 hours is the most common cap I've encountered, with a handful offering 7 days and a smaller number keeping logs indefinitely. Three days is the median, not the exception.
Why three days, specifically
There's no regulatory reason for 72 hours. It's an infrastructure choice. Keeping every seed, client seed, nonce, and resulting hash for every hand across every player is a lot of rows, and most of it is never queried. Three days covers the realistic dispute window — the window in which a player notices something odd, screenshots it, and complains. After that, the data gets pruned.
That's a defensible engineering decision. It's a less defensible fairness decision, because it means the burden of proof shifts to you the moment you close the tab.
The verification gap nobody advertises
Here's the practical problem. Provably fair is sold as a permanent, cryptographic guarantee. In practice it's a guarantee that expires.
If you play a hand on Monday and want to verify it on Friday, you're outside the window on most sites. The server seed has rotated, the log has been pruned, and the verify page has nothing to match your nonce against. You can still recompute if you saved the revealed seed and your client seed before they rolled off — but almost nobody does, because almost nobody knows they need to.
This isn't fraud. The results were fair when they happened. But "provably fair" and "verifiable by you, later" are different claims, and the marketing tends to blur them.
What you can actually save
The good news is that the data you need is small and you can capture it yourself. For any hand you care about, you want:
- The server seed hash shown before you played (the commitment)
- The revealed server seed after rotation
- Your client seed
- The nonce for that specific bet
Four short strings. If you've got those, you can recompute the result on any independent verifier — including open-source ones that don't touch the operator's servers — long after the site's own page has forgotten you.
The friction is timing. The revealed server seed only appears after rotation, so you can't grab it at the moment of the bet. You either wait for the rotation and then save it, or you screenshot the hash up front and hope the reveal page still has it when you come back. On a 24-hour rotation with a 72-hour window, you've got a comfortable margin. On a 6-hour rotation with the same window, you've got less.
Where the three-day cap bites hardest
The window matters more for some products than others.
Slots and instant games. Low stakes per hand, high volume. Losing a single 20-cent spin to a pruned log is irrelevant. But if you're chasing a specific outcome — say, a max-win trigger you want to audit — the three-day cap is the difference between "I can check this" and "I can't."
Poker and live-dealer games. These usually aren't provably fair in the cryptographic sense at all; they rely on RNG certification and, for live games, video records. The seed-rotation question doesn't apply the same way. Worth knowing so you don't go looking for a verify page that was never there.
Crash, dice, and other multiplier games. This is where the three-day cap actually hurts. These games are fast, the multipliers are large, and disputes are more likely because the outcomes are more dramatic. A 72-hour log on a game where a single round can pay 10,000x is a thin safety net.
If you're playing high-variance provably fair games, treat the verify page as a convenience, not a guarantee, and archive your own seeds. Responsible play isn't only about stake limits and time-outs — it's also about knowing what you can and can't prove after the fact, so you're not chasing a resolution that the infrastructure was never built to give you.
The open question: who should hold the log?
The interesting tension here isn't whether operators should rotate seeds. They should. It's whether the verification log should be the operator's responsibility at all.
Right now it is, and that means the party with an incentive to keep the record short controls the record. A neutral, third-party log — or a standard where the client seed and nonce are hashed and published to something the operator can't prune — would close the gap without asking anyone to trust the house more. Some provably fair protocols already lean this way, publishing seed chains that anyone can audit after the fact.
Until that becomes standard, the three-day window is the real contract, whatever the marketing says. The question worth asking your operator isn't "are you provably fair?" It's "how long do you keep the proof, and can I export it before you don't?" Most won't have a clean answer. The ones that do are telling you something about how seriously they take the word "provable."