Lido contributors have prepared the initial version of the ICS list to be used in CSM v2 deployment - https://ipfs.io/ipfs/bafkreia462ih3h45hpl7jdam5fmdewkvwcxbdcottaf6xjcemwmmwm67cy (will soon be available in GitHub repo - community-staking-module/artifacts/mainnet/ics/addresses.json at develop · lidofinance/community-staking-module · GitHub)
The list is compiled using on-chain and off-chain data as of July 4, 2025, using the methodology described in Community Staking Module - #139 by dgusakov
If current CSM EA Node Operators think that their address was not included in the list due to a mistake, they can submit an appeal in this thread using the following template:
I’m the owner of CSM NO #XXX <link to the verified signature on etherscan from manager or reward address>, and I want to appeal the decision to not include my address in the initial ICS list for CSM v2. I confirm that:
- CSM NO #XXX is the only Node Operator owned/controlled/managed by me as a person/entity and I do not own/control/manage other NOs in CSM.
OR
As a person/entity, I own/control/manage the following Node Operators in CSM: #XXX, #YYY, #ZZZ, … none of which were included in the list. I confirm that CSM NO #XXX should be considered my main Node Operator in the ICS consideration process. - I run all software myself (CL+EL nodes, and validator client), and I am not using “Validators as a Service” (Allnodes, Stakely, Launchnodes, a friend/relative etc.) for the operation of these validators.
- As a person/entity, I do not act as a professional Node Operator in Ethereum or other ecosystem staking.
- CSM NO #XXX has non-zero active and/or depositable validator keys in CSM as of July 4, 2025.
- CSM NO #XXX does not have validators with performance below the performance threshold in the Performance Oracle reports for both May and June.