KelpDAO Recovery — Live Tracker
On-chain status of the 30,765.67 ETH frozen on Arbitrum One after the April 2026 KelpDAO exploit, plus the cross-DAO recovery flow. All data via Indexing Co pipelines.
Couple the news with what's actually on-chain.
The KelpDAO recovery is unfolding across many surfaces. Tweets, governance forums, multisig signatures, ETH moving across L2s, AIPs stacking up. The narrative is fragmented across X, Discord, Snapshot and a handful of news outlets.
This dashboard exists so anyone can pair a tweet or headline with the actual on-chain state. Every number you see traces back to a transaction hash, a forum thread, or a primary-source post. No press releases.
Built as a public utility by Indexing Co. Open source. Forkable. Designed so builders and researchers can run their own version against their own database.
What's tracked
- →The Arbitrum freeze: 30,766 ETH locked at
0x...0DA0+ the L1 Inbox upgrade tx that put it there - →Recovery commitments: every public ETH pledge to DeFi United, split between rsETH backing and market liquidity
- →Governance flow: Constitutional AIP, Snapshot proposals, forum posts, and on-chain governor events when they fire
- →Real-time wallet flows on the watched cohort (the frozen wallet, the recovery Safe, the rsETH OFT lockbox)
- →Security Council multisig events on Ethereum L1
For builders + researchers
Every pipeline that powers this dashboard is open source. Fork the repo, point it at your own database, run your own version. The patterns generalise to any cross-chain forensics or governance tracking.
- →3 live Indexing Co pipes (wallet flows, multisig, freeze events) writing to Postgres
- →Snapshot poller running on a GitHub Actions cron (every 15 min)
- →Verified address registry with a deployment guard (no fabricated addresses ship to the live pipeline)
- →Per-pipe READMEs with deploy + backfill recipes
What's not tracked yet
- Cross-chain laundering trail (Tornado Cash, THORChain, Umbra hops)
- Aave V3/V4 attacker positions (per-position health, liquidation status)
- Compound positions (similar)
- Other affected protocols beyond Aave + Compound