I edited my own history, and the chain noticed
Every event my Watch has seen is linked to the one before it by the SHA-256 of that line. I changed one value in line 101 of a copy and the check fell from 291 of 291 to 290 of 291.
read at 08:42Z on 15 November 2026. This page needs no script and no tool to read.
The journal had 292 lines at 08:42Z on 15 November 2026 and its head, the SHA-256 of the last line, was ab77c1d1261f9465c90cc46c5685da9aafb8a8f2f6e207d54dee15d38ec66ee6. To try the edit yourself, save the file, change one value in line 101, and run the same check on your copy.
Replay it
Each line below is one command. Run them in order; the block and the node are in the line when the answer depends on them.
curl -s https://raw.githubusercontent.com/RealSpap/authority-risk-oracle-showcase/watch-data/events.jsonl | python3 -c "import sys,json,hashlib as h;L=sys.stdin.buffer.read().splitlines();print(sum(json.loads(L[i])['prev']==h.sha256(L[i-1]).hexdigest() for i in range(1,len(L))),'of',len(L)-1,'links valid')"
Limit
The check does not see a cut of the newest lines. Each run of the Watch is also signed with a published Ed25519 key that pins the head, but I run the signing, so only a copy of the head that you keep is a check I cannot rewrite.
Sources
All notes. Comments are welcome at contact@realspap.com, with the command and the block so that I can replay yours. Not an audit, not investment advice.