Lido is considering a measured intervention in the fallout from the Kelp exploit, offering to contribute staked Ether if a broader recovery plan comes together.
In a new proposal, Lido Labs said it may make 2,500 stETH available, worth roughly $5.8 million, to help address the rsETH backing shortfall created by the LayerZero exploit tied to Kelp. The contribution, however, would not be unconditional. Lido said the stETH would be made available only as part of a fully funded recovery package intended to close the deficit in full.
That distinction matters. Lido is not positioning this as a standalone rescue of a single protocol. Instead, it is framing the Kelp incident as a problem with wider second-order effects across integrated DeFi markets.
In the proposal, the team said the exploit created a “material rsETH backing shortfall” that has already led to pressure on market rates, elevated lending and borrowing stress, and the risk of forced unwinds for users exposed through vault structures and looping strategies.
That broader spillover is likely why Lido is even entertaining a contribution in the first place. When a liquid staking or restaking asset loses backing, the problem rarely stays neatly contained. It starts pushing on collateral assumptions, borrowing costs and leverage across multiple venues at once.
The structure Lido is suggesting is also fairly deliberate. By tying the stETH allocation to a fully funded package, the protocol is avoiding a scenario in which it plugs part of the hole while leaving the wider deficit unresolved.
That is a sensible guardrail. A partial recovery can stabilize sentiment for a moment, but it can also simply spread losses differently if the capital stack underneath remains incomplete.
Users who stake Ether through Lido receive stETH, a liquid token that represents their staked position. Offering part of that supply into an external recovery process is therefore not a trivial gesture. It is a sign that the Kelp exploit is now being treated as a broader ecosystem event rather than merely a protocol-specific failure.
For DeFi, that may be the more important point. The question is no longer just who was hacked. It is which protocols are willing to help contain the damage once the stress begins moving outward.
]]>

