🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-13 19:29 UTC.

@m_murfyon X · 2026-09-13
i ask myself if the reason i bought bsv in 2019 still holds the price is lower than it was then, but the protocol has scaled to millions of transactions per second bitcoin is now set in stone forever, and fully unbounded and it is still being treated like a footnote in the “crypto space” that’s the asymmetric information advantage people who understand bitcoin have against the market the reason still holds
posthttps://x.com/m_murfy/status/2099152148458254447
author id179461935
posted2026-09-13T15:04:07.000Z
manifest sha256014b20de62f367947c94abe331ef3ccfd6d979c1bda2bb222fc00bb29b2be8ef
text sha256c78a2a0762345b36a704602a4865a2bc69933e392e564976d89093615b0598a9
on-chain⛓ anchored — ce40681c718b5e06a1e99a5d63007292f04b71f88d72643b137657ed436b452c

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