DeFi United Fundraising Chips Away at Kelp Exploit Gap

DeFi United’s emergency fundraising effort is starting to narrow the hole left by the Kelp DAO rsETH exploit, but the numbers show the gap is not closed yet. As of April 26, 2026, coverage across The Defiant, The Block, Galaxy and other market reports points to a recovery pool that has moved from crisis response into balance-sheet triage. The real story is not just how much ETH has been pledged. It is how much systemic pressure that fundraising has removed from Aave, rsETH markets and the wider DeFi credit stack.

Recovery Commitments Cross 69,534 ETH After April 23 Launch

The fundraising is real. So is the remaining deficit. Coin360 reported that Aave announced DeFi United on April 23, 2026, as a multi-party recovery fund aimed at the rsETH backing shortfall left by the Kelp DAO exploit. Two days later, The Block reported that Aave service providers proposed a 25,000 ETH contribution to help close the remaining hole. MEXC News then put the recovery pool at roughly 69,534 ETH, or about $161 million, as of April 25, 2026.

That matters because the exploit itself was huge by any 2026 standard. The Defiant said Kelp had already clawed back 40,300 rsETH, roughly 43,000 ETH, after pausing bridge contracts 46 minutes into the attack. The same report said another 30,700 ETH was frozen by the Arbitrum Security Council on April 21, 2026. Across separate coverage, the exploit size was cited at $290 million by TechRadar on April 21, $292 million by Galaxy and Cointelegraph, and $293 million by CoinUnited. That narrow range suggests broad agreement on the scale even if exact mark-to-market values differ by source and timestamp.

Here is the angle many competitors have not pushed hard enough: DeFi United is not just a rescue fund. It is a firewall for interconnected lending markets. I have tracked enough DeFi stress events to know that once collateral confidence breaks, the damage spreads faster through lending books than through token charts. That is exactly why the fundraising pace matters more than the headline pledge count.

Why the rsETH Shortfall Hit Aave Harder Than the Headline Suggests

The exploit was not a plain treasury drain. Galaxy’s April 22 research note said the attacker minted unbacked rsETH through a compromised LayerZero-linked setup, while mainnet rsETH itself was not directly affected because it remained backed by Kelp’s underlying ETH staking deposits. The problem sat in the adapter and bridge layer. That distinction is crucial. It meant the exploit created a backing mismatch that could travel into lending venues where rsETH had already been accepted as collateral.

The Block’s April 24 report made that explicit: the unbacked rsETH was used as collateral on Aave to borrow real assets, leaving significant bad debt. Cointelegraph added another layer on April 22, reporting that Aave’s supplied balance had dropped sharply, with deposits down by $15 billion following the exploit as users pulled funds amid uncertainty. That is the kind of second-order effect that turns a bridge exploit into a market structure event.

That sequence shows why DeFi United matters. It is buying time for protocols that were never supposed to absorb a bridge-layer failure of this size. Lido’s language, quoted by Coin360, described “market rates pressure, elevated borrow/lending stress, and the risk of forced unwinds.” That is not PR fluff. It is a concise description of how collateral contagion works when one synthetic or restaked asset loses clean backing.

Exploit Size Near 18% of Supply While Mainnet Backing Stayed Intact

This is where the story gets more nuanced. CoinUnited and DefiPrime both said the attacker drained or minted roughly 116,500 rsETH, equal to about 18% of circulating supply. Yet Galaxy argued that mainnet rsETH was not directly impaired because the underlying ETH staking deposits were still there. Both statements can be true at once. The exploit damaged the bridged representation and the credit plumbing around it, not necessarily every unit of native economic backing.

That split explains the fundraising logic. DeFi United is not trying to recreate the entire Kelp balance sheet from scratch. It is trying to patch the part of the stack where liabilities became socially distributed across protocols. In plain English: the fundraiser is aimed at the hole that matters most for market confidence.

There is another underappreciated point. The Defiant’s reported 40,300 rsETH clawback and the 30,700 ETH freeze together imply that early containment actions addressed a large chunk of the immediate damage before fundraising even accelerated. Add the 69,534 ETH cited by MEXC News, and the market is looking at a layered response: technical containment, governance intervention and socialized recapitalization. That is unusual. It also tells you DeFi’s informal lender-of-last-resort mechanisms are evolving in public.

Can DeFi United Close the Gap Without Socializing More Losses?

That is the question now. If the 69,534 ETH figure is accurate and the exploit involved about 116,500 rsETH, the simple residual gap is still close to 46,966 ETH before accounting for recoveries, legal outcomes, asset sales or further freezes. If Aave’s 25,000 ETH proposal is approved and delivered, it would represent more than one-third of the reported recovery pool. Helpful, yes. Sufficient on its own, no.

Data Verification: Exploit size was cross-referenced across TechRadar ($290 million, published April 21, 2026), Galaxy ($290 million, published April 22, 2026), Cointelegraph ($292 million, published April 22, 2026), DefiPrime ($292 million, published April 19, 2026), and CoinUnited ($293 million, published April 19, 2026). Recovery figures were cross-checked against The Defiant, The Block, Coin360 and MEXC News reports published April 23-25, 2026.

The bottom line is straightforward. DeFi United has chipped away at the Kelp exploit shortfall, and it has probably reduced the odds of a deeper lending-market spiral. But the fundraiser is not a clean resolution yet. It is a partial repair job on a system that learned, again, that bridge risk does not stay at the bridge.

Frequently Asked Questions