# Community Staking Module Committee **URL:** \ **Category:** Proposals\ **Created:** [September 10, 2024, 10:15am UTC](https://research.lido.fi/t/community-staking-module-committee/8333 "2024-09-10T10:15:21Z")\ **Posts on this page:** 1\ **Showing post:** 32
**Author:** ![dgusakov](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/dgusakov/32/1238_2.png) [@dgusakov](https://research.lido.fi/u/dgusakov)\ **Post date:** [July 13, 2026, 1:47pm UTC](https://research.lido.fi/t/community-staking-module-committee/8333/32 "2026-07-13T13:47:28Z")
Thanks for the proposal, @JulianCross! The case above (that you refer to as a bottleneck) is a one-off case related to [Proposal: Wind Down the Simple DVT Module Regular Clusters](https://research.lido.fi/t/proposal-wind-down-the-simple-dvt-module-regular-clusters/11571). Other ICS assessments are done automatically based on the on-chain data and other public information. Anyone can verify the assessment results using scripts - [staking-modules/ics\_assessment at develop · lidofinance/staking-modules · GitHub](https://github.com/lidofinance/staking-modules/tree/develop/ics_assessment) that are updated after each assessment round to include the latest data. Hence, I see no need for additional automation here. It is also worth noting that the points you mentioned (slashing conditions and other stuff) are not related or not directly related to the ICS Framework - [Identified Community Stakers Framework](https://operatorportal.lido.fi/modules/community-staking-module/ics). --- _[View the full topic](https://research.lido.fi/t/community-staking-module-committee/8333)._