Don't trust — replay
Everything below comes from public chain logs and the public drand beacon. The same open code runs on your machine.
Run it from a clone of the repo after pnpm install && pnpm --filter semalam build (the npm package is not published yet). Exit 0 prints the hash below and says MATCH.
✓ MATCH
- Result hash (runner artifact)
- 0x78d71f232eb1ce8bf9e50625d125d931f07de635dc859b8d32160612d4170c9e
- Result hash (on chain)
- 0x78d71f232eb1ce8bf9e50625d125d931f07de635dc859b8d32160612d4170c9e
- CLI cross-check (runner's fresh-process run)
- v0.1.0 · same hash
- drand round
- 33727112 · quicknet 52db9ba70e… · the runner and the CLI BLS-verify this beacon before replaying (packages/beacon); run the CLI to check it yourself
- Randomness
- 0x206310bd…f15a0b2f
- Players (accounts, house excluded)
- 0 (0 operator addresses excluded) · house-only night · excluded: 0x5b84f1, 0xaf3436, 0x944bc9, 0x0310dd
- Void commits
- none
- Commit logs read · policy set hash
- 0 · 0x569e75fc…71af0cfd
- Contracts
- Orders · Results · Scrimmage
- Commit transactions
- none
Your replay says ✗ MISMATCH? Re-run it with another node (--rpc <url>): one that has not indexed every commit log gives a false mismatch — compare the commit count and policy set hash above. Still different: the night is disputed. A post is final on chain and is never re-posted; open an issue on the repo with the CLI output. The full artifact is /api/round/4.
Orders compiled by the AI path are visible to the operator; the builder path never leaves the browser. Sealed orders cannot be read by anyone until the drand round above is published.
Replay