Question 1

Can a player verify an active seed before the server reveals it?

Accepted Answer

The player can confirm that the server published a commitment. The player cannot fully recalculate past rounds until the server reveals the hidden seed. The interface needs to show the seed cycle status and expected reveal rule.

Question 2

Does a client seed need strong randomness?

Accepted Answer

A predictable client seed does not expose the hidden server seed. It can still weaken the independence of the player contribution. The player gains more protection when they create a fresh value after receiving the server commitment.

Question 3

Can an operator delete old seed cycles after rotation?

Accepted Answer

No. Rotation ends active use of a server seed. It does not end the evidence duty. The platform needs to retain commitments and reveal seeds and receipts for its required dispute and audit period.

Question 4

What happens if the revealed seed does not match?

Accepted Answer

The player needs to preserve the round receipt first. The operator then needs to check the seed cycle and nonce, input format, and mapper version. A genuine mismatch requires the platform to stop the affected game version. It also requires a defined incident and player remedy process.

Question 5

Can a Bitcoin transaction ID act as the client seed?

Accepted Answer

Some Bitcoin casino games accept a transaction ID as input. That value may already be public or known to the operator before commitment. It cannot provide strong independent entropy in that order. A fresh player value after commitment gives a cleaner trust boundary.

Provably Fair Bitcoin Games: How Results Are Verified