Liquid
Nov 4, 2026

Liquid reserve backing restored as 4,270.54 BTC now supports matching L-BTC

Liquid’s reserve backing has been restored after the shortfall created by the Sept. 6 exploit was fully covered, according to monitoring cited by Odaily and Bitcoin News. The incident stemmed from an Elements rangeproof verification flaw that let an attacker mint about 4,000 L-BTC without corresponding bitcoin reserves. That pushed backing down from roughly 4,205 BTC to 197 BTC. Most of the tokens were later returned. The remaining gap was closed with a final 250 BTC deposit made on Nov. 2. SideSwap now shows that 4,270.54 BTC backs an equal amount of L-BTC, indicating that full reserve support has been restored on that basis. Even so, direct redemption through the federation remains restricted. Users who want to exit still need to do so through swap or exchange service providers rather than redeeming directly through the consortium.

780
Liquid reserve backing restored as 4,270.54 BTC now supports matching L-BTC
Elements
Nov 4, 2026

Elements flaw let attacker mint about 4,000 L-BTC without Bitcoin backing

Bitcoin News said an attacker exploited a range proof verification flaw in Elements to mint about 4,000 L-BTC without corresponding Bitcoin reserves. The incident reduced backing reserves from about 4,205 BTC to 197 BTC. Most of the tokens were later returned, and the final 250 BTC deposited closed the gap. SideSwap now shows 4,270.54 BTC backing an equal amount of L-BTC. Direct redemption through the federation remains restricted, and users still need to exit through swap service providers. The report focuses on the reserve shortfall, the later restoration of backing, and the current redemption limits that remain in place.

710
Elements flaw let attacker mint about 4,000 L-BTC without Bitcoin backing
Liquid
Nov 2, 2026

Liquid reserve gap drops to 250 BTC after 300 BTC top-up

Liquid’s reserve shortfall has narrowed to 250 BTC after a 300 BTC top-up, according to The Defiant. The update pushed the estimated backing ratio for L-BTC to 94.14%, showing an improvement in reserve coverage but not a full restoration yet. The report said the federation’s recovery plan still requires reserves to return to 100% before direct peg-outs can resume. That means the latest top-up reduced the gap, but it did not reopen normal redemption flows. The figures point to progress in rebuilding reserves while leaving the final step of the recovery plan unmet.

960
Liquid reserve gap drops to 250 BTC after 300 BTC top-up
Liquid
Oct 20, 2026

Liquid says Bitcoin swaps are back, but peg-outs remain frozen

Liquid said Bitcoin swaps have been restored, while peg-outs are still frozen. The update indicates that reserves currently cover about 85.8% of outstanding L-BTC, leaving an estimated shortfall of roughly 603 BTC. TheDefiant reported the development in a brief item, which also noted that its articles are stored on Filecoin. The available source text did not provide additional operational details, timing beyond the publication record, or further explanation for the freeze. Based on the supplied material, the key points are limited to the status of swaps, the continued halt on peg-outs, and the reserve coverage figure tied to circulating L-BTC.

1160
Liquid says Bitcoin swaps are back, but peg-outs remain frozen
Liquid Network
Sep 15, 2026

How 4,000 BTC Left Liquid Network’s Vault Without a Stolen Key

On Sept. 6, roughly 4,000 BTC, worth about $320 million at the time, left Liquid Network’s federation wallet in what the article describes as the largest crypto theft of 2026 so far. What made the incident unusual was not just the size. No private key was reported stolen, no hardware security module was broken, and no insider compromise was identified. The 11-of-15 multisig process still worked exactly as designed. The reported failure point was lower in the stack: the software logic used to verify whether newly issued L-BTC was valid. According to the reconstruction cited in the source article, an attacker abused a range-proof cache issue in Elements, the open-source node software used by Liquid, allowing 3,996 unsupported L-BTC to be accepted and later redeemed for real BTC through the normal peg-out path. The article notes that Blockstream has not formally confirmed that this exact bug caused the theft, but says external researchers linked the timeline to a patch that had already been written before the attack and was merged too late for the federation nodes running in production. The attacker later returned 3,400 BTC and kept 598.5 BTC while calling themselves white hats and demanding an additional payout. Blockstream publicly rejected that demand, said it would not pay ransom, and maintained that L-BTC holders would not be haircut to cover the loss.

1450
How 4,000 BTC Left Liquid Network’s Vault Without a Stolen Key
SlowMist
Sep 11, 2026

SlowMist details Liquid exploit that minted 3,998.5 L-BTC without collateral

SlowMist said on X that Liquid Network was hit by a Rangeproof verification cache key collision exploit on Sept. 6. According to the security firm, the attacker minted about 3,998.5 L-BTC without any corresponding BTC peg-in, then converted the tokens into Bitcoin on the main network through peg-out transactions within minutes. After the incident, about 3,400 BTC was returned to the Liquid federation peg wallet, while roughly 598.5 BTC remains under the attacker’s control. SlowMist said the flaw came from the way Elements constructed Rangeproof verification cache keys by concatenating multiple variable-length fields without adding length prefixes. That allowed different parameter combinations to produce the same cache key. By crafting transactions to trigger a cache collision, the attacker caused nodes to hit a previously cached “verification passed” result, skipping both secp256k1_rangeproof_verify and the minimum amount check. SlowMist added that it has traced the Bitcoin-side fund flows and completed its analysis of the incident.

1530
SlowMist details Liquid exploit that minted 3,998.5 L-BTC without collateral
Liquid Network
Sep 10, 2026

Liquid Network resumes block production, while transactions and peg operations stay halted

Liquid Network has restarted block production after deploying emergency software updates, but the network is still operating without transactions as it monitors stability. Peg operations, including PAK-authorized peg-outs, remain suspended while Liquid works to restore its BTC/L-BTC reserves. The recovery follows a Sept. 6 incident in which actors claiming to be white-hat hackers withdrew about 4,000 BTC, valued at roughly $320 million at the time, from the federation wallet. Liquid said the incident was tied to a proof-verification cache vulnerability in Elements, the open-source software that underpins the network. A day before block production resumed, the network released Elements v23.3.4 to harden cache keys used for range proofs. After Blockstream said affected bridge nodes had been patched, 3,400 BTC, worth about $270 million at the time, was returned. As of Sept. 7, about 598 BTC, valued at roughly $46 million at current prices, was still outstanding.

1130
Liquid Network resumes block production, while transactions and peg operations stay halted
Samson Mow
Sep 10, 2026

Samson Mow warns alleged Liquid attacker, says all user assets must be returned in full

Samson Mow warned the alleged attacker involved in the Liquid incident, saying the person may have left more traces than expected, according to monitoring cited by Bitcoin News. Mow said 「正义之网广泛且无法逃脱,不会放过任何人。」, which translates to a warning that justice is wide-reaching and inescapable. He also challenged the attacker’s reported demand to return bitcoin in exchange for a bounty, questioning whether it was wise to publicly admit taking bitcoin and then ask for a reward. Mow added that roughly $5 billion in Liquid-related assets, including L-BTC, Tether and real-world assets, belong to their respective issuers and holders, so they should not be used as the basis for calculating any bounty. He said that regardless of whatever else may be negotiated, all user assets must be returned in full.

1660
Samson Mow warns alleged Liquid attacker, says all user assets must be returned in full
Total 12 items
Go topage