The Liquid Network has restarted block generation as a precautionary measure to confirm full stabilization after a security incident involving the unauthorized withdrawal of approximately 4,000 Bitcoin. Although functionary nodes are now signing and validating blocks following required updates, transaction processing and peg operations, including PAK-authorized peg-outs, remain halted while the network works to restore its BTC/L-BTC reserve.
The disruption began on Sept. 6 when actors claiming to be white-hat hackers exploited a proof-verification cache vulnerability in Elements, the open-source software underpinning Liquid. This bug allowed them to withdraw about 95% of the federation wallet’s roughly 4,200 BTC balance, valued at $320 million. Blockstream subsequently released an emergency update, Elements v23.3.4, to harden cache keys. While 3,400 BTC worth $270 million was returned after bridge nodes were patched, approximately 598 BTC remained outstanding as of Sept. 7.
This development highlights the critical dependency of sidechain integrity on the underlying consensus software and the operational risks associated with complex cryptographic proofs. The decision to resume block production without transactions indicates a phased approach to restoring trust, prioritizing network stability over immediate functionality. It underscores that even established infrastructure can face severe liquidity shocks from single-point-of-failure vulnerabilities in core codebases.
For institutional observers, the partial return of funds demonstrates the efficacy of rapid patching and negotiation with ethical actors, yet the remaining $46 million exposure serves as a cautionary tale regarding custody and reserve verification. Stakeholders should monitor the timeline for fully restoring peg operations, as this will signal whether the network can maintain its collateralized value proposition without further intervention or capital injection.
