Diary Mode
Every round, the console can produce a proof — a SHA-256 fingerprint of the game state. Optionally, that fingerprint can be posted to the XRPL Testnet.
How it works
Section titled “How it works”- End a round — generates a proof hash of the full game state
- Create a wallet — free Testnet wallet (test XRP has no value)
- Anchor the proof — post the hash to the XRPL Testnet
- Verify later — anyone can check the proof against the on-chain record
sov end-round # generate proofsov wallet # create testnet wallet (free)sov anchor # post hash to XRPL (optional)sov verify proof.json --tx <txid> # trust but verifyOnly the host needs a wallet. Nobody else touches a screen. The game works perfectly without anchoring — it’s just the diary that remembers.
Security
Section titled “Security”- Proofs contain hashes and state snapshots, but never wallet seeds
- The
.sov/directory is gitignored sov walletwarns about Testnet seed reuse on Mainnet- Proofs include player names and game state (scores, positions, promises) — share only with your play group
- Only the SHA-256 hash is posted to the ledger; the full proof stays local
Why anchor?
Section titled “Why anchor?”Anchoring is optional and educational. It demonstrates:
- How cryptographic hashes create tamper-evident records
- How public ledgers provide independent verification
- How trust works when you can prove what happened