Arbitrum DAO Votes 90% to Get $71 Million in ETH Frozen After Kelp DAO Exploit
Uncategorized

Arbitrum DAO Votes 90% to Get $71 Million in ETH Frozen After Kelp DAO Exploit

In one of the most closely watched governance votes in DeFi this year, the Arbitrum DAO has overwhelmingly backed a proposal to release approximately $71 million in Ether that has been frozen since the Kelp DAO rsETH exploit.9 million ARB tokens – a result that signals broad community alignment behind a coordinated cross-protocol recovery effort.

The Backstory: What Happened to Kelp DAO

The Kelp DAO exploit was one of the more technically complex DeFi hacks of the past year. An attacker drained 116,500 rsETH – a liquid restaking token – from Kelp DAO’s smart contracts in a move that stripped hundreds of millions in user backing from the protocol. The attack left Kelp’s rsETH token undercollateralized and its users exposed to significant losses.

As part of the post-exploit containment effort, approximately 30,765.67 ETH – worth roughly $71 million at current prices – was frozen inside Arbitrum’s on-chain infrastructure. The freeze was a protective measure designed to prevent the attacker from moving or liquidating those funds while the affected protocols attempted to coordinate a recovery response.

The resulting standoff between Kelp DAO and LayerZero – another protocol involved in the incident – has played out publicly, with what CryptoGazette previously covered as a “$292 million blame war” over liability and responsibility for the exploit’s losses.

The Vote: Near-Unanimous Approval

The proposal to unfreeze the 30,765.67 ETH cleared the governance vote with 90.5% approval. Of the 173.9 million ARB tokens cast in the vote, fewer than 10% opposed the motion. The scale of support reflects a community consensus that holding the funds frozen indefinitely was no longer appropriate once sufficient due diligence and legal review had been conducted.

According to KuCoin and CryptoNews coverage, the vote formally sets the stage for the funds to be released and directed toward compensating rsETH holders who suffered losses in the exploit – though the full distribution mechanism still needs to be finalized.

Why This Matters for DeFi Governance

The Arbitrum vote is significant for several reasons beyond the dollar amount involved.

First, it demonstrates that DAO governance can function under extreme pressure. Managing a nine-figure frozen asset position while navigating cross-protocol legal disputes and community sentiment isn’t a simple task. The fact that the vote achieved near-unanimous support suggests that the Arbitrum community rallied around a coherent recovery narrative rather than fracturing into competing factions.

Second, it tests the limits of on-chain governance as a recovery mechanism. When exploits occur in DeFi, there’s rarely a clean path to restitution. Arbitrum’s willingness to use its governance process to help victim compensation sets a precedent – and one that future hacked protocols will almost certainly reference.

Third, the Kelp case is a stress test for cross-chain liability. LayerZero’s involvement introduced inter-protocol complexity that single-chain governance wasn’t designed to handle. The resolution – however imperfect – will inform how the industry approaches similar situations.

Legal Challenges Still Pending

The governance approval isn’t the final word. According to IndexBox, there’s at least one ongoing legal challenge related to the frozen ETH and the exploit’s recovery process. The legal proceedings introduce uncertainty about timing and may affect how or when the unfrozen funds actually reach affected users.

The cross-protocol nature of the dispute – involving Kelp DAO, LayerZero, and Arbitrum’s governance layer – means that any single legal proceeding could have ripple effects across the recovery plan. Stakeholders have been warned to expect a drawn-out process even after the governance vote passes.

The Broader Context: 2026 Is a Bad Year for DeFi Exploits

The Kelp DAO recovery effort is happening against a backdrop of escalating losses across DeFi. TRM Labs data shows that North Korea alone was responsible for 76% of all 2026 crypto hack losses through just two attacks. The DeFi sector has proven particularly vulnerable to sophisticated exploits that target bridging and restaking infrastructure – the same categories that brought down Kelp DAO.

For users, the Arbitrum vote offers a rare piece of good news: that some of the money is coming back. For the industry, it’s a reminder of how much damage a single smart contract vulnerability can still do in 2026, despite years of auditing improvements and security tooling.

FAQ

What was the Kelp DAO exploit? Kelp DAO suffered an exploit that drained 116,500 rsETH tokens from its smart contracts, leaving the protocol significantly undercollateralized. The attack triggered a cross-chain response that resulted in approximately 30,765 ETH being frozen on Arbitrum as a protective measure.

Will Kelp DAO users get all their money back? The $71 million represents a partial recovery. The full amount of losses from the exploit was significantly larger. Distribution details for how recovered funds reach affected users are still being finalized and may be subject to ongoing legal proceedings.

What does this mean for Arbitrum’s governance? The successful vote demonstrates that Arbitrum’s DAO can mobilize quickly and achieve consensus on major financial decisions even in complex, adversarial situations – a positive data point for the chain’s governance model.

*Sources: KuCoin, MEXC News, Crypto.news, CryptoNews.net, IndexBox*

================================================== DE-AI Processing Summary ================================================== Unicode artifacts cleaned: 15 – Fancy punctuation: 15 Phrases deleted: 2 Words replaced: 2 Contractions added: 6 ==================================================

cg_editor

cg_editor

Crypto Reporter

cg_editor covers cryptocurrency markets, blockchain technology, and decentralized finance for CryptoGazette.

Leave a Comment

Your email address will not be published. Required fields are marked *