Liquids – Bitcoin Platform https://bitcoinplatform.com Breaking Crypto News and Blockchain updates Thu, 24 Sep 2026 12:20:00 +0000 en-GB hourly 1 https://wordpress.org/?v=7.1.5 https://bitcoinplatform.com/wp-content/uploads/2026/09/cropped-fevi-18-32x32.png Liquids – Bitcoin Platform https://bitcoinplatform.com 32 32 Could a payout limit have stopped Liquid’s $320M exploit? https://bitcoinplatform.com/could-a-payout-limit-have-stopped-liquids-320m-exploit/ https://bitcoinplatform.com/could-a-payout-limit-have-stopped-liquids-320m-exploit/#respond Thu, 24 Sep 2026 12:20:00 +0000 https://bitcoinplatform.com/could-a-payout-limit-have-stopped-liquids-320m-exploit/ On September 6, 2026, the Liquid federation experienced a major security breach that resulted in the release of approximately 3,996 BTC. This incident occurred after the network accepted L-BTC that did not have proper Bitcoin backing. Liquid is a Bitcoin sidechain designed to hold Bitcoin in a federation reserve, with L-BTC serving as a representation of these holdings.

Alpen Labs CEO, Simanta Gautam, revealed that his AI agents were able to trace the flaw that led to the unauthorized release of funds. In a detailed account published on September 22, Gautam explained how the flaw was identified and reproduced locally within an hour. The technical report provided by Alpen Labs sheds light on the failed proof check that allowed the invalid sidechain state to be converted into a real Bitcoin payment.

The flaw in the system was related to how Elements, the software underlying Liquid, cached successful checks of cryptographic proofs attached to confidential transactions. A code change implemented on September 1 aimed to improve verification by including all relevant context in the cache. However, Alpen discovered that this change led to a vulnerability where a valid “seed” proof and an invalid target could produce identical cache input, bypassing the necessary proof check.

In a local replay of the incident, Alpen found that the cache was able to accept the invalid target due to the flawed caching mechanism. This demonstration highlighted the consensus failure that allowed the unauthorized withdrawal to take place. Subsequent changes made to the Elements software, including encoding field lengths in cache keys and adding collision-focused tests, aimed to prevent similar incidents from occurring in the future.

SideSwap, a platform affected by the attack, revealed that a private security build installed on its node had accepted the unauthorized transaction. This revelation underscored the need for enhanced security measures and continuous monitoring of network activity to prevent similar breaches.

Following the incident, Liquid announced that peg-outs were paused until full one-to-one BTC backing was confirmed, and necessary software updates, testing, and reviews were completed. The resumption of withdrawals would only occur once these measures were in place to ensure the security and integrity of the network.

Overall, the security breach in the Liquid network highlighted the importance of robust security measures, continuous monitoring, and prompt response to vulnerabilities to safeguard digital assets and prevent unauthorized access to funds.

]]>
https://bitcoinplatform.com/could-a-payout-limit-have-stopped-liquids-320m-exploit/feed/ 0