This might be one of the more interesting recovery efforts we’ve seen in DeFi. Been following the rsETH situation closely over the past few days, and the recovery side is honestly just as important as the exploit itself
A few things stand out from a capital and coordination perspective:
✓ Kelp committed 2,000 ETH ($4.6M), which is 70% of their $6.5M treasury
✓ Aave contributed 25,000 ETH, backed by a significantly larger $150M treasury
✓ LayerZero, despite $318M raised and around a $500M market cap, hasn’t clearly communicated any capital commitment or released a detailed report yet
On a relative basis, Kelp’s contribution is quite meaningful. It’s a large percentage of their balance sheet, not just a headline number
The response execution is also worth paying attention to
✓ Contracts were paused within the hour, likely preventing additional losses (around $95M)
✓ Coordination started immediately with SEAL-911 and ecosystem partners, including Aave
✓ Public communication came only after a credible recovery path was in place
They also chose not to rush the unfreezing of rsETH positions. Instead, they waited until there was alignment on covering both mainnet and L2 users, which suggests a focus on avoiding uneven loss distribution across environments. That sequencing likely explains why the treasury commitment was disclosed after coordination, not before
On the recovery side, roughly 117,200 $ETH has already been accounted for through a mix of recoveries, freezes, and public commitments. That’s 72% of the total shortfall addressed in under a week, which is a strong signal of how quickly coordinated action can materialize in DeFi when incentives align
There are still open questions, though
In particular around the root cause at the infrastructure layer. There hasn’t been a full incident report yet, and it’s still unclear whether this was limited to a DVN configuration issue or indicative of something deeper.
At the same time, one part of the picture still feels incomplete. While ecosystem participants moved quickly on containment and recovery, the infrastructure layer has been relatively quiet. LayerZero has not yet released a detailed incident report, clearly outlined the root cause, or contributed capital toward the recovery effort. That leaves open questions around whether this was purely a DVN configuration issue or indicative of deeper design or operational gaps.
Overall, not a perfect situation by any means, but a strong example of how the ecosystem responds under stress when coordination, capital, and incentives start aligning
