Software Flaw Let Nearly 4,000 BTC Leave Liquid Reserve

A software flaw in the Liquid Network allowed nearly 4,000 BTC to exit the platform’s reserve through a mechanism that the network’s own validation logic treate...

Software Flaw Let Nearly 4,000 BTC Leave Liquid Reserve

A software flaw in the Liquid Network allowed nearly 4,000 BTC to exit the platform’s reserve through a mechanism that the network’s own validation logic treated as legitimate. The incident has drawn scrutiny to how peg-out processes are secured and monitored on Bitcoin sidechains.

What the reported flaw triggered

According to security researchers at SlowMist, the exploit minted 3,998 L-BTC on the Liquid Network. The corresponding Bitcoin-side movement was processed as a valid peg-out, meaning the network’s own rules did not flag the outflow at the time it occurred.

Blockstream, which develops and maintains the Liquid Network, subsequently confirmed the issue and said the bridge nodes were patched following the exploit and bridge-node remediation. No further technical breakdown of the flaw’s root cause has been confirmed at the time of writing. For related coverage, see Nearly 4,000 BTC Leaves Liquid Through Valid Peg-Out.

Questions about safeguards and disclosure

Reserve integrity on a federated sidechain depends on the bridge nodes correctly validating peg-in and peg-out requests. A flaw that allows a peg-out to be treated as valid without proper authorization removes a core control layer. Whether the affected BTC has been recovered, frozen, or remains outside the reserve has not been confirmed by an authoritative source. For related coverage, see Crypto Options Nearly Double Market Share as Derivatives Shift: Report.

Readers should also note that the framing of this event differs across reports: SlowMist categorized it as an exploit, while on-chain records show it processed through a valid peg-out path. Whether that distinction affects user balances or reserve solvency is a key open question.

What to watch next

Three items require confirmed follow-up before the full picture is clear: an official explanation of the flaw and the transaction path it exploited; confirmation of the reserve’s current status and any recovery measures; and a statement from Blockstream addressing whether customer-held L-BTC positions were affected.

TLDR KEY POINTS

  • A software flaw allowed nearly 4,000 BTC (3,998 BTC per SlowMist) to leave Liquid’s reserve.
  • The outflow was processed as a valid peg-out, according to on-chain records, despite originating from an exploit.
  • Blockstream has patched the bridge nodes; reserve status and customer exposure remain unconfirmed.

Additional source references: source document 1, source document 2.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.

More From Crypto News

Akita Inu

Author

Akita Inu

Akita Inu covers fast-moving crypto market updates, exchange news, and token ecosystem developments for CoinLive, with a focus on concise source-led reporting.