Mentioned in This Article
1. Why are Liquid Network redemptions still halted?
Liquid Network redemptions remain suspended as of October 11, 2026, more than a month after an exploit drained close to 4,000 bitcoin (BTC) from the sidechain's reserve. Users can no longer convert Liquid Bitcoin (L-BTC) back into ordinary bitcoin, a step known as a peg-out, and reserve coverage is estimated at about 86 percent of the tokens in circulation.
The shortfall is roughly 603 BTC, the portion of the stolen funds that has not been returned. Operators say redemptions will stay paused until the reserve fully backs every L-BTC token and security reviews are complete, so holders face an open-ended wait with no reopening date announced.
Other parts of the network have resumed. The freeze applies to the specific route that turns L-BTC into bitcoin on the main chain, which is the function that gives the token its value as a one-to-one claim.
2. What happened on September 6?
The incident began on September 6, 2026. A bug in Elements, the open-source software that underpins Liquid, allowed an unknown party to create and redeem L-BTC without authorization. In effect, tokens were produced without the matching bitcoin having been deposited, and those tokens were then redeemed against the real reserve.
About 3,996 BTC left the reserve held by the Liquid federation, a value of roughly $320 million at the time. The sum was drawn from infrastructure that exchanges and other businesses use to move bitcoin quickly.
A key detail is what did not fail. The signing keys of the federation members were not compromised, and the peg-out authorization key used by SideSwap, a service that handles Liquid redemptions, was also not compromised. The flaw sat in the software's handling of token creation, so the attacker did not need to steal keys to take funds.
3. How much bitcoin has come back, and how large is the gap?
Part of the money returned quickly. By September 7, roughly a day after the drain, white-hat actors had sent back about 3,400 BTC. That recovery reduced the loss from nearly the entire amount to a much smaller remainder.
Between 598 and 603 BTC has still not been returned, depending on the count. The difference between those figures reflects how reports tally the unreturned amount, and the estimate of about 86 percent backing derives from comparing the identified reserve with the L-BTC still outstanding. It is an estimate and not a full reconciliation of the reserve against all liabilities.
Even a recovery of roughly 85 percent leaves a gap that matters. A token promised as redeemable one-to-one for bitcoin is only as sound as the reserve behind it, and a reserve that is 14 percent short cannot meet every possible claim at once.
4. What is a federated sidechain like Liquid?
Liquid is a Bitcoin sidechain managed by Blockstream. It is a separate blockchain that runs alongside Bitcoin, built for faster settlement and for features such as confidential transactions. Users who want to move onto it send bitcoin to a reserve controlled by a group of organizations called the federation, and they receive L-BTC in return.
The reserve is protected by a multisignature arrangement, which means a set quorum of federation members must jointly approve any movement of funds. In principle this removes a single point of failure, since no one member can move the money alone.
The system works as a two-way peg. Bitcoin goes in and L-BTC comes out, and the reverse should work equally well. The design therefore rests on two things: the integrity of the multisignature reserve and the reliability of the software that decides when tokens may be created and redeemed. In September, the second of these failed.
5. Which parts of the network are working?
Liquid is operating again after the incident. Block production and user transactions have restarted, and people can send and receive L-BTC. What is missing is the return path to Bitcoin, which is the feature that anchors the token's price.
That distinction has practical consequences. A holder can still pay another user in L-BTC or trade it on markets that support it, but cannot take it to the Bitcoin network and claim the underlying coin through the official process. The token's market value then depends on confidence that the peg will eventually be restored.
For businesses that use Liquid for settlement, the pause is a practical inconvenience as well as a financial one. Exchanges and traders who relied on moving bitcoin onto and off the sidechain must now plan around a bridge that is closed in one direction, and they may keep balances elsewhere until the peg-out function returns.
This is why a token that cannot be redeemed behaves differently from one that can, even when its issuer promises to pay holders back in full. Without a working exit, the price rests on trust and expectation rather than on an enforceable right to redeem.
6. How does a mint-and-redeem exploit work?
On a sidechain, new tokens are meant to appear only when bitcoin has been locked in the reserve. The software enforces that rule by validating each transaction before it is accepted by the network. If a flaw lets an invalid transaction pass validation, the network can accept tokens that have no matching deposit behind them.
Once such tokens exist, they look identical to legitimate ones. The holder can then request a peg-out, and the federation, trusting the network's own records, pays out real bitcoin from the reserve. Nothing about the redemption request itself appears unusual, which is why the damage came from the software error and not from any breach of the multisignature keys.
This is also why the unreturned portion matters so much. Every unbacked token that was redeemed took real bitcoin away from holders who had deposited honestly, so the gap in the reserve is borne collectively by those who still hold L-BTC.
7. Why reserve checks and audits matter after an incident
After a failure of this kind, operators generally need to establish two separate facts: that the flaw has been removed, and that the reserve can be accounted for in full. The first is the purpose of the Elements upgrade and the security audits. The second requires matching the bitcoin held by the federation against every L-BTC token in circulation.
Independent review adds credibility to both steps. A fix announced by the same team that operates the system is less reassuring than one checked by outside specialists, and users who lost confidence will look for that outside verification before returning.
Public reserve data also lets observers form their own estimates. The 86 percent figure is an example, as it comes from comparing publicly visible reserve balances with the supply of tokens, which is possible because the system's accounts are open to inspection.
8. What conditions must be met before peg-outs restart?
As of October 11, four conditions for restarting redemptions have been described. The first is restoring full one-to-one backing of the reserve. The second is upgrading Elements to remove the flaw that allowed the exploit. The third is completing security audits, and the fourth is changing how keys are managed, notably by moving them into cold storage.
Cold storage means keeping signing keys on devices that are not connected to the internet, which makes remote theft far harder. That the federation is considering it suggests the incident has pushed operators toward stricter operational security, even though the keys themselves were not the point of failure.
None of these conditions has a published completion date, and reporting does not specify how the missing bitcoin will be replaced. That leaves the timeline for resuming redemptions uncertain.
9. Why not reopen redemptions at 86 percent backing?
Refusing to reopen below full backing is the cautious choice. If redemptions resumed while the reserve covered only 86 percent of tokens, holders would have a reason to rush to redeem first, because the early redeemers would be paid in full and the last ones might receive nothing or only a fraction.
This dynamic resembles a run on a bank. Even people who would otherwise be content to hold L-BTC could feel pressure to withdraw quickly, which would drain the reserve faster and could leave the final holders without recourse. A pause stops that race and gives operators time to close the gap.
The trade-off is that a pause also freezes the value of an asset many users rely on, and the longer it lasts, the more holders must weigh the costs of waiting. For now, operators have judged that protecting the fairness of an eventual full repayment outweighs the cost of delay.
10. What the freeze means for the sidechain model
The episode highlights a basic trade-off in sidechain designs. They can offer speed and features that Bitcoin itself does not, but users must trust the bridge, the federation and the software that connects the two networks. A failure in any of them can affect holders who never interacted with the original flaw.
For users and institutions, the lesson centers on reserve transparency and independent verification. The ability to check whether tokens are fully backed, and to do so in real time, is a major factor in how much capital these systems can attract. Reserve gaps like this one draw attention to that need.
The next developments to watch are an announcement of a plan to fill the remaining shortfall, the completion of the audits, the Elements upgrade and key-management changes, and a date for peg-outs to resume. Until those arrive, L-BTC holders have a token that moves normally but cannot yet be exchanged for the bitcoin behind it.