🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-10 02:29 UTC.

@collinctoon X · 2026-10-10

So, we're getting lots of feedback requesting BRC-100 wallet integration, @ProjectBabbage @HandCash @BWallet_Bot, and we're sold on the identity key working inter-operably across the eco-system; bringing your username with you. We love that. Is anyone using this?

posthttps://x.com/collincto/status/2108713624047169566

author id2075654931722227712

posted2026-10-10T00:18:00.000Z

manifest sha256a4770a6cd2b3faf6a5b4796960a1591278e1ed9716f013a6dd1d1b412b8eb256

text sha256aeb3b8bce531c45b268fb79d3302a9793b103879b021ace0679156e92237cad4

on-chain⛓ anchored — 2eaae2f381aef04b3b07609ffa3b7f2f5e8fe1f68a79eff4834c9f7db05b4b11

Verify it yourself: the manifest is the exact JSON whose SHA-256 is a4770a6cd2b3faf6a5b4796960a1591278e1ed9716f013a6dd1d1b412b8eb256; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match aeb3b8bce531c45b268fb79d3302a9793b103879b021ace0679156e92237cad4, and read the anchor transaction's OP_RETURN bsv.cx / x1 / a4770a6cd2b3faf6a5b4796960a1591278e1ed9716f013a6dd1d1b412b8eb256 — 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.

← bsv.cx · JSON · ⚠ Report