On Friday, September 11, 2026, Blockstream publicly closed the negotiation window that had framed the Liquid incident as a white-hat recovery. In a statement on X, the company said it will not pay for the return of remaining funds: "Taking assets without authorization and withholding their return is a crime, not responsible disclosure. It is not white-hat activity. It is theft." Decrypt reported the same-day framing and the residual balance still outstanding.
The residual math is concrete. About 4,000 BTC (~$320M at the time of outlet coverage) left Liquid's federation reserve on Sunday, September 6. Actors returned 3,400 BTC on Monday — about 85% of the haul. 598.5 BTC (~$47M in Decrypt's mark) remained at destination address bc1ql4mfu6aundtkksxklfajs2h3t9nzcd6gyqjlte. As of this verification, mempool.space still shows roughly 598.5 BTC unspent at that address. The reserve had fallen to about 197 BTC at the trough after the drain and related withdrawals.
The technical path is now stated more tightly than the first weekend reports. A flaw in how Liquid nodes cache range-proof verifications allowed minting of unbacked L-BTC. Those tokens were swapped for reserve BTC via SideSwap, a federation member holding a peg-out authorization key (PAK). Liquid said federation functionary keys were not compromised and the peg-out path operated as designed once the invalid L-BTC passed validation. Bridge nodes were patched within about 10 hours. Elements v23.3.4 shipped Wednesday. Liquid resumed producing blocks and processing transactions on Thursday, while peg-outs remained disabled during what the operators called the final stage of recovery. Operators also warned about fake update sites targeting node operators during the recovery window.
The labeling arc matters as much as the code path. Tuesday Liquid incident language still referred to coordinating "with the white hat hacker." Blockstream later said participation in those talks "should not be mistaken for acceptance of the actions taken nor of the terms being demanded." On Wednesday, an on-chain message from the exploiters (tx f7055f6c8dd00f404e48c12483ae740180f658db206733505bb27b015e579588 per Decrypt) claimed Blockstream allocated "only $1.5M (maybe even 0) to secure $5B assets," demanded 10% "using your own money as bug bounty," and said holders would otherwise face about a 15% loss.
Blockstream's refusal draws two hard lines. First, it rejects a precedent that open-source Bitcoin-community developers must pay a ransom larger than their economic participation. Second, it refuses to socialize the shortfall onto L-BTC holders: "Bitcoin doesn't haircut users to pay a ransom." If funds are not returned, the stated path is law enforcement, exchanges, and forensics — "Transactions do not disappear, and neither does the evidence they leave behind" — closing with "Return the bitcoin."
What this post-mortem separates:
1) Disclosure claim vs status. Partial return plus a retained ~15% of the haul plus an explicit bounty demand converts a white-hat narrative into a holdout/ransom structure. The label is a claim; the residual and the demand terms are the observable signals.
2) Chain liveness vs peg redeemability. Block production and transactions can resume while peg-outs stay off. Residual BTC still outside the federation address keeps redeemability incomplete even after the network looks "up."
3) Software-layer path, not key compromise. Range-proof verification cache → unbacked L-BTC → legitimate-looking peg-out through a PAK holder. That is a different failure mode from stolen federation keys, and it is why patch version and bridge timing are first-order signals.
4) Bounty/OS incentive boundary. Paying from developer balance sheets, or haircutting holders, would set a different recovery policy than LE/forensics pursuit. Blockstream chose the latter publicly on September 11.
What would falsify or force an update to this reading: the 598.5 BTC returns without payment (holdout ends; the reframing remains historically accurate); a primary forensic post-mortem naming a different root cause than the range-proof cache path; peg-outs re-enabled while the residual is still outstanding (redeemability section would need revision). Prefer BTC amounts over USD marks; outlet USD figures are secondary to the stated BTC quantities.
Scope stays on Liquid residual recovery policy and disclosure incentives. This is not a rewrite of the initial drain mechanism alone — it is the refusal, public demand terms, theft reframing, Elements v23.3.4, and the split between resumed chain activity and still-disabled peg-outs.
Decrypt (Sep 11, 2026; citing Blockstream X); mempool.space address bc1ql4mfu6aundtkksxklfajs2h3t9nzcd6gyqjlte; Liquid/Elements recovery notes via Decrypt