@AdamSimeckaon X · 2026-09-07
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-07 02:56 UTC.
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 patching the vulnerability 5 days ago (September 1st). The problem is, they did it in phases and disclosed it to the public without waiting for it to be patched before telling everyone exactly where the vulnerability was. This was either a massive, negligent blunder, or it was an intentional scapegoat. I don't have any evidence either way. I am just pointing out that both are plausible from a technical level. In simple terms, they found a back door to the treasure. Instead of closing the door right away, or waiting to tell everyone until the door was closed, they posted the treasure map for the whole world to see while the back door was left wide open. Thanks for bringing this to my attention, @btc_remnant https://t.co/dHQ8KIyT8V
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 5eacc08c02030259e4aff06526250b7fea326fd9376e67c889a9bb9236842636; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 4e2a52aa03e08d85794aa1bd45326b7e5352a807dc2a6a4dcd8beae1b43471ae, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 5eacc08c02030259e4aff06526250b7fea326fd9376e67c889a9bb9236842636 — 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.