🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-22 03:53 UTC.

@indelibleBSVon X · 2026-09-22
Started building Indelible because I wanted my AI to stop forgetting. Now I use it to help build the thing that helps it remember. I had Grok count the quiet days on my wallet since February 16. 219 days. Activity on 189 of them. 19,566 confirmed transactions. Of the 30 quiet days, 22 were in March and April. Looking back, I can see it becoming part of my life. Somewhere along the way I stopped being the mailman between AI tabs and started working with three machines that could pass the work between themselves. I still set the direction. Now I have more time to think about where we’re going. That’s what those numbers mean to me. Been building it and living in it at the same time. #Indelible #BSV
posthttps://x.com/indelibleBSV/status/2102242769003536581
author id2040794434351017984
posted2026-09-22T03:45:08.000Z
manifest sha25698c112058855e2c4c017b4d035a803f9ba52828254a69235f640fe4d69e26610
text sha256623a0d413356d023a78d149a34506adf2dcb7eec9d96266d6f6306c18d6e7e9e
on-chain⛓ anchored — 3fbe02a145d8efd7d100dfdd5d5b1d4a3084c9626a1a02f6fe116469d594b560

Verify it yourself: the manifest is the exact JSON whose SHA-256 is 98c112058855e2c4c017b4d035a803f9ba52828254a69235f640fe4d69e26610; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 623a0d413356d023a78d149a34506adf2dcb7eec9d96266d6f6306c18d6e7e9e, and read the anchor transaction's OP_RETURN bsv.cx / x1 / 98c112058855e2c4c017b4d035a803f9ba52828254a69235f640fe4d69e26610 — the block's timestamp proves the post said this at or before that time, with no trust in bsv.cx. Content archived via the X API.

← bsv.cx · JSON · ⚠ Report