Jack Paul 
Lido DAO, the governance body behind the liquid staking protocol Lido, has put forward a proposal to address leftover losses affecting its EarnETH vault. The move comes after an exploit involving the Kelp protocol caused disruptions across integrated DeFi products.
The affected vault holds about 9% exposure to rsETH, which translates to roughly $21.6 million. Residual losses are estimated between 400 and 600 ETH. These losses fall below the 1% threshold needed to trigger the $3 million first-loss buffer. That leaves a gap in user protection.
Why the gap exists
External parties are expected to resolve the main loss from the Kelp incident. However, smaller impacts remain, and they are not covered by the existing safety mechanism. Lido’s proposal seeks to adjust the threshold on a one-time basis. This would allow the protocol to cover these leftover amounts directly.
The goal, I think, is to preserve user trust without fundamentally changing the system. The fix is limited in scope, which helps contain broader protocol risk. If approved, confidence may stabilize among EarnETH users. But the restricted nature of the intervention also signals that not every loss will be covered in the future.
Treasury intervention tests Lido’s limits
Beyond the immediate fix, Lido’s response has highlighted the strength and constraints of its treasury. Following the rsETH shock, the DAO allocated up to 2,500 stETH—worth about $5 million—to stabilize affected positions and prevent forced liquidations.
This move was necessary because external risks spilled into integrated products. While the treasury stands at nearly $94 million, this allocation remains relatively small. Still, it introduces a new dynamic where protocol funds absorb external stress. Governance approval signals strong coordination, but it also subtly shifts expectations.
If similar interventions become routine, reserves could tighten over time. Users may increasingly expect protection beyond what the protocol originally designed. That could change how Lido manages risk going forward.
Lido limits liability while containing integration risk
The Kelp exploit exposed how external integrations can transmit risk into Lido’s ecosystem. Rather than expanding coverage broadly, the DAO proposes using its existing first-loss fund only for Kelp-related losses. The 1% rule remains unchanged, and no new capital is added.
This approach emerges because the core protocol itself was not directly affected. Yet user exposure still required a response. So Lido is balancing protection with restraint. The goal is to restore confidence without setting broad bailout expectations.
This shift signals that future risks may not receive similar support. If users accept this boundary, trust may stabilize. But uncertainty around coverage could influence participation and how people perceive risk in the protocol.