@BitcoinSVCOLon X · 2026-09-12
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-12 20:13 UTC.
More OP_RETURN history: The decision to increase the OP_RETURN data limit to 100KB implemented as a local policy in the Bitcoin Core (BTC) v30.0 update. This adjustment sparked significant debate across the community, as it effectively relaxed the previous 83-byte restriction, allowing larger arbitrary data blobs to be transmitted as standard transactions in the mempool without altering the network's underlying consensus rules. The primary argument driving this change was the urgent need to avoid the abuse of other OP codes for data storage. Before this update, users circumvented strict limits by disguising heavy files within witness data fields via Taproot, which polluted the active UTXO set. By providing a dedicated 100KB space within OP_RETURN, developers aimed to channel this inevitable data insertion into a provably unspendable area that nodes can easily prune, thereby protecting the network's efficiency and preventing the misuse of critical transaction structures. What few people realize is that OP_RETURN messages are contained in 0-satoshi outputs and can be easily pruned by miners, which will inevitably cause BTC-based Ordinals (Bitcoin NFTs) to disappear. In contrast, BSV-based @1SatOrdinals are embedded using OP_PUSHDATA, which is much harder to prune, ensuring their long-term persistence. https://t.co/FdHWosICok
https://t.co/1be55dcMLQ
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.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is fcfd134523f1ace4ff41928264a0f0c982e54b9e970dacba0eb2551de5955a11; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 02f33bca98c47ffe564c7ca88433d0e6465f6cc35f94fd008dbfb445cf6d506e, plus the quoted post's id, author, and text hash 043caaec68e772bfc8e26b5067d79d2d98089edfa4f4b4030e9c09d9461d6b46, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / fcfd134523f1ace4ff41928264a0f0c982e54b9e970dacba0eb2551de5955a11 — 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.