When will Liquid Network restore Bitcoin peg outs?
Liquid is getting closer to reopening Bitcoin withdrawals, but the final recovery step is still locked down. The latest update says an external audit of Elements v23.3.4 is underway, while the Liquid Federation replaces entries in its Peg out Authorization Key, or PAK, system and hardens the Bitcoin receiving keys tied to peg outs.
- External audit of Elements v23.3.4 underway
- PAK entries being replaced
- Bitcoin receiving keys moving to cold storage
- No date yet for peg-out restart
- About 602 BTC still being pursued
That matters because peg outs are Liquid’s bridge back to Bitcoin’s base chain. Users can still transact inside Liquid without them, but if the withdrawal path stays shut, the network is running with a major safety valve turned off. Call it a sidechain with one door bolted from the inside.
In its Sept. 28 ecosystem update, Liquid said an external security audit of Elements v23.3.4 is now in progress. Elements is the open-source blockchain platform behind Liquid, and the patched release was published after the Sept. 6 incident exposed a serious flaw in the software.
Liquid also said the federation is updating its PAK list. Existing entries are being replaced, and the network is working to make sure the Bitcoin receiving keys tied to peg outs are secured in cold storage, meaning offline storage designed to reduce exposure to online attacks.
No restart date was provided. Another update is expected shortly, which in plain English means the network is not ready to reopen withdrawals yet.
What happened on Sept. 6
On Sept. 6, an attacker created roughly 4, 000 unbacked LBTC and used Liquid’s normal peg-out process to withdraw Bitcoin from the federation reserve. That distinction matters: the attacker did not just create a suspicious token balance, they reportedly turned that bogus balance into a real BTC withdrawal.
LBTC is Liquid Bitcoin. “Unbacked” means the tokens were created without the matching Bitcoin reserve that is supposed to support them. That is not innovation. That is counterfeit collateral with better branding.
Liquid’s assessment said the problem started with the way Elements cached results of rangeproof verification. Rangeproofs are cryptographic checks used in confidential transactions to confirm that amounts are valid without revealing them.
According to Liquid, an earlier change removed some transaction context from the cache key. That created a consensus flaw, because different transactions could end up sharing the same cached result even though they should not have been treated as equivalent.
Liquid said a first fix addressed that initial issue, but a second problem remained in how fields were combined in the cache key. The attacker exploited that remaining weakness to create an output whose value was not backed by its inputs.
The hardened fix changed how rangeproof and surjection proof cache keys are built by serializing each field with a length prefix. In simpler terms, that helps prevent different sets of inputs from being treated as identical by the cache system.
The fix was merged into the Elements 23.3.x release branch on Sept. 8, and Elements v23.3.4 was published the following day. After functionary nodes received the updated software, Liquid resumed block production. Transactions later returned as the network moved through a staged recovery. Peg outs did not.
Why peg outs are the hardest part to restore
Liquid’s peg-out process depends on the federation’s authorization setup. Under that system, each PAK entry contains two keys with different jobs.
One part is tied to a member’s Bitcoin receiving wallet and is meant to stay offline. The other is an online signing key used to authorize peg-out requests on an Elements node.
Functionary nodes use the offline component to verify that the Bitcoin destination matches a registered PAK entry. That structure is supposed to stop unauthorized withdrawals and reduce damage if one piece of infrastructure is compromised.
In the Sept. 6 incident, Liquid said two separate problems lined up: the Elements consensus flaw and a gap in the configuration of one federation member’s PAK signing process.
SideSwap, the federation member involved in that peg-out path, said the federation knew its peg-out authorization key operated online and that this arrangement had been visible in its peg outs for years. SideSwap also said it had not been told to change how the key operated or suspend peg outs before the incident.
The company said it is reviewing how its authorization key is held and what checks and limits apply to payouts, and it will not restore its peg services until it and the federation are satisfied with the revised security setup.
That is the ugly truth about federation-based systems: they can be fast and useful, but they are only as solid as the operational assumptions behind them. If a key is online when the system’s safety model was assumed to be stronger than that, the whole setup gets a lot less elegant very quickly.
How much was taken, and how much came back?
The original incident resulted in approximately 4, 000 BTC leaving the federation reserve. The attackers identified themselves as white hats in an on-chain message, and later returned 3, 400 BTC to the federation wallet after Blockstream confirmed affected nodes had been patched.
According to Liquid’s latest detailed incident assessment, approximately 602 BTC remains unrecovered and is still being pursued through recovery efforts. Blockstream rejected a bounty demand tied to the remaining funds and said it would work with law enforcement, exchanges, forensic specialists, and other service providers to try to recover them.
That is better than losing the whole stack, obviously. But it is still a reminder that “we got most of it back” is not the same thing as “the system was fine.” If a network can be pushed into emergency recovery mode by a consensus bug and a weak withdrawal setup, the trust model needs work even after the patch is in place.
What happens next?
Liquid says the audit and PAK changes are the steps needed before peg outs can safely resume. That sequence makes sense: patch the software, audit the patch, harden the key management, and only then reopen the withdrawal path.
Until that work is complete, peg outs remain the last major restriction in Liquid’s recovery. Block production is back. Transactions are back. The route back to Bitcoin is still waiting for the all-clear.
For users, that means Liquid is not fully back to normal. For everyone else, it is a blunt reminder that Bitcoin-adjacent systems do not get to survive on vibes. They live or die on boring controls, careful key handling, and whether the federation actually knows where its keys are stored.
Key takeaways
-
When will Liquid peg outs resume?
Liquid has not given a date. The network says it is still auditing Elements v23.3.4 and updating the PAK system before withdrawals restart. -
Why are peg outs still disabled?
Liquid froze withdrawals after the Sept. 6 incident exposed a consensus flaw in Elements and a weakness in one federation member’s peg-out authorization setup. -
How much BTC is still missing?
Approximately 602 BTC remains unrecovered and is still being pursued, according to Liquid’s latest incident assessment. -
What is the PAK system?
PAK stands for Peg out Authorization Key. It is part of Liquid’s federation model and helps authorize withdrawals from Liquid back to Bitcoin. -
What does cold storage change here?
Cold storage keeps private keys offline, which reduces exposure to online compromise. Liquid says it is securing the Bitcoin receiving keys tied to peg outs that way before withdrawals resume. -
Is Liquid fully recovered yet?
Not yet. Block production and transactions have resumed, but peg outs are still disabled while security work and the audit continue.
The broader lesson is simple: if a Bitcoin sidechain promises a reliable bridge back to BTC, that bridge needs to be boring, hardened, and ugly in all the right ways. Liquid is trying to get there. It just is not there yet.
Further reading
A few related resources worth skimming if you want more background around Liquid, outages, and the usual crypto chaos:
