Lido stays on the Radar because the latest Kelp-related proposal is not about price reaction. It is about whether a protocol-level protection rule should bend for a very specific incident.
That makes this a governance-policy story. Exception handling is often where protocol values become operational, especially when the usual threshold logic is too blunt for the actual loss path.
What Happened
A Lido research proposal published on April 29, 2026 seeks authorization for loss coverage below the usual 1% threshold for the Kelp incident as a one-time exception. The proposal argues that if the coordinated recovery fills the rsETH gap, the remaining realized loss could land below that standard trigger level.
Lido's earlier EarnETH policy material says a first-loss protection trigger normally activates at or above a 1% vault-loss threshold. The new proposal frames this as an incident-specific exception rather than a rewrite of the standing rule.
Why It Matters
For Radar, the signal is that protocol protections are now being tested in the gray area between a clean rule and a messy real-world incident. That matters because exception design can change how users interpret future promises about protection, recovery and governance discretion.
The proposal is also useful because it makes the trade-off explicit. A strict threshold may be internally consistent while still missing the user-outcome goal in a time-sensitive recovery. A one-time exception can improve remediation while also creating precedent risk.
Researchers should therefore read this as more than a Kelp update. It is a live example of how incident remediation pressure meets formal protocol policy.
What To Watch Next
Watch whether the discussion stays tightly scoped to the Kelp incident or expands into a broader debate about how flexible loss-coverage rules should ever be.
The next useful checkpoint is whether delegates articulate what makes this exception unique enough to avoid becoming an informal template for future cases.
This stays on Radar because governance exceptions often reveal more about protocol operating philosophy than routine rules ever do.
Continue this cluster
Protocol risk surfaces get easier to judge when incident response, policy thresholds and governance exceptions are reviewed together instead of one headline at a time.
