THORChain restarts after $10.7M hack with no-mint recovery plan

THORChain's $10.7M vault drain tested the protocol's resilience — the no-mint restart plan reveals how DeFi handles failure.

THORChain node operators approved ADR028 on May 27, authorizing a staged restart that covers a $10.7M loss using Protocol-Owned Liquidity without minting new RUNE.

"The no-mint commitment removes one common post-hack reflex — inflating supply to recapitalize — and shifts the cost to the protocol's balance sheet," Chad Barraford, a THORChain contributor, said in the project's June 11 update.

The exploit drained a single Asgard vault on May 15, triggering emergency pauses and a coordinated code review. Developers shipped v3.18.1 as an immediate patch and v3.19 with store migrations implementing ADR028's loss-accounting methodology. A roughly $700,000 shortfall in migration logic was resolved by developer Codehans before the restart release went live.

The restart's credibility hinges on whether hardening changes — stricter key verification flows and phased chain rollouts — prevent repeat incidents without breaking core cross-chain swap functionality. Trading could resume as early as mid-June, with Zcash integration following within two weeks and Monero targeted for July 1-15.

The decision to use POL rather than minting or selling new RUNE sidesteps immediate dilution risk for tokenholders. The cost instead lands on the protocol's balance sheet, potentially reducing owned liquidity and affecting pool depth. Shallower pools can raise slippage and temporarily compress volume until market-makers and liquidity providers step back in.

Liquidity providers are shielded from a direct exploit-linked haircut under ADR028, but thinner protocol-owned depth could change rewards dynamics. Node operators must complete upgrades and verify key assignments; the professionalism of this cohort is a leading indicator for network safety.

When trading resumes, arbitrageurs will likely test edges across chains and centralized venues. If vault handling and settlement latency improve under v3.19.x, spreads should normalize. Conservative parameter sets — swap limits and throttles — may initially constrain throughput as a safety measure before loosening as confidence builds.

Re-enabling Zcash within two weeks and targeting Monero for early July signals confidence in vault operations under the updated releases. These integrations are complex, especially around key management and fee estimation, so their safe activation is a milestone for the restart's maturity.

Residual risks remain. The exploit vector could have adjacent variants that evade current mitigations. Using POL to cover losses may thin protocol-owned depth, increasing slippage during reopening. If parameters stay restrictive too long, liquidity providers and traders may shift volume elsewhere. Re-enabling privacy chains introduces fresh surface area in key handling and fee logic. Even with a smooth restart, some venues or wallets might delay reactivation, dampening volume.

This article is for informational purposes only and does not constitute investment advice.