Expand the CSMC Mandate to Cover Additional Penalty Cases
Proposes letting the Community Staking Module Committee use the existing General Delayed Penalty mechanism for validator slashing and other protocol-harming incidents, not only MEV stealing.
This Lido proposal asks voters to adopt an updated mandate for the Community Staking Module Committee (CSMC), which handles operational actions for both the 0x01 and 0x02 Community Staking Modules. Today the committee can apply the General Delayed Penalty mechanism only to MEV stealing. The proposal does not create a new penalty; it widens when the existing one may be used, to cover penalties tied to validator slashing and other incidents that may adversely affect the protocol. The background cites a slashing incident on March 12, 2026 involving six CSM validators, where penalties and missed rewards came to about 0.79 ETH: about 0.34 ETH was covered automatically by the operator bond and about 0.45 ETH was compensated voluntarily by the operator. The proposal says this showed the committee lacked an established way to address additional losses without relying on voluntary compensation. Node operators in both modules would be subject to the wider penalty cases; the stated beneficiary is the protocol and its stakers. The vote is a For/Against choice. Open questions in the text include how the additional cases are defined and applied in practice.
Free: this site, which you have to remember to check. Paid: every Monday an email lists the votes closing in the next 7 days, sorted by deadline, then the week's items in full.
Sample of the weekly email
Closing in the next 7 days 1. [dao] Proposal title - vote ends 2026-11-16 - one-line summary 2. [dao] Proposal title - vote ends 2026-11-18 - one-line summary The week in full [dao] Proposal title: full plain-English analysis and flags
10 USDC on Base = 31 days.
- Send 10 USDC on Base to
0xdbe64890cbC58304815A865F63151c205F2C88B2 - Email the transaction hash to saleforce@agentmail.to, which is this project's own inbox. Send it from the address that should receive the digest.
- Access starts when the payment is confirmed on-chain.