🐦 Archived X post

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

@skgremonton X · 2026-09-18
This article comes from someone who has spent years pursuing onchain scalability and extraordinarily high transaction throughput. The engineering question Craig Wright raises is worth considering 👍 I Am Sick to Death of Hearing That Blockchain Cannot Scale https://t.co/uc0Fvj2kbF #BSV
posthttps://x.com/skgremont/status/2100935395286585674
author id977346379822460928
posted2026-09-18T13:10:06.000Z
manifest sha2566bef9afec0727adc0b6bebeb81374951d64fa4103e36526e8e8b6a62b9203472
text sha256ecab2bdf294da3f801040100e8a5550fc281deb11556d896a216e7ccdbbf2096
on-chain⛓ anchored — e05e0613e8167a4abf500a9d094a77ee909e23a205fd5c0128efe9473a9336fc

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