The Authority Report, number 0

Who can change what, replayed every Monday. This first number covers 202 targets on nine networks and ends with one question: would a protocol publish a commitment anyone could check every day?

202targets followed by the Watch

read at 07:14Z on 16 November 2026. This page needs no script and no tool to read.

The Authority Report, number 0. Who can change what, replayed every Monday.

1. What changed this week. The Watch follows 202 targets: 63 on Robinhood Chain mainnet (chainId 4663), 39 on Ethereum mainnet (chainId 1), 13 on Arbitrum One (chainId 42161), 13 on Base mainnet (chainId 8453), 14 on Tempo mainnet (chainId 4217), 9 on Plasma mainnet (chainId 9745), 9 on Monad mainnet (chainId 143), 16 on HyperEVM mainnet (chainId 999) and 26 on Solana mainnet-beta. In the seven days to 07:00 UTC on 16 November 2026, the chained journal recorded 3 admin changes, 6 upgrades, 4 score moves and 1 change of method. 5 alerts are active: 2 high and 3 medium.

2. Levels. Authority Levels are not published yet, so there is no promotion to report this week.

3. What I corrected. On 6 November I named the wrong ERC-8004 registry address in a public thread: the team's testnet entry, not the mainnet one. The dated correction is in the errata folder of the public repository.

4. A question for you. Would a protocol publish a commitment, for example a minimum delay and a minimum number of signers, if anyone could check it every day? What would stop you?

5. Replay. The journal has 305 lines, numbered 1 to 305, the last recorded at 06:40:51 UTC on 16 November 2026. Every line carries the SHA-256 of the line before it, and the SHA-256 of the last line is the head signed by the Watch: 32f85b3924b718cc639df2e103b077937e9acca069725e9099299de687d54a11. The chain does not see a cut of the newest lines unless you keep the head. The commands below read one fixed commit of the watch-data branch, so they give the same answer later.

Quoth the Raven: replay.

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 -o events.jsonl https://raw.githubusercontent.com/RealSpap/authority-risk-oracle-showcase/4e6a8b86f307f8035f64d36cf206b6b163abb52d/events.jsonl && python3 scripts/verify_chain.py --events events.jsonl --head 32f85b3924b718cc639df2e103b077937e9acca069725e9099299de687d54a11
curl -s https://raw.githubusercontent.com/RealSpap/authority-risk-oracle-showcase/4e6a8b86f307f8035f64d36cf206b6b163abb52d/events.jsonl | python3 -c "import json,sys;L=[json.loads(l) for l in sys.stdin if l.strip()];print(len(L),L[0]['seq'],L[-1]['seq'])"
curl -s https://raw.githubusercontent.com/RealSpap/authority-risk-oracle-showcase/4e6a8b86f307f8035f64d36cf206b6b163abb52d/events.jsonl | python3 -c "import json,sys,collections;c='2026-11-09'+'T07:00:00Z';e='2026-11-16'+'T07:00:00Z';print(json.dumps(dict(sorted(collections.Counter(json.loads(l)['kind'] for l in sys.stdin if l.strip() and max(json.loads(l)['run_utc'],c)==json.loads(l)['run_utc'] and min(json.loads(l)['run_utc'],e)==json.loads(l)['run_utc']).items()))))"

Limit

These are counts from one commit of the watch-data branch (4e6a8b86f3), not a judgement of any protocol. The journal starts on 10 October 2026: before that date it proves nothing. The Watch runs the signing, so only a head you keep yourself 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.