ANCHORS / ONE DAY, ONE HEAD, ON CHAIN

A head this project
cannot edit afterwards.

Every closed UTC day, the day's last sealed chain head is written on chain as a memo. Recompute the day from the code and you get the same hash — or you have caught us. That is the whole point: the site can be changed, the chain cannot.

2 ANCHORED DAYSSHA-256 FROM SEASON 3RECOMPUTABLE BY ANYONE
01 · THE DAILY ANCHORS

What was written,
and what it commits to.

A memo of the form ffw:1|season|date|lastTick|chainHash. Season 0 was sealed with market/1 (FNV-1a); from season 3 the head is SHA-256. The head commits to every tick before it, including the ones nobody can change now.

CHECK IT YOURSELF — npm run verify:anchors recomputes every day in this list from the code; add --chain to read the memo back from a public RPC. Both the manifest and the status shown here are enforced by CI: tests/anchors.test.ts recomputes every anchor on every push and fails if a hash disagrees. A divergence is never silently re-anchored — it is marked here in red.
WHERE THIS LIST COMES FROM — the site's server, which is where the daily job appends each confirmed memo. The same file is published in the repository as anchors/anchors.json, and CI recomputes every entry in it on every push.
ANCHOR WALLET — EospJLqJohc5SV9JaSuejTxWb57XyVK3H4ECPw2H7vYF — the only key that writes these memos. It holds a few cents of SOL for fees and nothing else, and every memo it has ever sent is listed above.
MEMO FORMAT — ffw:1|1|2026-10-11|28799|34c9b98b (the latest entry, or season 0's head before the first anchor lands)