KVORUM
lidoSource: Snapshot · #0x5629f9b201f32dbd5780f7e2e5601eed7504cdb7919b622a7ef039261d3c671a

Authorize Lido EarnETH Loss Coverage Below 1% Threshold For The Kelp Incident

succeededMay 6, 2026, 08:30 AM UTCsignaling · non-bindingby8E0x8ee5…fbc1View on Snapshot ↗

01Summary

AISummary by Kvorum

An AI summary is not generated yet. Read the description →

02Description

504 words

TL;DR

Lido Earn contributors request DAO authorization to use the Lido Earn first-loss mechanism to cover Kelp-related losses incurred by Lido EarnETH users, even if such losses are below the previously approved 1% threshold. This is a one-off, Kelp-specific exception intended to support Lido Earn's continuity and user confidence.

Motivation

The April 2026 Kelp rsETH incident (LayerZero exploit) resulted in a material rsETH backing shortfall and triggered broader cross-protocol dislocation across DeFi. In response, a coordinated initiative — DeFi United — has been established to cover the rsETH deficit. However, even in the case of full coverage, Lido EarnETH vault users remain exposed to residual losses arising from elevated borrowing costs in leveraged positions, estimated at approximately 400–600 ETH, depending on the time required for the Kelp protocol to resume normal operations.

Lido DAO previously approved a first-loss mechanism for Lido Earn with a 1% loss threshold, which may limit its applicability to Kelp-related losses. However, given the irregular nature of the Kelp incident and Lido DAO’s commitment to supporting Lido Earn users, covering residual losses even if they fall below the 1% threshold would not only preserve user confidence but also reinforce Lido Earn’s competitive position and support its medium-term growth potential as market conditions normalize.

Proposal

It is proposed to authorize the use of the existing Lido Earn first-loss mechanism to cover losses related to the Kelp incident, irrespective of the 1% threshold.

This authorization is strictly limited to actual residual Kelp-related losses borne by the EarnETH vault users. It constitutes a one-off, exceptional use of the first-loss mechanism and does not modify the general ≥1% threshold rule. This authorization is intended to serve as a backstop to be used only to the extent that alternative loss coverage (e.g., from vault curators) is insufficient. The proposed coverage does not introduce any new treasury allocation, subsidize yield, offset foregone annual percentage yield (APY), smooth returns, or provide any profit support once normal vault operations resume.

This proposal is time-critical given the expected timeline of the broader rsETH recovery following the Kelp incident, which may conclude sooner than the standard governance cycle. For this reason, the Snapshot vote is proposed on an accelerated timeline. If approved, it will allow Lido Earn to act without delay after the broader incident is resolved.

If the DAO decision is delayed, Lido Earn may be unable to act even after the incident is resolved. This could unnecessarily extend loss coverage and withdrawal uncertainty for EarnETH users, and increase operational, legal, reputational, and commercial risks, while weakening confidence in Lido Earn.

Next Steps

If the proposal is approved:

  • Lido Earn will be authorized to apply the first-loss mechanism to cover actual residual Kelp-related losses for EarnETH users, even if those losses are below 1%.
  • Lido Earn contributors will publish a full post-mortem covering the incident, the vault’s exposure, and the response. Concrete changes to the risk framework, operating approach, and related controls will be proposed to reduce the likelihood of similar situations recurring.

03Mismatch analysis

AIMismatch analysis by Kvorum

A calldata-vs-description analysis is not generated yet. Review the decoded actions →

04Actions

0 total

This proposal carries no on-chain actions.

05Tally

Summed from votes

Voters60
VP participating0
Outcome (current)For
Current support94.8%

06Voters

60 total
Filter:
VoterChoice% of totalRationale
4A0x4af8…6a0bFor015.64%—6mo ago
420x42e6…3fb0For013.63%—6mo ago
B60xb664…f890For010.87%—6mo ago
A40xa418…b737For010.46%—6mo ago
810x8172…922eFor09.33%—6mo ago
1F0x1f76…5ed6For09.24%—6mo ago
7E0x7ee0…bb6cFor08.72%—6mo ago
LIlido.banteg.eth0x55bc…f0faFor06.04%—6mo ago
310x3133…5c00Against05.25%—6mo ago
450x45bc…fd99For03.55%—6mo ago
6D0x6d8d…0cccFor02.91%—6mo ago
6F0x6f9b…8a1dFor02.75%—6mo ago
E80xe80e…28e8For00.40%—6mo ago
9C0x9cbc…7519For00.28%—6mo ago
3D0x3ddc…05b0For00.26%—6mo ago
8C0x8c3a…09a6For00.21%—6mo ago
060x06a9…bba0For00.20%—6mo ago
EF0xef3a…dce1For00.07%—6mo ago
3D0x3d63…4afcFor00.07%—6mo ago
B90xb933…8dd1For00.05%—6mo ago
7A0x7a59…8e22For00.04%—6mo ago
350x352c…8248For00.00%—6mo ago
F80xf804…9d2eFor00.00%—6mo ago
3D0x3d5a…b97fFor00.00%—6mo ago
050x0579…ca09For00.00%—6mo ago
220x2206…64fbFor00.00%—6mo ago
3B0x3ba6…0cefFor00.00%—6mo ago
F10xf1cc…ac93For00.00%—6mo ago
B10xb1f8…4250For00.00%—6mo ago
380x3805…0636For00.00%—6mo ago
F60xf6dc…4e03For00.00%—6mo ago
0A0x0ab1…7c6aFor00.00%—6mo ago
250x257b…9830For00.00%—6mo ago
BF0xbff4…030fFor00.00%—6mo ago
7B0x7b27…a893For00.00%—6mo ago
170x1729…b879For00.00%—6mo ago
0D0x0df5…105dAgainst00.00%—6mo ago
870x87c7…7960For00.00%—6mo ago
0F0x0f53…66d1Against00.00%—6mo ago
4D0x4d32…bbfaFor00.00%—6mo ago
2F0x2f2f…f78aFor00.00%—6mo ago
1F0x1f3d…0591For00.00%—6mo ago
B30xb3bf…6ce4For00.00%—6mo ago
FB0xfbd0…f886For00.00%—6mo ago
650x659f…dadcFor00.00%—6mo ago
AF0xaf90…7b3bFor00.00%—6mo ago
010x0151…c3b9For00.00%—6mo ago
BF0xbfd1…4f66For00.00%—6mo ago
CE0xce57…70f0For00.00%—6mo ago
C50xc554…7759For00.00%—6mo ago
Showing 50

07Forum

No forum thread is confidently linked to this proposal.

08Similar proposals

AI · embeddings

No semantically similar proposals found yet.