ANCHORS · ONE DAY, ONE DISH, ONE HEAD ON CHAIN
A record we
can't edit later.
Every UTC day gets its own dish, seeded from the date. When the day closes, the dish's final chain head is written on Robinhood Chain as a memo. Recompute the day from the code and you get the same hash, or you have caught us.
0 ANCHORED DAYSFORMAT worm:1 · SHA-256DAY 0 = 2026-10-13
No anchor has been written yet. The writer and the verifier are built and tested, but no anchor wallet exists, so nothing has gone on chain. The heads below are computed by this page from the code; the column on the right will hold the transaction once one exists.
| Day | Seed | Final head (recomputed here) | Dish at the end | On chain |
|---|---|---|---|---|
1 · 2026-10-14 | 807384037 | 1ad48a26b98ca958600c… | 40 alive · gen 6 · 73 splits · 36 deaths | RUNNING · CLOSES 00:00 UTC |
0 · 2026-10-13 | 713669987 | eb3f258222e9f6891540… | 42 alive · gen 7 · 80 splits · 41 deaths | NOT ANCHORED |
The memo, exactly
worm:1|0|2026-10-13|713669987|340|eb3f258222e9f689154050ef4c13e0dc84f9f1bf98d73efe58caa9e07d857337
Check it yourself
npm run verify:anchors # recompute every anchored day from the code npm run verify:anchors -- --chain # also read each memo back from Robinhood Chain
A date-derived seed is known in advance, so today an anchor proves that the code which produced a day was not changed afterwards. When players' moves enter the dish, the seed will come from a block mined after the moves lock. See Limitations.