@bielokamotoon X · 2026-09-11
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-11 05:21 UTC.
@Dr_CSWright @Dr_CSWright @Bielokamotobr This is the answer now I don’t know what to do with the weight of the informationn I found the answer. I’m very happy to listen to the Bitcoin white paper. Using the methods of The IT Regulatory and Standards Compliance Handbook https://t.co/7YAg0Z52ha
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is b2e69ce6fad18c56837f9b5519da6b109868b436a3735a3239ef8f6a64457bd8; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match a5541c783566b2097ef305b9b4d2180a58a5af43cc821d7d08f31755160d900c, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / b2e69ce6fad18c56837f9b5519da6b109868b436a3735a3239ef8f6a64457bd8 — 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.
