Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
BTC Liquid network software vulnerabilities caused nearly 4,000 BTC to flow out, triggering a sidechain security mechanisms to examine a software vulnerability in
Liquid network, causing nearly 4,000 BTC to leave the platform reserve in a way that is deemed legal by the network's own verification logic. This incident has attracted widespread attention in the industry to the security and monitoring mechanism of the "peg-out" process on the Bitcoin sidechain.
Specific circumstances triggered by the vulnerability
According to SlowMist security researchers, this exploitation resulted in 3,998 L-BTC being minted on the Liquid network. The corresponding Bitcoin sidechain capital flows were treated as effective "anchored exits", which means that at the network rule level, the outflow was not marked as abnormal at the time.
Blockstream, which is responsible for developing and maintaining the Liquid network, subsequently confirmed the issue and stated that patches and remedies had been implemented on the bridge nodes after the exploit occurred. As of press time, there have been no official confirmation of technical details on the root cause of the vulnerability.
Questions about safeguards and disclosure
In the alliance chain, the integrity of reserve assets relies on the bridge node to correctly verify "anchored deposit" and "anchored exit" requests. If a vulnerability allows an "anchored exit" without proper authorization to be considered valid, this removes one of the core control layers. At present, authoritative sources have not confirmed whether the affected BTC has been recovered, frozen or is still outside the reserve.
读者需注意，不同报道对该事件的定性存在差异：慢雾将其归类为“漏洞利用”（exploit），而链上记录显示其是通过有效的“锚定退出”路径处理的。这种区别是否会影响用户余额或储备偿付能力，是一个关键的不确定因素。
后续关注重点
在情况完全明朗之前，以下三点需要得到确认：
- 官方对漏洞性质及其所利用的交易路径的解释；
- 对当前储备状态及任何补救措施的确认；
- Blockstream发布声明，说明客户持有的L-BTC头寸是否受到影响。
核心要点总结
一处软件漏洞导致近4,000枚BTC（根据慢雾数据为3,998枚）离开Liquid储备。
尽管源于漏洞利用，但根据链上记录，该流出被处理为有效的“锚定退出”。Blockstream已修复桥接节点，但储备状态和客户风险敞口仍未获确认。
免责声明：本文仅供参考，不构成财务或投资建议。加密货币和数字资产市场存在重大风险。在做任何决策前，请务必进行独立研究。
