Liquid Network Restores Full Bitcoin Backing After $320M Exploit

According to CoinDesk, Liquid Network's bitcoin IOUs are fully backed again after a $320 million exploit, with a final 250 BTC transfer closing the hole left by September's bug. The federation behind the network has not disclosed who paid to fill it. The development matters for anyone holding Liquid-issued bitcoin claims, because full backing is the operational baseline for redemption and settlement. The confirmed change is the restored reserve; the unresolved detail is the funding source.

What the Final 250 BTC Transfer Changed

CoinDesk reported that the last 250 BTC transfer completed the restoration of Liquid's bitcoin reserves. The exploit had left a $320 million gap, and the final transfer closed it. The Block reported that Samson Mow, a Liquid Federation board member, said Blockstream provided the missing bitcoin after the September exploit left nearly 600 BTC unreturned. That figure is the clearest operational marker: the shortfall was measured in bitcoin, not in a synthetic claim, and the repair was executed in the same unit.

The affected participants are Liquid users who hold bitcoin IOUs, the federation members who govern the sidechain, and Blockstream as the entity that supplied the funds. For holders, the practical consequence is that redemption claims are again matched by reserves. For the federation, the consequence is governance scrutiny: the reserves are restored, but the funding path remains a detail that requires a source-document check.

Blockstream's Role and the Hardened Defenses

Decrypt reported that Blockstream CEO Adam Back said the sidechain's defenses have been hardened, and warned developers not to trust AI-suggested fixes blindly. That warning is operationally specific. It tells developers that code changes proposed by automated tools need human review before deployment, especially in a system that custodies bitcoin claims.

The Block's report adds that Blockstream provided the funds, which separates two roles: Blockstream as liquidity provider for the reserve gap, and Blockstream as the operator whose CEO is describing defense changes.

For developers building on Liquid, the shared operating impact is a stricter review standard. A fix that looks correct in an AI-generated patch still needs testing against the sidechain's custody and federation rules. The confirmed change is the hardened defense posture described by Back. The unconfirmed detail is the exact scope of those changes, which requires checking the federation's technical documentation rather than relying on the interview summary.

Who Is Affected and What the Restored Backing Means

The affected participants span three groups. Holders of Liquid bitcoin IOUs are affected because their claims are again fully backed. Federation members are affected because they must explain the funding and the defense changes. Developers are affected because the review standard for fixes has been raised. The shared operating consequence is that settlement and redemption on Liquid can proceed against a restored reserve, but the governance record is incomplete.

This is not a price-direction call. Bitcoin's spot price was $77,249.92 at the time of capture, according to the supplied market data, and that figure does not establish what happens next. The relevant risk taxonomy here is custody and counterparty risk: a sidechain that issues bitcoin IOUs depends on the federation's custody controls and on the willingness of a large holder to supply missing bitcoin. Liquidity risk also applies, because a restored reserve does not guarantee deep markets in Liquid-issued claims.

The Source-Document Check Still Pending

The confirmed facts are the restored backing, the final 250 BTC transfer, the near-600 BTC shortfall reported by The Block, and Back's statement that defenses were hardened. The unresolved detail is who paid to fill the gap. CoinDesk reported that the federation has not said who funded it, while The Block reported that Blockstream provided the funds. Those two statements are compatible only if Blockstream is the funder and the federation has not formally named it.

The next check is the federation's own disclosure: a reserve attestation or governance note that names the funding source and describes the defense changes. Until that document appears, readers should treat the funding path as reported but not formally confirmed. The operating implication is that full backing is restored, while the governance transparency around the repair remains a separate item to verify.

Reference

• https://www.coindesk.com/markets/2026/11/03/liquid-s-bitcoin-ious-are-fully-backed-again-after-a-usd320-million-exploit
• https://decrypt.co/382397/liquid-network-restores-full-bitcoin-backing-two-months-after-320m-exploit
• https://www.theblock.co/news/ecosystems/2026-11-03-liquid-network-restores-full-bitcoin-backing-following-exploit-432387