@Satoshi_N_on X · 2026-09-07
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-10 01:21 UTC.
Blockstream reportedly was aware of the Liquid bug 5 days ago, and before patching it someone disclosed the vulnerability. @DropReceipts 🤔 https://t.co/bW3oU7ofmf
Well, they found the bug that drained the Liquid Federation. It's not good. From what we can tell, Blockstream recently found a vulnerability from 2019. I am going to leave individual names out, because this is ultimately Blockstream's responsibility. They were actively https://t.co/VmXyhrNdRS
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 6781e2084ab91249e5c44e2f1d4ab8b08b93c08e053ff7f13c7ccb8f3867467c; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 4e85aa1a575f2a705a24ed1f821088a503e3ec4240734aba0a4ebbeec3a9ef98, plus the quoted post's id, author, and text hash da3e802ae137873e3f93b137b31efc72ad9e451d413059abd0e027da1cc1c14b, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 6781e2084ab91249e5c44e2f1d4ab8b08b93c08e053ff7f13c7ccb8f3867467c — 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.