Here is the hard truth up front: the recovery cannot be confirmed. No official incident statement, no postmortem, and no on-chain transaction has been located to corroborate the figures. The claim rests on a single report that could not be independently read at the time of writing. For related coverage, see Malone Lam Faces Plea Hearing Over $245M Bitcoin Theft.
The reported 3,400 Bitcoin recovery
According to unconfirmed reports, 3,400 Bitcoin were returned to Liquid Network by actors characterized as white-hat hackers. That characterization is an attribution, not an endorsement, and no disclosure, authorization, or bounty arrangement has been verified.
No transaction hash, wallet address, transfer timestamp, or dated statement was obtained to support the amount. Treat the identity of the affected operator and the nature of the return as open questions until primary evidence surfaces.
Liquid, a Bitcoin sidechain, has been at the center of large BTC movements before. The network previously saw hackers return $270 million in Bitcoin after a reported theft, and separately drew scrutiny when it was reportedly halted following an alleged BTC withdrawal. Those are distinct, earlier episodes, not confirmation of the current claim.
Talks continue over the remaining $47M
The same unconfirmed reports say negotiations are ongoing over a remaining $47 million. No participants, deadlines, demands, or asset breakdown have been disclosed, and no outcome is confirmed.
Keep the dollar figure separate from the Bitcoin figure. There is no verified valuation timestamp, so the $47 million cannot be converted into a reliable BTC equivalent, and no combined “total loss” can be responsibly calculated from the available information.
What Liquid’s design actually confirms
What can be verified is how Liquid’s custody machinery works. The network’s Watchmen software manages the multisignature wallet holding pegged bitcoin, delivers peg-outs, and sweeps controlled UTXOs before they expire, according to Liquid’s functionary-code announcement. That announcement also confirms Liquid’s functionary source code was released publicly for independent audit, and that its Dynamic Federations feature allows functionaries to be added or removed without a fork.
History shows that custody and block production are separate concerns. A Dynamic Federations activation once caused a roughly 22-hour Liquid outage in October 2021 while Watchmen kept sweeping funds, per Andrew Poelstra’s account. That is background, not evidence of the current incident.
What remains unconfirmed
Recovering funds is not the same as restoring them. Nothing in the available material establishes custody of the returned Bitcoin, whether users have regained access, or whether any reimbursement is planned.
The reporting still needs the basics: an attributable, dated confirmation of the return, the block-explorer trail behind the 3,400 Bitcoin, and the status of the talks over the outstanding amount. Liquid has previously disclosed large flows in detail, such as when it released 3,996 BTC after an L-BTC burn and when nearly 4,000 BTC left through a valid peg-out, which sets the bar for what a credible confirmation here would look like.
Until that evidence exists, one question hangs over the story: is this a genuine recovery in progress, or a headline still waiting for its proof?
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.
