@PacArtCollecton X · 2026-09-21
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-21 18:55 UTC.
@Jus7Degen Here is a 15 minute summary of what occurred. BitcoinABC (BCHABC) wanted to enforce CTOR & add new op-codes keeping the block size limit at 32MB. BitcoinSV (BCHSV) wanted to increase the block size limit to 128MB & re-enable existing Satoshi op-codes. https://t.co/TjukTuW0Q7
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 99686b833d7ae0851b1acecf5039428fa91bc1a4f65d1fe8983d3a148b82f1fe; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match b567c8c7cdc5269c54b5459661d787e13e751f034dafe42a9088aea7e748ef93, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 99686b833d7ae0851b1acecf5039428fa91bc1a4f65d1fe8983d3a148b82f1fe — 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.
