Liquid Network is operating normally again for block production and on-chain transfers, but roughly 600 BTC remains unrecovered from its September exploit and the network’s normal route for redeeming L-BTC back into bitcoin is still suspended.
In its latest recovery update, timestamped Sept. 17 at 21:05 UTC, Liquid said 3,400 BTC of the roughly 4,000 BTC withdrawn during the Sept. 6 security incident had been returned to the federation reserve. Approximately 600 BTC remains outstanding.
The network said it is not yet able to provide a firm date for restoring peg-outs. Redemptions will restart only after full one-to-one BTC backing for L-BTC has been confirmed and the required software updates, testing and independent security reviews have been completed.
That leaves Liquid in an unusual intermediate state. The blockchain itself is running, users can transfer L-BTC and other Liquid assets, markets and several ecosystem services have reopened, and new bitcoin can again enter Liquid through peg-ins. But holders still cannot use the federation’s standard peg-out mechanism to redeem L-BTC for BTC on Bitcoin.
The situation follows the nearly 4,000 BTC drain from Liquid’s federation reserve on Sept. 6. A vulnerability in the Elements software underlying Liquid allowed approximately 4,000 L-BTC to be created without corresponding bitcoin backing.
The newly created L-BTC was sent through SideSwap’s peg-out service. Liquid’s functionaries accepted the tokens as valid and authorized the redemption, releasing approximately 4,000 real BTC from the federation reserve. Liquid and SideSwap have said federation private keys were not compromised; the failure occurred because invalid L-BTC was accepted before the authorized peg-out process began.
Blockstream patched Liquid’s bridge nodes on Sept. 7, and the party responsible returned 3,400 BTC later that day. Liquid subsequently released Elements v23.3.4 to address the proof-verification cache vulnerability. Block production resumed on Sept. 10, followed later that day by normal network transactions.
The remaining reserve deficit has not yet been eliminated.
SideSwap provided unusually explicit figures when it reopened peg-ins on Sept. 11. At that point, it said 4,229 L-BTC was in circulation while the federation reserve contained 3,627 BTC, leaving a difference of about 602 BTC.
SideSwap also directly warned customers that L-BTC could not then be redeemed for bitcoin through the federation and said users who did not immediately need L-BTC might prefer to wait until the peg was restored.
Despite that warning, SideSwap reopened its peg-in service because the incoming process is structurally different from the operation that failed during the exploit. A peg-in sends bitcoin into the federation and results in L-BTC being credited on Liquid. No bitcoin leaves the reserve, and the peg-out authorization key involved in the Sept. 6 incident is not used.
SideSwap said the Liquid Network had already been processing peg-ins since transactions resumed on Sept. 10. Its own service began accepting them again the following day, charging its standard 0.1% fee.
The latest Liquid update suggests the broader ecosystem is continuing to reopen around the still-disabled redemption mechanism. AQUA has restored Liquid asset transfers and peg-ins, while its Indra feature can provide swaps between L-BTC and Lightning BTC subject to available liquidity. BTSE has re-enabled USDT-Liquid transfers, while other wallet and swap providers have restored portions of their services.
That distinction matters. Peg-outs being disabled does not mean L-BTC is completely trapped. Holders may still trade or use alternative liquidity routes where they are available. What remains unavailable is the core federation redemption mechanism that normally destroys L-BTC and releases an equivalent amount of BTC from the reserve.
Liquid’s problem also increasingly resembles other recent incidents involving synthetic bitcoin whose circulating claims exceeded the genuine collateral behind them. The Nomic exploit left allBTC under-backed after counterfeit nBTC entered Osmosis, while the Symbiosis Bitcoin bridge exploit created billions of unauthorized syBTC before the attacker converted part of the synthetic supply into genuine liquidity.
In all three cases, the underlying Bitcoin network was not compromised. The failure occurred in infrastructure responsible for deciding whether a representation of bitcoin was legitimately backed.
New Bitcoin Can Enter Liquid Before Old Bitcoin Can Leave
The technical argument for allowing peg-ins before peg-outs is fairly easy to understand.
A peg-in adds bitcoin to the system. A peg-out removes it. After an exploit that drained the reserve through an outgoing redemption path, reopening the direction that increases reserves while keeping the vulnerable exit path closed can make sense from a security perspective.
Economically, though, the picture is more complicated.
A customer pegging in today starts with ordinary BTC and ends with L-BTC that joins the same fungible asset already circulating on Liquid. There is no separate class of “post-exploit L-BTC” with its own reserve pool. SideSwap itself tells customers that the L-BTC received through a new peg-in is the same asset trading across its markets.
The public disclosures reviewed so far also do not describe a mechanism that legally or economically ring-fences newly deposited BTC from the pre-existing reserve shortfall.
That is the part worth watching.
A new peg-in does not automatically repair the old deficit. In the normal economic model, one BTC entering ultimately supports one additional L-BTC claim. Assets and liabilities rise together. The approximately 600 BTC hole only disappears if the unrecovered bitcoin comes back or additional BTC is contributed without an equivalent new L-BTC liability being created.
In other words, accepting fresh BTC can strengthen the gross size of the reserve without necessarily closing the gap between reserves and outstanding claims.
This is why reserve accounting matters as much as the software patch. Similar problems are becoming a recurring concern across cross-chain liquidity infrastructure: the technical bridge can function while the harder question is whether every token circulating downstream still has the asset behind it that users think it does.
Liquid does have one important advantage compared with some bridge failures: the deficit is visible, most of the bitcoin has already been recovered, and Blockstream has publicly indicated that the L-BTC peg will ultimately be covered one to one. What has not yet been disclosed is precisely how the remaining roughly 600 BTC will be restored if the outstanding coins are never returned.
That missing detail is now more important than whether blocks are being produced normally.
The reopening sequence also shows why investors need to distinguish between a functioning blockchain and a fully functioning financial product. Crypto platforms regularly restore individual services in stages, and recent network-specific funding disruptions have shown how deposits, withdrawals and trading can have very different operational states at the same time.
Liquid is an extreme version of that problem. Transfers work. Markets work. New BTC can enter. The core BTC redemption route does not.
The next meaningful update therefore needs more than another statement that the network is stable. Investors and integrations need a reconciled reserve figure, a clear explanation of how the remaining deficit will be covered, evidence that the revised peg-out controls have survived independent review and a concrete plan for testing redemptions before they return at scale.
Until then, Liquid has recovered most of the bitcoin and most of the network’s functionality, but not the one property that matters most to a bitcoin-backed asset: unquestioned one-to-one redemption.
Shane Neagle is a financial markets analyst and digital assets journalist specializing in cryptocurrencies, memecoins, prediction markets, and blockchain-based financial systems. His work focuses on market structure, incentive design, liquidity dynamics, and how speculative behavior emerges across decentralized platforms.
He closely covers emerging crypto narratives, including memecoin ecosystems, on-chain activity, and the role of prediction markets in pricing political, economic, and technological outcomes. His analysis examines how capital flows, trader psychology, and platform design interact to create rapid market cycles across Web3 environments.
Alongside digital assets, Shane follows broader fintech and online trading developments, particularly where traditional financial infrastructure intersects with blockchain technology. His research-driven approach emphasizes understanding why markets behave the way they do, rather than short-term price movements, helping readers navigate fast-evolving crypto and speculative markets with clearer context.