@DereckWDewon X · 2026-10-06
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-06 19:09 UTC.
Addendum: i'm not saying anyone in the aforementioned posts are said bad actors & cognitive dissonance machines. Specifically, @vamosvigilante serves as an excellent stalwart & provocateur to spur people into doing their own research. In lieu 😏 of that, 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 bfb5a424334b85903b8e47c6300ea881cecc99a087e721de3618e26bf52d290a; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match dd1b83f4a9932841bae0f53876f71bf4e06f2f7292f10af80cb976e13333b522, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / bfb5a424334b85903b8e47c6300ea881cecc99a087e721de3618e26bf52d290a — 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.
