Publish the commitment.
The operator creates a random server seed and publishes its SHA-256 commitment before accepting the covered play. The player keeps that commitment with the round’s context.
GALABET LEARN / SEED LIFECYCLE
A seed has a working life.
Then it becomes evidence.
A commitment lets a player retain a reference before play. The seed becomes useful for checking results after it can no longer expose an unfinished game. Follow what each side can see at every stage.
Allocate each accepted round.
Bind the client seed, nonce and game parameters to the request. Distinct rounds under the same seed pair need distinct nonces. A retried request should recover the original round instead of consuming another nonce or stake.
Close the old seed’s work.
Stop allocating rounds to the old seed. Resolve any games whose concealed outcomes it could reveal. Prepare the next seed and publish its commitment before it is used.
Reveal, then reproduce.
Release the retired seed. A reader can first match its commitment, then recalculate each completed result using the saved client seed, nonce and parameters.
SUPPORT / KEEP THE ROUND TOGETHER
What to retain
Keep the original commitment, revealed seed, client seed, nonce, game and parameters, claimed result, and the application’s round identifier. For settlement questions, also retain the accepted action and balance receipts. The verifier checks the calculation record.