@DereckWDewon X · 2026-10-06
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-06 18:59 UTC.
Addendum: i'm not saying anyone in the aforementioned posts are said bad actors & cognitive dissonance machines. Specifically, @vamosvigilante serves as an excellent stall and provocateur to spur people into doing their own research, so I'm sure as hell not calling him one of them. He's one of the most staunch real BitCoin supporters I've encountered since first having entered ~ eight years ago (& he still remains undefeated). I'm also not insensitive to appearances & too quickly drawing conclusions of others intentions. I'm in strange case, and many have questioned my motives, which are welcome. It's important to remember that passive comments on the social media equate neither to actual dialog nor direct communication, & sometimes the fractus between intention & interpretation—chasmic
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 1aaf075a4221fc40346f73b013358f5482b297b6ea1344cb4605b9337bb58d9e; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 05069b7fd0be1385405cea5935a3a2fbb54a8f9b74025a71e8ec581379cdcbdf, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 1aaf075a4221fc40346f73b013358f5482b297b6ea1344cb4605b9337bb58d9e — 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.