@c3ntrxon X · 2026-10-01
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-01 03:19 UTC.
Playing around with this and working on listings ... https://t.co/d0g2Lfrz3u https://t.co/VTSaHWC8Tv
TRU own take on inscriptions with TRUScripts TRU-native on-chain inscriptions, similar in spirit to Ordinals but built for the TRU ecosystem. TRU is already a genuinely programmable PoW/UTXO blockchain, far beyond a basic Bitcoin clone. We’re building toward much greater scale
This post quote-tweets the one above. Its text and identity are anchored (one level, no deeper); any media it showed is anchored with this post's media. Quoted text may be truncated for a long-form original — the anchored hash covers exactly the text shown here.
Linked media above is notarized by reference — bsv.cx captured the link's title and preview image at archive time; it does not host the linked video or page.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 5eae66416815ef1cb74799a288bb5a95732830d0088798ec190e51c24d3bda43; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 8967dd540f84e16e946ed4f905e9316f72efe688fab11e276cb7a4bac91bd267, plus the quoted post's id, author, and text hash 6aa760597d1f57e7141a0b4e85aa01338fb3a025f8d07daa259a4d1f171080ac, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 5eae66416815ef1cb74799a288bb5a95732830d0088798ec190e51c24d3bda43 — 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.
