🐦 Archived X post

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

@jmorpusson X · 2026-09-22
"Here is my story, 12 years ago I awoke in the middle of the night in excruciating pain in my legs, a piece of calcium had broken of from the main artery that supplies blood to my legs blocking at the junction I had to have a double bi-pass, they thought I my loose a leg because of the lack of blood flow. I seen my vascular surgeon and told him what I thought caused this calcification. For over 20 years I carried my mobile phone clipped to the back of my nail bag up against my back that caused the calcification, he's response was "why do you think my phone is way over their" pointing to the table sitting in the corner of his office, then i started to look for conformation of my thoughts and sure enough there is plenty out there like this paper that corelates well with the introduction of the mobile phone in Australia. A week before my experience I had a CT scan and what it showed was calcium build-up at the junction to my legs and the only other bit of calcium build-up was behind my ear." JMorpus, on X https://t.co/ltLxzOZzxR https://t.co/8KkErfV3S6
quotesthe post below (author id 1621062850818220032)
@Anti5GWarrior @CorinneNokel The young have allot to look forward to in the future, Here is my story, 12 years ago I awoke in the middle of the night in excruciating pain in my legs, a piece of calcium had broken of from the main artery that supplies blood to my legs blocking at the junction I had to have

This post quote-tweets the one above. Its text and identity are anchored (one level, no deeper); any media it showed is anchored with this post's media. Quoted text may be truncated for a long-form original — the anchored hash covers exactly the text shown here.

posthttps://x.com/jmorpuss/status/2102302491551690803
author id1621062850818220032
posted2026-09-22T07:42:27.000Z
manifest sha256f0d76dcb540ad8ce3d13136de26e73429f3d2194d8c5abeadd90b2b37ca61b79
text sha256d12908423c19d9bbdf6ae9c5e8c99267e2af6926925b13c62737e0275626f5c2
quoted text sha25637ef241bf869f2e7eccd118328ab1c6fc202196f51fe3e4042c5edf241337ff2 (quoted post 2050684840241176809, author id 1621062850818220032)
on-chain⛓ anchored — f0a30c2c4e5602800a74b06bb3f0cb39898cdd1fda57eb5e733e04fe58defc6d

Verify it yourself: the manifest is the exact JSON whose SHA-256 is f0d76dcb540ad8ce3d13136de26e73429f3d2194d8c5abeadd90b2b37ca61b79; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match d12908423c19d9bbdf6ae9c5e8c99267e2af6926925b13c62737e0275626f5c2, plus the quoted post's id, author, and text hash 37ef241bf869f2e7eccd118328ab1c6fc202196f51fe3e4042c5edf241337ff2, and read the anchor transaction's OP_RETURN bsv.cx / x1 / f0d76dcb540ad8ce3d13136de26e73429f3d2194d8c5abeadd90b2b37ca61b79 — 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