@Vince50818862on X · 2026-09-14
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-15 05:27 UTC.
FCA & Bank of England: "We cannot accept solutions where customers have no recourse when assets are lost or stolen." That statement alone rules out every "code is law" blockchain. BSV's NAR was built exactly for this. The regulators drew the line. Only BSV was ready for it. https://t.co/A1amBsOx1q https://t.co/H2l6ef4HHb
The Bank of Japan on their CBDC pilot report: "We need 500K+ TPS" "We're studying the UTXO model" "We can't truly solve single-account bottlenecks" BSV handles all natively: • 1 Million+ TPS • UTXO parallelism • Base layer settlement The research is pointing somewhere. https://t.co/wIbj26xiGY https://t.co/U0TIkyKFnx
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 77fafee0b75c929ef23f2d30afc257e0a715db3a76e0a869b8a6777cca6539a2; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 5b8c065a682b845c1fa8165d956b3f7eb2324c9511ed9068e9076a293548f8c7, plus the quoted post's id, author, and text hash e02a86d4b29301c9e5b44cbd623ca77766b8c8de35f50c3317129f6ffead4a34, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 77fafee0b75c929ef23f2d30afc257e0a715db3a76e0a869b8a6777cca6539a2 — 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.
