THORChain (RUNE)

$Rune (4h) couldn't go above the S/D Zone... https://t.co/Q0ZPTm9vUK

THORChain is preparing for a staged restart after the May 15 exploit as developers and security teams continue recovery efforts. Nodes have now approved ADR028, the hacker bounty program is active, and the protocol expects protocol-owned liquidity to help cover the remaining losses. The team is also testing v3.19.0 while tss-lib remains under a temporary closed security audit period to strengthen overall security before full operations resume. The situation shows how major DeFi protocols are prioritizing recovery coordination, transparency, and infrastructure security during high-pressure moments. BingX

THORChain is slowly moving toward recovery after the May 15 exploit. Nodes already approved ADR028, the hacker bounty is active, and the team is preparing a staged restart while testing v3.19.0. Interesting part is that protocol-owned liquidity is expected to absorb the remaining losses instead of pushing the damage entirely onto users. Also noticed tss-lib is still under a temporary closed security audit period while fixes are being reviewed. Security pressure in DeFi keeps getting more serious every cycle. #THORChain #BingX

$RUNE trading will be re-enabled on Maya soon https://t.co/qYMoev1mzf

THORChain is gradually working toward recovery after the May 15 exploit. The team is preparing a staged restart of the network while developers and security teams coordinate fixes. Nodes have already approved ADR028, and a hacker bounty program is now active to help recover stolen funds. Protocol owned liquidity is expected to cover part of the losses, while the team continues testing version 3.19.0. The security system (tss lib) is also under a temporary closed audit. Overall, the project is taking a careful, step by step approach to restore stability and trust. #THORChain #BingX

What THORChain's incident response revealed about the protocol @THORChain's May 15 $10.7M exploit has been widely covered. What hasn't been discussed enough is how the network actually responded – and what that says about the protocol's architecture. The automated systems caught it before humans did. Within minutes of the vault imbalance, THORChain's solvency checker fired automatically across ETH, AVAX, BSC, BASE, DOGE, and GAIA. No one pressed a button. THORChain's own infrastructure caught it first. 18–20 independent nodes coordinated with no central commander. Nodes independently identified the threat, stacked manual pauses, and cast on-chain governance votes that brought the network to a controlled halt in roughly two hours. Only one vault out of five was affected. The vault isolation architecture did its job. Four vaults were completely untouched. For a protocol handling cross-chain liquidity across a dozen blockchains simultaneously, that containment is a meaningful architectural win. The community is voting on the recovery. No bailout, no central decision. The community votes on how to share it. Full transparency from minute one. Block numbers, node addresses, timestamps, vote tallies – all public, all in the report. The on-chain record is the statement. The response was fast and the damage was contained. Now the goal is to restart the network as soon as possible.

ALERT: DeFi bridge hacks in 2026 have now caused at least $328.6 Million in losses across eight major exploits. Following the KelpDAO exploit, total DeFi TVL also dropped from nearly $100 Billion to around $86 Billion. The recent wave of attacks is once again raising serious concerns around bridge security, smart contract risks, and overall confidence in the DeFi ecosystem.

🚨 @THORChain proposes a recovery plan after the May 15 hack 👀 According to the proposal, no new $RUNE tokens will be minted or sold as part of the recovery plan 🔥 The step aims to avoid increasing inflationary pressure on the token while trying to contain the effects of the breach and restore community trust 📉 The THORChain community is now monitoring the implementation details and how the network will handle the security and financial ramifications of the incident 🌐