hn.today

Liquid Network Security Incident Assessment

blog.blockstream.com11 points0 comments
Screenshot of Liquid Network Security Incident Assessment

On September 6, 2026 an attacker exploited a consensus vulnerability in Elements’ rangeproof verification cache to create roughly 4,000 unbacked LBTC and move it through Liquid’s peg-out process, producing a Bitcoin withdrawal of about 4,000 BTC (confirmed in Bitcoin block 965,783). Smaller earlier peg-outs drained the reserve from ~4,205 BTC to ~197 BTC. The attacker identified themselves on-chain and returned 3,400 BTC on September 7; approximately 602 BTC remain outstanding. Liquid’s design - 15 geographically distributed functionary nodes with 11-of-15 block signing, confidential transactions using Pedersen commitments and rangeproofs, and a two-key Peg-out Authorization Key (PAK) model separating an offline receiving xpub from an online signing key - meant the exploit combined a consensus verification flaw with a gap in one member’s PAK signing configuration to enable the theft.

Root cause analysis found Bug A: a 2018 change that removed asset commitment and scriptPubKey from the rangeproof cache key so cached verifications could be reused in incorrect contexts, producing consensus mismatches; a related byte-boundary issue (Bug B) remained undetected by an initial fix. The defect was reported August 2, 2026, and rapid internal and external reviews converged on the root cause. Response actions included halting bridge nodes, deploying an emergency interim patch within hours, shipping Elements v23.3.4 as a full hardening release within days, and expanding AI-assisted legacy-code review and other corrective measures to prevent recurrence.

Read on blog.blockstream.com0 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Security

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.