# Expand the CSMC Mandate to Cover Additional Penalty Cases

- Space: [Lido](https://snapshot.box/s:lido-snapshot.eth.md)
- Author: 0x0A4d7032914271D95aB51DC9a7E708beAD15e31c
- State: Active
- Voting type: Single choice
- Start: 2026-11-16 16:00 UTC
- End: 2026-11-23 16:00 UTC
- Votes: 36
- Discussion: https://research.lido.fi/t/community-staking-module-committee/8333/41
- Open in Snapshot: https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x2abd5c6c05b74a847f64967ca553f55a96bfe6ce01a34e6bd7887b98538e415c

## Results

- For: 53,838,932.35 voting power, 92.9%
- Against: 4,125,000 voting power, 7.1%

## Proposal

### Summary

This proposal seeks approval to adopt an updated mandate for [the Community Staking Module Committee (CSMC)](https://docs.lido.fi/multisigs/committees#29-community-staking-module-committee), which oversees [operational responsibilities](https://research.lido.fi/t/community-staking-module-committee/8333) for both 0x01 and 0x02 [Community Staking Modules (CSM).](https://docs.lido.fi/staking-modules/contracts/CSModule) 

The principal change is to extend the circumstances in which the CSMC may apply the existing General Delayed Penalty mechanism beyond MEV stealing, to include additional penalties associated with validator slashing and other incidents that may adversely affect the protocol. By doing so, the proposal does not introduce a new penalty mechanism, but rather expands the authorized uses of the existing mechanism.

### Background

The CSMC was established to handle operational actions that may require frequent execution or rapid response, including MEV stealing penalty management, Node Operator bond curve adjustments, module parameter changes, and emergency interventions. With [the introduction of 0x02 CSM](https://research.lido.fi/t/0x02-csm-landscape/11697), the Committee's responsibilities were extended to the new module. However, its mandate regarding Node Operator penalties remained limited to MEV stealing. 

[A slashing incident on March 12, 2026](https://research.lido.fi/t/incident-minor-csm-operator-slashing/11281), involving six CSM validators, demonstrated the limitations of this mandate. The total penalties and missed rewards amounted to ≈0.79 ETH, of which ≈0.34 ETH was automatically covered by the Node Operator's bond and ≈0.45 ETH was voluntarily compensated by the operator. The incident highlighted the need for the Committee to have an established mechanism for addressing additional losses without relying on voluntary compensation.

### What Changes Compared to the Existing Mandate

The proposal authorizes the CSMC to apply the existing General Delayed Penalty mechanism to both 0x01 and 0x02 CSM in the following circumstances:

1. **MEV stealing (existing)**: Execution Layer rewards transferred, in full or in part, to an address other than the Lido Execution Layer Rewards Vault in violation of the Lido Block Proposer Rewards Standard Node Operator Protocol (SNOP).
2. **Operator slashing (NEW):** Additional penalties to compensate for missed rewards resulting from slashing events, beyond amounts automatically covered through on-chain mechanisms.
3. **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 a General Delayed Penalty is necessary or appropriate to protect the protocol.

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.

### Full Committee Responsibilities

The CSMC's mandate encompasses the following responsibilities:

1. **General Delayed Penalty management (0x01 and 0x02 CSM)**
    1. Report facts warranting a General Delayed Penalty committed by Node Operators.
    2. Cancel reported General Delayed Penalties where appropriate.
    3. Initiate Easy Track motions to settle confirmed General Delayed Penalties.
2. **Operator type and bond curve management (0x01 and 0x02 CSM)**
    1. Set or reset a Node Operator's bond curve through the applicable `SET_BOND_CURVE_ROLE` and `RESET_BOND_CURVE_ROLE` permissions.
    2. Add Node Operators to, or remove them from, the ICS and IDVTC lists, as applicable.
    3. Maintain [ICS](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xc3f92bcdf8926cfa7528ca6a979c0fdce1e4d0cfaaa72dd6410a76a2e1e55766) and [IDVTC](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x1d416954538fb9b82aae05daca1be29f7b20d5f9fac61bd2eb9da1f5901a3867) frameworks as specified in respective posts, including:
        1. Adjusting the ICS framework, scoring methodology, scores, and scoring sources.
        2. Adjusting IDVTC requirements and eligibility criteria.
        3. Pausing or stopping application intake and list updates under the respective frameworks.
3. **Module parameters (0x01 and 0x02 CSM)**
    1. Propose adjustments to CSM stake share limits through the corresponding `UpdateStakingModuleShareLimits` Easy Track factories, within governance-approved bounds.
    2. Set key-removal charges and delayed-penalty additional fines.
4. **Module operations (0x02 CSM)**
    1. Roll back the top-up queue when invalid top-up information is delivered by the Depositor Bot, using `REWIND_TOP_UP_QUEUE_ROLE`.
5. **Emergency response (0x01 and 0x02 CSM)**
    1. Report slashed validators as withdrawn through Easy Track motions.
    2. Pause either module in an emergency through [CircuitBreaker](https://docs.lido.fi/deployed-contracts/#circuit-breaker), acting as the designated pauser.

### Reporting and Oversight

The CSMC shall continue to operate under the following reporting and oversight requirements:

- Committee members must report on actions taken every quarter through the [Lido Research forum](https://research.lido.fi/t/community-staking-module-committee/8333/37).
- CSM Node Operators may contact the Committee with questions or complaints through the [designated Lido Research forum section](https://research.lido.fi/c/csm-support/21).

### Next Steps

If the vote concludes positively: 
1. The CSMC mandate will be expanded to cover additional General Delayed Penalty cases for both 0x01 and 0x02 CSM: operator slashing and broader protocol protection cases.
2. The updated mandate described in this proposal will be adopted as the consolidated statement of the CSMC's responsibilities, superseding previous descriptions of its mandate.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

