Semalam
Verify · round 15 · chain 4663

Don't trust — replay

Everything below comes from public chain logs and the public drand beacon. The same open code runs on your machine.

$ node packages/cli/dist/semalam.mjs replay 15

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)
0x6e1f6854eb5efb4dd5963ac43707621f8dd1a1991d66da8b0d65a8db28aeddba
Result hash (on chain)
0x6e1f6854eb5efb4dd5963ac43707621f8dd1a1991d66da8b0d65a8db28aeddba
CLI cross-check (runner's fresh-process run)
v0.1.0 · same hash
drand round
34043912 · quicknet 52db9ba70e… · the runner and the CLI BLS-verify this beacon before replaying (packages/beacon); run the CLI to check it yourself
Randomness
0x44b50cb4…5f724dc2
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/15.

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