Liquid Network resumes block production after $320M exploit
Liquid restarted block production after deploying emergency software updates, though transactions and peg operations remain suspended as recovery efforts continue.
Asanat Analysis — Why it matters
Liquid's resumption of block production signals a controlled recovery, but the suspension of peg operations—the mechanism allowing BTC deposits and withdrawals—represents a critical constraint on network functionality. A $320M exploit (likely affecting the peg mechanism or sidechain security model) indicates either a cryptographic vulnerability, consensus bug, or custody compromise. The fact that block production restarted before peg operations suggests developers are proceeding cautiously to prevent further loss, prioritizing network stability over liquidity restoration.
Liquid's extended downtime exposes structural risks in Bitcoin sidechains dependent on federated custody models. Unlike Layer 2 rollups with transparent on-chain settlement, Liquid relies on a functionary set to manage the peg—a trust assumption that, once broken, requires operational recovery rather than cryptographic proof. This incident will intensify scrutiny on other sidechain designs (Stacks, RSK) and may accelerate institutional preference for self-custodial scaling solutions. Recovery timelines and final loss quantification will determine whether Liquid retains market confidence for its derivatives and yield-seeking use cases.