Liquid Network Suffers Critical Peg-In Bypass Attack
TREE NEWS reports: The Liquid Network, a Bitcoin sidechain operated by Blockstream, was exploited on September 6 in an attack that allowed an adversary to mint approximately 3,998.5 L-BTC without depositing any corresponding bitcoin through the network’s peg-in mechanism. SlowMist, the blockchain security firm that disclosed the incident, attributed the breach to a rangeproof verification cache key collision vulnerability — a flaw in how the sidechain validates cryptographic proofs tied to confidential transactions.
How the Attack Worked
Liquid uses confidential transactions to obscure amounts and asset types, relying on rangeproofs to prove that hidden values fall within valid bounds without revealing them. The attacker manipulated the cache key used during rangeproof verification, causing the system to accept fraudulent proofs. This allowed the minting of L-BTC — the sidechain’s representation of bitcoin — with no underlying BTC locked in the federation’s peg-in wallet. The attacker then redeemed the unbacked tokens for real BTC, draining value directly from the two-way peg.
Key aspects of the exploit include:
- No peg-in collateral: Roughly 3,998.5 L-BTC were created without any BTC deposit, breaking the 1:1 backing assumption that underpins the entire sidechain.
- Cache collision vector: The vulnerability stemmed from a collision in the rangeproof verification cache, a performance optimization that stores previously verified proof results.
- Real BTC extraction: The attacker converted the fabricated L-BTC into bitcoin, turning a purely digital flaw into a tangible loss of funds for the federation or liquidity providers.
Implications for Bitcoin’s Sidechain Ecosystem
The incident strikes at the core trust model of federated sidechains. Unlike trustless bridges secured by cryptography and smart contracts, Liquid relies on a federation of functionaries to custody the BTC backing L-BTC. A flaw that lets an attacker mint unbacked tokens undermines the peg’s integrity and raises uncomfortable questions about whether users can reliably redeem L-BTC for BTC at par. The event also highlights the risks of confidential transaction cryptography, which is complex and less battle-tested than transparent Bitcoin scripts. Cache-based optimizations, while efficient, introduce state-dependent attack surfaces that can be difficult to audit.
What Comes Next
Blockstream and the Liquid federation will need to disclose remediation steps — likely a patch to the rangeproof verification logic, a cache invalidation strategy, and potentially a rollback or compensation plan for affected holders. The broader lesson for the industry is that sidechains and Layer-2 systems inheriting Bitcoin’s security assumptions must treat proof verification as a first-class security boundary. As Bitcoin DeFi and tokenized asset activity migrate onto sidechains, exploits like this will draw heightened scrutiny from users, auditors, and regulators alike. Expect renewed calls for formal verification of cryptographic components and more conservative caching policies in high-value bridge infrastructure.
