According to unconfirmed reports, Blockstream rejected a $50 million bounty demand tied to the Liquid Network. The figure is described as a payment requested by an attacker, not a loss booked by the company or a reward that was paid out.
Blockstream has reportedly refused a Liquid hacker’s $50 million bounty demand, a claim that circulated in the wake of a security incident on the Bitcoin sidechain but that no verified source has confirmed. The reported dispute centers on the Liquid Network, a Bitcoin layer-two federation operated by Blockstream, and it arrives without a public statement establishing the demand, its terms, or the company’s response.
WHAT TO KNOW
- A Liquid hacker is reported to have made a $50 million bounty demand, according to unconfirmed reports.
- Blockstream is reported to have rejected that demand; no official statement corroborates the rejection.
Blockstream rejects the $50 million bounty demand
According to unconfirmed reports, Blockstream rejected a $50 million bounty demand tied to the Liquid Network. The figure is described as a payment requested by an attacker, not a loss booked by the company or a reward that was paid out. For related coverage, see Liquid Network Halt: Reported $320 Million Bitcoin Hack.
No official statement, quotation, or dated announcement supporting the rejection was located in the available evidence. The single source carrying the claim is a headline tip that was not independently corroborated, so the decision, its timing, and any counter-offer remain unestablished. For related coverage, see Blockstream Says Bridge Nodes Patched in Message to Hacker.
What Blockstream has published directly concerns user safety rather than any negotiation. On September 9, 2026, the company issued an official phishing warning referencing the recent Liquid Network incident, telling users the event does not require them to move funds, enter a recovery phrase, check reimbursement, re-peg assets, or install software sent by email.
That same alert flagged supposed white-hat, bounty, or on-chain contacts asking users to coordinate outside official channels as one of the impersonation lures, a caution that overlaps directly with the reported bounty framing. This context around the incident aligns with prior reporting that Blockstream rejected a ransom after the alleged Liquid hack.
What is known about the Liquid hacker’s demand
The supplied claim describes the claimant as a Liquid hacker seeking a bounty. A requested bounty is not the same as an accepted or paid reward, and nothing in the available material shows that any payment was authorized, negotiated, or completed.
The headline establishes little beyond the allegation itself. There is no verified claimant identity, no vulnerability description, no disclosure history, and no stated bounty terms or deadline in the evidence reviewed.
Independent reporting does document an underlying incident, without confirming the bounty story. Protos reported on September 7, 2026 that roughly 4,000 BTC worth about $320 million at the time left the Liquid Federation wallet, adding that all 83 inputs to the drain transaction used 11 valid signatures on the federation’s 11-of-15 signing branch. Those figures are attributed historical reporting, not independently rechecked totals, and coverage of the reported Liquid Network halt and $320 million figure has tracked the same source data.
Protos also attributed to SideSwap the position that faulty L-BTC came from a third-party Elements bug and that SideSwap’s own systems were not responsible; the root cause was not independently established. Separately, an earlier report placed the ransom figure at $47 million, underscoring how unsettled the demand amount remains.
What remains unverified about the Liquid incident
Blockstream’s reasoning for any rejection is not established in the available material, and no source sets out the terms the company is said to have turned down. Whether a valid vulnerability was demonstrated, and its technical validity, would require supporting evidence that has not surfaced.
Bitcoin developer Jameson Lopp publicly criticized apparent inactivity in the Liquid functionary codebase on September 6, 2026. His comment reflects one named opinion on maintenance, not an independently audited finding, and reports linking the incident to AI remain speculation.
I seriously doubt it's a coincidence that the Liquid bridge got drained just a couple days after Astra dropped.
Looks like the Liquid functionary codebase hasn't been touched in 2 years, which isn't a good sign.https://t.co/skDn0tHQIg
— Jameson Lopp (@lopp) September 6, 2026
Source: @lopp on X
Neither user losses nor an absence of security risk can be established from the headline alone. Reporting on whether the Liquid Network attacker returned 3,400 BTC speaks to recovery efforts but does not confirm the bounty negotiation at the center of this story.
For market context only, and unrelated to the unverified demand, Bitcoin traded at $77,258 at the time of research capture, with the broad crypto Fear & Greed reading at 63, classified as Greed. These are current snapshots, not incident-time figures.
Bitcoin price at research capture
$77,258 USD
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
