@vamosvigilanteon X · 2026-10-06
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-06 23:55 UTC.
I've already taken the best and brightest along with me to eCash (ECX). The ones that are yet to move will do so now thanks to your post. After all, why would a talented dev build on the same network that keeps giving him the same illiquid results??? It is intelligent to hedge. The smartest in BSV already have.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is bbc420da58b1b5c21276d33da8490e7523443893a7ea2de04042c5ba82f4fa1c; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match b5268d5f5ce3c1f03ee6cf413f29b0da1667d7854cb4c648acf09e9eade8f052, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / bbc420da58b1b5c21276d33da8490e7523443893a7ea2de04042c5ba82f4fa1c — 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.