The actors behind the Liquid Network security incident have returned 3,400 BTC to the federation while retaining approximately 598.5 BTC, according to a September 7, 2026 incident summary fro
The actors behind the Liquid Network security incident have returned 3,400 BTC to the federation while retaining approximately 598.5 BTC, according to a September 7, 2026 incident summary from Bitcoin.com News, leaving the network paused and the terms governing the retained balance unconfirmed even as broader Bitcoin markets traded quietly lower.
Bitcoin.com identifies the affected system as Liquid Network, the Blockstream-operated sidechain, and reports the incident began on September 6, 2026, per its incident summary by Jamie Redman. That distinction matters because a separate Japanese exchange also named Liquid was hacked for an estimated $97 million in August 2021, an unrelated event that naming the Liquid Network avoids conflating. For related coverage, see PolyNext Awards & Conference Dubai 2026: Advancing the Global Dialogue on Plastic Recycling and Circularity.
The core claim rests on a single fetched media report; the linked Bitcoin transaction and retained-balance address were not independently readable in the supplied research, so the figures below carry explicit attribution and remain conditional pending on-chain confirmation. For related coverage, see AINext Awards & Conference Dubai 2026: Where AI Leaders, Innovators and Decision-Makers Shape the Future of Artificial Intelligence.
Bitcoin.com reports the actors sent the returned Bitcoin back to the federation address after Blockstream said its bridge nodes had been patched, with the return following a fix rather than preceding one. The linked transaction candidate on Mempool.space returned only an application shell, meaning sender and receiver addresses, confirmation time and fees could not be verified in this run. For related coverage, see CFTC Seeks Dismissal of CME Suit Over Kalshi Bitcoin Perpetuals.
Liquid Network: reported BTC return
3,400 BTC
Bitcoin.com reported on September 7, 2026 that the actors returned 3,400 BTC to the Liquid federation. The linked transaction was not independently verified in the supplied research.The pattern echoes an earlier episode in which a Liquid-linked white hat pledged to return Bitcoin after a fix, though white-hat status here is self-described and contested, according to unconfirmed reports. No published agreement identifies the retained portion as an authorized bounty, so the funds should not be labeled a negotiated reward.
The retained balance is reported at exactly 598.49955894 BTC at the article's snapshot, supporting the approximately 598.5 BTC framing. Treating the two figures as one pool, their arithmetic sum is roughly 3,998.5 BTC.
Liquid Network: reported BTC retained
Approximately 598.5 BTC
Bitcoin.com reported a retained balance of 598.49955894 BTC at its September 7, 2026 article snapshot. This is not an independently verified current balance; no agreed bounty was established.On that same conditional basis, the returned share works out to roughly 85% and the retained share to roughly 15%. These are derived calculations, not a verified recovery rate, and the roughly 3,998.5 BTC total should not be equated with any confirmed original theft figure, which the supplied research does not establish.
Reported figureAmount (BTC)Derived share of poolReturned to federation3,400~85%Retained~598.5~15%Conditional total~3,998.5100%No dollar conversion is applied to these amounts because no timestamp-matched valuation was established; a media-reported approximate valuation exists but is not a transfer-time figure. Bitcoin traded at $79,155 as of September 7, 2026, down about 0.88% on the day, a current snapshot that carries no established causal link to this incident.
The supplied context offers no explanation for why roughly 598.5 BTC was retained and no terms governing those funds. The actors' self-described white-hat framing and any prospect of keeping the remainder as a reward are unconfirmed reports, not settled facts.
Bitcoin.com attributes criticism of the take-first-and-negotiate-later approach to Ledger CTO Charles Guillemet, who later acknowledged the actors could be inexperienced researchers, according to that report; his original statement was not independently fetched. The retained amount should not be characterized as a bounty, settlement, negotiated payment or permanent loss, and no further return is promised or expected in the supplied context.
The reported return, absent readable transaction hashes, wallet addresses or recipient confirmation, does not by itself establish reimbursement to affected users or full resolution of the incident. Bitcoin.com reports Liquid remained paused on September 7, with bridge nodes disabled and centralized-exchange L-BTC deposits and withdrawals halted, which is time-specific reporting rather than a verified current status.
A root-cause claim, that an Elements range-proof verification cache bug allowed creation of unbacked L-BTC rather than a compromise of federation signing keys, appears in the report as a technical reconstruction, according to unconfirmed reports, with no official postmortem independently fetched. These are limits of the supplied evidence, not proof that public documentation is unavailable, and they mirror the enforcement uncertainty seen when protocols weigh legal process against exploiters.
Broader market sentiment sat at 71 on the Crypto Fear & Greed Index, in Greed territory as of September 7, 2026, a market-wide reading that does not measure reaction to this specific incident.
The concrete triggers are an official Blockstream or Liquid Network postmortem confirming the exploit mechanism, a readable on-chain confirmation of the 3,400 BTC return and the retained-address balance, and the network's restart from its paused state. Until the linked transaction is independently verifiable, holders and builders should treat the return, the retained share and the root cause as reported-but-unconfirmed rather than closed.
The supplied headline and Bitcoin.com report 3,400 BTC returned to the Liquid federation.
Approximately 598.5 BTC, reported precisely as 598.49955894 BTC at the article's snapshot.
The supplied context does not explain why, and no agreement identifying the retained funds as a bounty was established.
No. User repayment is not established by the supplied context, which provides no information on reimbursement or operational recovery.
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.
The post Liquid Hackers Return 3,400 BTC, Retain About 598.5 BTC was initially published on Coincu.
