Updated CSMC Mandate
Background
The Community Staking Module Committee (CSMC) is entrusted with a set of operational responsibilities for CSM that require frequent usage or a rapid response. These include reporting MEV stealing penalties, canceling such reports where appropriate, initiating EasyTrack motions to settle MEV stealing penalties, updating bond curves for Node Operators (including adding operators to and removing them from the ICS and IDVTC lists) adjusting the module’s stake share limits via EasyTrack motions, and pausing module contracts via CircuitBreaker in case of emergency.
With the introduction of CSM 0x02, the CSMC was further authorized to oversee the new module under largely the same scope of responsibilities, with the addition of rolling back the top-up queue in the event that invalid top-up information is delivered by the Depositor Bot.
It is worth noting that the mechanism historically referred to as the MEV stealing penalty and the mechanism introduced with CSM v3 as the General Delayed Penalty are one and the same. Going forward, this mechanism will be referred to uniformly as the General Delayed Penalty for both modules.
What This Proposal Changes
Since the CSMC now oversees a substantially larger portion of the Lido protocol (two modules whose combined stake share limit is expected to grow over time) it has become necessary to update and expand the Committee’s mandate regarding Node Operator penalties. As of today, the CSMC is authorized to lock a Node Operator’s bond only in cases of MEV stealing.
The change proposed in this post is not the introduction of a new mechanism. It is the expansion of the set of cases in which the CSMC may apply the existing General Delayed Penalty mechanism, for both 0x01 and 0x02 CSM. Specifically, the CSMC would be authorized to apply the mechanism in the following cases:
- MEV stealing — as before, covering violations of the Lido Block Proposer Rewards Standard Node Operator Protocol (SNOP);
- Additional penalties associated with slashings [new] — compensating for missed rewards caused by slashing events, beyond the amounts automatically captured by on-chain mechanisms;
- Other protective cases [new] — incidents that cause, or may reasonably be expected to cause, penalties, missed rewards, APR dilution, withdrawal delays, reward leakage, key compromise risk, slashing risk, operational burden, or reputational harm, where the CSMC determines that reporting/applying a General Delayed Penalty or another appropriate measure is necessary or appropriate to protect the protocol.
Motivating Example
The following incident illustrates the need for this expansion. On March 12, 2026, a slashing incident occurred in CSM affecting six validators. The total penalty and missed rewards as of the end of the incident amounted to 0.7973122 ETH, of which:
- 0.3459189 ETH was automatically covered from the Node Operator’s bond by the CSM contracts, and
- 0.4513933 ETH was voluntarily compensated by the Node Operator.
Notably, the Committee was fortunate in this instance: it happened to possess the operator’s contact information and was able to reach out directly, and the operator voluntarily compensated the remaining losses. Had either condition not held, the protocol would have had no recourse for the uncompensated portion. This outcome should not depend on luck or goodwill, and under the expanded mandate, it would not.
The Full Updated Mandate
Upon approval of this proposal, the full mandate of the CSMC shall be as follows:
General Delayed Penalty management (0x01 and 0x02 CSM):
- Report facts warranting a General Delayed Penalty committed by Node Operators;
- Cancel a reported General Delayed Penalty where appropriate;
- Initiate EasyTrack motions to settle confirmed General Delayed Penalties.
The General Delayed Penalty mechanism may be applied in the following cases:
- MEV stealing — EL rewards transferred in violation of the Lido Block Proposer Rewards SNOP, whether fully or partially, to any address other than the Lido Execution Layer Rewards Vault;
- Operator slashing — additional penalties to compensate for missed rewards caused by slashing events;
- Other incidents — incidents causing or reasonably expected to cause penalties, missed rewards, APR dilution, withdrawal delays, reward leakage, key compromise risk, slashing risk, operational burden, or reputational harm, where the Committee deems a General Delayed Penalty necessary or appropriate to protect the protocol.
Operator type management (0x01 and 0x02 CSM):
- Set the bond curve for a particular Node Operator or reset it to the default (
SET_BOND_CURVE_ROLE, RESET_BOND_CURVE_ROLE);
- Add operators to, and remove them from, the ICS and IDVTC lists.
- Maintain ICS and IDVTC frameworks as specified in respective posts.
- Adjusting the ICS framework, scoring methodology, scores, and scoring sources.
- Adjusting IDVTC requirements and eligibility criteria.
- Pausing or stopping application intake and list updates under the respective frameworks.
Module parameters (0x01 and 0x02 CSM):
- Propose adjustments to the CSM stake share limits via EasyTrack motions (via the corresponding
UpdateStakingModuleShareLimits factories, within the bounds approved by governance)
- Set key-removal charges and delayed-penalty additional fines
Module operations (0x02 CSM):
- Roll back the top-up queue in the event of invalid top-up information being delivered by the Depositor Bot (
REWIND_TOP_UP_QUEUE_ROLE).
Emergency response (0x01 and 0x02 CSM):
- Report slashed validators as withdrawn via EasyTrack motions
- Pause the module in case of emergency: both 0x01 CSM and 0x02 CSM via the CircuitBreaker (as designated pauser).
All of the functions above may require frequent usage or rapid reaction, and it is reasonable for the Committee’s multi-sig to hold them in order to support smooth operations of both modules.
Reporting
Reporting remains the same: the committee members must report on actions taken every quarter using the Lido research forum.
CSM Node Operators can use a special section on the Lido research forum to contact the committee with their questions and complaints.