@DereckWDewon X · 2026-10-19
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-20 03:28 UTC.
Much against popular opinion, I think PAC, if he'll forgive the presumption, is holding back (restraint—in-line w Values over value) from the fact that USDC a Cuckbase & Fraudstrong grift. The only, only reason to mess with it is to swap it for real bitcoin. That's the only reason any of these things continue to stay propped up. When you have the real deal, you don't need to play these games of including captors because you know they had feelings too. They lost those rights when they held others captive, which is what happened to bitcoin, the real one, and it has not stopped. We should be cutting all of these people out like cancer because it's exactly what they are. Chancres hoping to spread their malignancy via the word of mouth that made real bitcoin what it is to begin with. It does not matter if I seem xenophobic or insular because this all sounds like more of this a few bad apple spoils the cliché nonsense, and I am fucking sick of it. I am glad that you are working. I am not degrading your efforts as related to real bitcoin, but this we all have to get along to go along stuff ab so fucking lewdly not. That violates 100% the precepts of why the technology exists. All the compromises are why we need real bitcoin. Which is just digital cash, so it's important not to mistake a hand for a vagina if you're trying to reproduce. All I'm saying.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is c5c90206b7b1be875f71b8ce43c6276c687aafd245bdbb5c03af7a2b3f2644de; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 812d5be027f9bc63f2db141624b668a02152094e1044c04d984516391537dbb4, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / c5c90206b7b1be875f71b8ce43c6276c687aafd245bdbb5c03af7a2b3f2644de — 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.