Proposal: Additions to the Lido ICS framework to streamline the SSV community NOs path to verification

Proposals
1

Summary

This proposal introduces new avenues to score points in the ICS framework, supporting SSV community node operators (NOs) to earn their Verified Operator (VO) and Identified Community Staker (ICS) status, and increasing net new verified SSV NOs participating in CSM.

Proposed additions to the ICS Framework:

  • Add a new score source: SSV pre-VO KYC to Proof of Humanity category [4 points]

  • Add a new score source: SSV High Signal score to Proof of Engagement [2 - 5 points]

Background and motivation

Becoming a VO in SSV Network requires 90 days of validator performance metrics above 98%. Permissionless community NOs in SSV Network generally find it hard to get a first validator allocated to them. Mainly because they don’t have 32 ETH to spin up their own validator, or don’t get validators allocated to them. VO status is a reputational signal that proves they are professional and reliable, and increases the chances of getting a validator allocated to them in SSV Network by a staker.

Therefore, the core bottleneck for new community operators is not only verification, but access to their first validator. Without performance history, it is difficult to become a trusted operator; but without access to a validator, it is difficult to build that history. This proposal aims to reduce that circular dependency by recognizing credible upstream verification and community engagement signals.

Goals

  • Streamline the process for SSV community NOs to earn VO + ICS status.

  • Grow the number of verified SSV community NOs participating in CSM and SSV Network.

  • Accelerate DVT adoption within Lido’s community operator set.

Pain Points Solutions
To earn SSV VO status NOs need to run a validator on mainnet. Pre-VOs join CSM and run their first mainnet validator with a smaller bond (2.4 ETH). And later, even lower bond costs after achieving ICS and onboarding to IDVTC.
Lower likelihood of community operators chosen to run validators in SSV Network without VO status. By getting their first mainnet validator on CSM, NOs can complete the VO program and get a reputation boost as a trusted NO in the SSV ecosystem.
Adoption of DVT in CSM. CSM becomes the gateway for SSV NOs to earn VO status.

The key changes are solely to the ICS framework score as mentioned above. The reasoning behind this is that both ICS and VO have a form of KYC for Proof of Humanity (SSV Verified Operator Committee uses Sumsub). The SSV Network VO program’s KYC/KYB stack is provided by the SSV Foundation, currently using SumSub, the number one provider in the space, as its primary service provider.

If the score is added an SSV NO can start their journey in the SSV VO program, join CSM, and if they meet requirements at the end of 60 days (SSV Operator committee will change monitoring period to 60 days for this cohort as opposed to 90d mentioned above) they can have both ICS and VO status; granted Proof of Experience and Engagement (reason for adding High Signal score for SSV) requirements are met.

Potential path to ICS + VO status

  1. Register for the SSV VO program to get pre-VO status for doing KYC [4 points] + X account [1 point].

  2. CSM mainnet participant [6 points].

  3. Complete 2 months’ performance metrics to get VO status [remaining 2 points for PoE].

  4. High signal score of 30+ in Lido/SSV Discord [2 points].

PoExperience (8) + PoEngagement (2) + PoHumanity(5) = 15 score for ICS

With this proposal, we want to formalize a path for new and existing (unverified) SSV community NOs to earn ICS and VO status by participating in CSM and, later on, potentially support the bootstrapping of the IDVTC (more on the potential synergy is described at the end of the proposal).

This new path is specifically focused on solo/community stakers, barring enterprise participants and professional organizations.

Additional alignment for SSV community operators

  • SSV Staking on mainnet went live in Q2 2026.

  • The SSV network switched from SSV to ETH operator fees for all new clusters (reduced operational friction).

  • SSV NOs in Lido earn SSV token rewards as part of the Incentivized Mainnet Program.

  • SSV distributed to SSV NOs can be staked to earn additional ETH rewards.

Synergies with the IDVTC

With the recently proposed Identified DVT Cluster (IDVTC), SSV NOs that follow this path will be eligible to earn this credential when it goes live. This sets up the playing field for SSV community NOs to run validators in dedicated clusters as per the IDVTC proposal.

Perceived benefits for Lido, SSV, and community NOs:

  • Net new community NOs in SSV Network and Lido.

  • Backstop IDVTCs leading up to launch.

  • Increase DVT adoption in the CSM module.

  • Higher returns and lower barriers for SSV community VOs that run validators in CSM using DVT.

6 Likes
2

Hey @GBeast, glad to see you here and thank you for the proposal!

I do support the proposal because it looks like a nice synergy that we can achieve by making slight adjustments to both of our mechanisms (VO and ICS).

One thing I want to point out:

The “CSM mainnet participant” score can be obtained by individuals for solo operators (not DVT) – it means we are not giving the score to each cluster participant. ICS was designed in a way that complexity related to identifying cluster participants is pushed to the DVT provider side: that’s why ICS has SSV VO and Obol Techne as separate sources of experience on top of just CSM participation.

That’s said, I suggest we adjust you proposal slightly:

The flow of receiving SSV VO + ICS

  • Join CSM, validate as a cluster on mainnet for 60 days (or testnet first for those who are new to validaton, this is what is usually recommended in any case to test the cluster setup, but specifically for newcomers)
  • Get SSV VO
  • Get ICS

ICS in this case can be received by providing following proofs (just minimum example):

  • Proof-of-Humanity: SSV VO [3 points] + X [1 point];
  • Proof-of-Experience: SSV VO [7 points]
  • Proof-of-Engagement: SSV High Signal [4 points]

So, this way, the changes I suggest to make to your initial proposal @GBeast:

  1. Instead of introducing the SSV pre-VO status, we just include the full SSV VO as a source for Proof-of-Humanity as the participants anyway will have to receive SSV VO first to get score for the Proof-of-Experience. This helps us to omit one redundant step
  2. Change 4 points for SSV VO in the PoH to 3 points. PoH requires minimum of 4, and I propose SSV VO would give a bit less score than required, so that applicants will have to provide something else (X, Discord, Human Passport, Circles) on top. That would be my personal recommendation for the CSMC to consider as for me having all 3 proofs “obtainable” from SSV ecosystem doesn’t sound good enough, especially given that SSV VO would serve as a score source for both PoH and PoEx.

Long story short, my suggestion is to:

  • Add SSV High Signal as a source for Proof-of-Engagement [2-5 points]
  • Add SSV VO as a source for Proof-of-Humanity [3 points]

Cheers!

3 Likes
3

Thanks for the feedback, @Aleksandra_G. I think these are good suggestions.

The only thing I might clarify is about the testnet. We definitely encourage people to run the SSV testnet before moving to mainnet, but we only count mainnet performance towards earning the Verified Operator status. So they have to be operating a validator share on mainnet for 60 days to earn the designation.

Otherwise, we can accept you changes and move forward.

2 Likes
4

Thanks for putting this forward — speaking from the perspective of an

existing SSV operator on a SDVTM cluster, both elements of this proposal

address real friction that I and other community operators see in practice.

A few operator-side observations that may be useful for the framing:

1. **The chicken-and-egg you describe is real.** I run operator 1039

(Lido x SSV Cohort 2) and have ~17 months of mainnet operational history,

but the existing 90-day SSV VO program effectively requires sustained

non-Lido validator selection in parallel — which is hard for any operator

whose first mainnet exposure was through SDVTM. The proposed pre-VO /

SSV-VO PoH path closes that gap cleanly.

2. **On Aleksandra_G’s modification** (use full SSV VO at 3 points instead

of pre-VO at 4): I agree with the intent — keeping ICS as a multi-source

credential rather than a single-pillar pass — but I’d flag one practical

point. For operators currently in the SDVTM wind-down, full VO status is

exactly the gating credential they cannot easily obtain in the available

timeframe (cluster winds down July 1; the standard 90-day VO window doesn’t

fit cleanly). If “full VO” is the requirement, an explicit transition

accommodation (e.g. SSV Operator Committee discretion for SDVTM-era operators

based on documented Lido performance history) would make the path usable

for the very cohort the proposal is designed to help.

3. **High Signal score as PoE** is a clean signal — easy to verify, hard to

game. Strong support for the 2-5 graduated scale.

If/when this lands as a Snapshot, happy to be in the first wave of test

applications — I have the SDVTM track record, ICS application already in queue,

and the infrastructure ready to continue.

5

Hi everyone,

I fully support this proposal. It addresses a major bottleneck for permissionless community node operators (NOs) by breaking the circular dependency between needing a validator to build a performance history and needing a history to attract a validator.

Here are the key aspects that make this a strong addition to the ecosystem:

  • Lowering Barriers: Allowing pre-VOs to join CSM with a smaller bond (2.4 ETH) enables community operators to run their first mainnet validator and complete the VO program, gaining a crucial reputation boost.

  • Streamlined ICS + VO Path: Leveraging the existing Sumsub KYC stack for Proof of Humanity (4 points) alongside the new High Signal score tiers for Proof of Engagement (2–5 points) creates a clear, formalized 15-point track for solo and community stakers within 60 days.

  • Ecosystem Alignment: This actively accelerates DVT adoption in the CSM module, builds a solid backstop for the upcoming Identified DVT Clusters (IDVTC), and integrates well with the current Incentivized Mainnet Program rewards.

This is a highly practical way to grow the number of verified community NOs across both Lido and SSV Network while strictly focusing on solo/community stakers. Looking forward to seeing this implemented.

2 Likes
6

Thanks for the proposal @GBeast!

Brought this to the CSM Committee and there were no objections to:

  1. Adding SSV Verified Operators to the Proof of Humanity category with 3 points
  2. Adding the SSV High Signal to the Proof of Engagement category with 2 to 5 points

We’re reviewing the necessary changes, but for now it looks like this could be ready for the next round of ICS on June 8. I will report back in if any issues arise.

This is very positive for DVT adoption in the CSM! I’m very happy to see this happening.

6 Likes