GM!
Here is a quarterly update from the CSM multisig committee for Q2 2025. During Q2 2025, no incidents were identified that resulted in reported MEV stealing by the committee.
There were 2 incidents that led to a block being proposed with a null fee recipient.
Node Operator 91 self-reported an issue related to a client. The block reward was compensated directly to the Lido EL Rewards Vault.
Node Operator 57 self-reported a misconfiguration issue and compensated the block reward directly to the Lido EL Rewards Vault.
In both cases, the committee members agreed that there was no malicious intent and no additional fee was necessary.
3 Likes
Iām happy to see the MEV Stealing prevention system working! This report is a clear indicator of that. No reported penalties and just two unfortunate situations with the config, followed by immediate compensation. Robust!
3 Likes
GM!
Here is a quarterly update from the CSM multisig committee. There were no transactions in Q3 2025, so the update covers Q4 2025.
No incidents resulting in reporting MEV stealing were identified by the committee. That said, the committee has an additional responsibility since CSM v2 that was not outlined in the original post: adopting the Community Stakers Identification Framework and initiating an update of the ICS trees on-chain.
Following the completion of 2 ICS rounds in Q4 2025, the following EasyTrack motions have been started by the committee:
All motions were executed and the ICS data was updated in CSM contracts on mainnet.
3 Likes