Explore Hub: Staking

Lido ICS SSV path proposal is the primary keyword for this Radar update. A May 13 Lido governance forum proposal suggests additions to the Identified Community Stakers framework to streamline the SSV community node-operator path.

Radar is covering it as staking ecosystem design. The proposal is about verification, community operator access and distributed validator technology adoption rather than a token trade.

What Happened

The proposal would add SSV pre-verified-operator KYC as a Proof of Humanity score source and SSV High Signal score as a Proof of Engagement source. It says the path is focused on solo and community stakers, excluding enterprise participants and professional organizations.

The post frames the problem as a circular dependency: community node operators need validator performance history to become verified, but need access to validators to build that history.

Why It Matters

This matters because operator onboarding is a decentralization and reliability issue for liquid staking. A clearer path for community operators can broaden participation, but it also adds governance responsibility around scoring and sybil resistance.

For protocol researchers, the signal is how Lido balances access, identity proofs, performance data and DVT adoption without making the framework too easy to game.

What To Watch Next

Watch community feedback, score-source revisions and whether Lido moves the addition toward a formal governance action. The strongest version would explain safeguards, appeals and update cadence.

Also watch SSV operator performance requirements and whether the path creates measurable net-new community operators in CSM rather than just relabeling existing capacity.

Decision Check

For Radar, the control point is Staking ecosystem angle on Lido ICS framework changes, SSV community node-operator verification and DVT adoption.. The update should be tracked as protocol discovery only if the source path remains visible, operators or governance actors provide follow-through, and users can verify the operational change instead of relying on a headline.

Continue this cluster

Continue this cluster with May 16 protocol, chain and ecosystem updates that show how live infrastructure is changing.