Rotate Lido on Ethereum Oracle Set member Kyber Network for Caliber, as per Snapshot decision. Items 1.1–1.6.
Confirms the previous Snapshot option to allow Caliber to succeed Kyber. Yes.
Increase CSM stake share limit from 2% to 3%.
Previous strong support on Snapshot. We need to increase the stake limit to see growth in the CSM. The charge reduction seems sensible in current market conditions. Yes.
Enable a grace period for CSM Node Operators by setting keyRemovalCharge = 0. Proposed on the Forum. Items 1.8-1.10.
This seems sensible and is time sensitive to July 2025 since CSM v2 goes live in August 2025. Yes.
Introduce a simplified CSVerifier for CSM. Proposed on the forum. Items 1.11, 1.12. Audit & deployment verification by MixBytes.
Having read the Conclusion in the MixBytes report which states no critical/high issues I am satisfied this will go smoothly. As a small note, it may make sense if these reports include a short Delegate summary or one is extracted, since we are essentially assessing the high level concerns. Yes.
Update the reward address and name for Node Operator ID 2 P2P.ORG - P2P Validator. Requested on the forum. Items 1.13, 1.14.
A functional change. Yes.
Switch off Easy Track environment for PML, ATC, RCC entities, deprecated after Snapshot-approved transition to Lido Labs and Lido Ecosystem BORG Foundations. Items 2–7.
An administrative change to enable the BORG transitions. Yes.
Snapshot votes
#### Triggerable Withdrawals Framework in the Lido Protocol #
Putting EIP-7002 to work in a very useful fashion. The VEB mechanism operates to my eye to expand the range of permissionlessness in the protocol, which is crucial. It reduces dependency on NO via the CL and allows parties to withdraw in a more autonomous fashion.
Easy Track Factories for Curated and sDVT to aid in exit requests seems necessary.
The TW limits seem sensible and well reasoned out For.
I really like the idea of identifying community stakers and giving them benefits, but the Community Stakers Identification Framework stands out to me as quite detailed. I wonder if it is both onerous on those who manage it and those who try to adhere to it to join the CSM. I would just suggest that there could be loosening of some requirements here and still effectiveness. I am generally of the view that in our industry we should try and minimise demands on users, even quite specialised ones, where possible. This is a general tendency I see in anti-Sybil resistance, where we become a little over-zealous to stop bad guys by making good guys do quite a lot of extra work.
The new types, the increase and the MEV budget all seem sensible.
For.