Liquid Recovers 3,400 BTC After $320 Million Network Incident
• September 8, 2026 11:46 am • CommentsLiquid has recovered most of the bitcoin removed in a security incident that briefly put roughly $320 million at risk, but the episode is not something the network can simply file away as a happy ending.
The incident began when a purported white-hat actor withdrew about 4,000 BTC from a Liquid Federation wallet. According to CryptoSlate, 3,400 BTC was later returned.
The person behind the transaction kept 600 BTC, worth about $47 million at the price used in the report.
Getting 85% of the bitcoin back is a major recovery. It does not erase the fact that one transaction moved an enormous amount of value through a system designed around distributed custody and controlled peg-outs.
The report says the returned bitcoin arrived after Blockstream and federation members contacted the actor with signed on-chain messages. The remaining 600 BTC turns the episode from a clean recovery into an unresolved custody and authorization failure.
We are aware of a security incident on @Liquid_BTC. Purported white-hat hackers have withdrawn ~4,000 BTC (~$320 million) from the Liquid Federation wallet. The @Blockstream team is working on contacting them on-chain with a signed message.
What we know so far is that the funds…
— Liquid Network 🌊 (@Liquid_BTC) September 6, 2026
What happened at the peg-out
Liquid is a Bitcoin sidechain operated through a federation. Users can move bitcoin into the network as L-BTC, use it for faster and more private settlement, and later peg out to receive BTC on the Bitcoin base layer.
The federation’s job is to authorize those movements and protect the underlying reserve.
SideSwap’s statement says a customer sent 4,000 L-BTC to its peg-out service at 14:05 UTC on September 6. SideSwap said its service processed the order normally: the L-BTC was burned with valid peg-out authorization, and the Liquid Federation paid the corresponding BTC about 23 minutes later.
That description narrows the question. A transaction carrying valid authorization moved through the peg-out machinery and resulted in a real Bitcoin payment.
Statement on today's Liquid incident
Today at 14:05 UTC a customer sent 4,000 L-BTC to the SideSwap peg-out service. Our service processed it like any other order: the L-BTC was burned on Liquid with a valid peg-out authorisation, and at 14:28 UTC the Liquid Federation paid…
— SideSwap (@side_swap) September 6, 2026
Recovery is only the first part of the answer
Liquid said the funds did not appear to have been sold or mixed during the initial response, giving Blockstream and federation members time to communicate with the actor through signed on-chain messages. That contact appears to have produced the 3,400 BTC return.
The unresolved 600 BTC is difficult to describe as a conventional bounty. A legitimate security reward is negotiated within a disclosure process; it is not normally set unilaterally by keeping tens of millions of dollars after demonstrating control over funds.
For Liquid users, the next meaningful update is not another percentage recovered. It is a technical explanation of how valid authorization was obtained, which controls failed to stop a peg-out of that size, and what has changed so the same path cannot be reused.
Those answers matter beyond Liquid. Federated sidechains trade some of Bitcoin’s base-layer model for speed, privacy and specialized functionality.
Their security depends on operational controls, signer behavior and emergency response working together. A failure in any one layer can become a reserve-level event.
The recovery shows that transparent on-chain communication and coordinated incident response can work under pressure. The incident itself shows why recovery cannot be the only measure of success.
Liquid protected most of the money after it moved. Its next task is proving that the system can prevent a repeat.
Join the conversation!
We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.
