A DAO with $70 million in recovered hack funds just voted to move it, and a court says they can't.
The Summary
- Arbitrum DAO's Snapshot vote is passing with 90% support to release $71M in ETH frozen after the Kelp DAO exploit, moving toward a binding onchain governance proposal.
- A May 1 court order blocked Arbitrum DAO from moving the recovered funds, with Aave filing an emergency motion to keep them frozen.
- Web3 governance is colliding with Web2 legal system in real-time, with actual money on the line and no clear playbook.
The Signal
Here's what happens when code-is-law meets actual law. Arbitrum DAO recovered roughly $71 million in ETH from the Kelp DAO exploit, the community voted overwhelmingly to release it, and now a court order says don't touch it. The Snapshot vote is clearing 90%, which normally would be the end of the story in DAO land. Community decides, multisig executes, funds move.
Except Aave filed an emergency motion and got a court to freeze the funds on May 1. This isn't a theoretical governance edge case anymore. It's a live standoff between onchain voting and offchain injunctions.
"A DAO vote means nothing if a judge can freeze the treasury."
The mechanics matter here. The current vote is on Snapshot, which is offchain signaling. If it passes, the next step is a binding onchain Arbitrum governance proposal. That's when code actually executes. But code executing doesn't mean the legal issue disappears. If the multisig holders ignore the court order and move the funds, they're in contempt. If they obey the court, they're ignoring the DAO vote. Pick your liability.
This is the quiet crisis of Web3 infrastructure that nobody wants to talk about: DAOs still need humans to sign transactions, and humans live in jurisdictions. You can write unstoppable smart contracts all day. If the five people with the keys get served, the contract stops.
Key tensions:
- 90% community consensus vs. legal injunction
- Onchain governance execution vs. offchain legal compliance
- Return funds to victims vs. respect court process
Aave's position makes sense if you assume they're a creditor with a claim to the recovered assets. The DAO's position makes sense if you assume governance is final. Both can't be right. The Kelp DAO exploit created a pool of recovered funds, and now multiple parties think they have the best claim to distribute them. Courts are built for exactly this kind of dispute. DAOs are not.
What's interesting is that this is all happening on Arbitrum, a Layer 2 built for speed and low fees, not for its legal architecture. The DAO has no terms of service that clearly spell out what happens when a vote conflicts with a court order. Most DAOs don't. They assumed they wouldn't need one.
The Implication
If you're building or governing in Web3, this case is a preview of the next decade. DAOs will keep recovering funds, voting on distributions, and running into legal claims from creditors, victims, or regulators. The tooling is mature. The legal wrapper is not.
Watch what Arbitrum's multisig does. If they execute despite the court order, it sets a precedent that onchain governance trumps legal process. If they don't, every DAO with a treasury needs to ask: what's a vote actually worth if a single motion can override it?