MARCH VOTINGS REPORT 
Lido governance in March 2025 addressed critical operational advancements. During the first spring month, in total there were 20 governance votings across all platforms:
| Voting platform | # of votings |
|---|---|
| On-chain (prev. Aragon) | 1 |
| Snapshot | 7 |
| Easy Track | 12 |
Take a quick look at the dashboard below or check a detailed report below 
I took part in all on-chain and Snapshot votings. Please see a breakdown with the voting name, my vote and a short reasoning, as well as a short summary of what the vote was about:
ON-CHAIN
Vote #184
Vote: Yes
Voting summary
- About: This is aimed to implement on-chain:
- Extended On-Chain voting duration (items 1-17) following approved on Snapshot main phase change: 48h → 72h and objection phase: 24h → 48h. To align with these changes, GateSeal (pausing the WithdrawalQueue and ValidatorExitBusOracle) and CSM GateSeal (pausing the CSModule, CSAccounting, and CSFeeOracle) will be updated with the same configuration. Statemind.io audited the initial Factory and Blueprint and verified that the updated GateSeal contracts match the Blueprint and have the correct parameters.
- Deploy Easy Track Factories for Lido Ecosystem with security limit $5m per quarter and Lido Labs BORG Foundations with security limit $18m per quarter to streamline operational funding (items 18-19). Also approved previously via Snapshot.
- Voting platform: On-chain Lido DAO Voting UI
- Reasoning: Both changes were approved earlier via Snapshot and audited to be added to the mainnet.
SNAPSHOT
Lido DAO Ops Multisigs Policy 2.0
Vote: Adopt multisig policy 2.0
Voting summary
- About: This proposal builds on the foundational principles set in the Lido DAO Ops Multisigs Policy while adapting to evolving operational needs. The goal is to optimize multisig governance for scalability, enhance security measures, and ensure a clear framework that aligns with the fast-moving nature of Web3 governance.
- Voting platform: Snapshot
- Reasoning: Support, as a new version polishes the existing Lido DAO Ops Multisigs Policy, introduced in 2023, and reflects changes and evolving contributors’ operational needs.
SSV Lido Module Proposal
Vote: Approve
Voting summary
- About: Clusterform (SSV Labs subsidiary) proposes integrating a new module SSV Lido Module (SSVLM) into the Lido protocol Staking Router. Currently there is no new module ready to be deployed to the mainnet, this Snapshot is to proposed the development of the module and its deployment on the testnet. If supported, testnet is targeted for Q2 2025.
If the testnet run results pass the threshold and codebase audit is fine, there will be another Snapshot vote, which will include the technical details and parameters, followed by a final on-chain vote aiming to integrate the module into the Lido on Ethereum protocol. - Voting platform: Snapshot
- Reasoning: I see three major benefits this new module introduction will bring to Lido protocol: (a) supporting 2025 approved goal “Establish an Open Market for Validators” and allowing builders to create new ; (b) a scalable and decentralized way to expand its operator set; (c) growing DVT utilization, as an addition to the existing SimpleDVT module.
MEV-Boost Relay Allowed List management via Easy Track
Vote: For
Voting summary
- About: It is proposed to adopt three new Easy Track EVM script factories for the management of the MEV-Boost Relay Allowed List with the Relay Maintenance Committee (RMC) as a trusted caller.
- Voting platform: Snapshot
- Reasoning: Current management process is manual and includes multiple steps (including submitting a change proposal on the Research Forum, waiting for the discussion period, and coordinating with RMC participants to draft, verify, and sign the transaction). The proposed introduction will streamline this process and reinforce governance by enabling LDO tokenholders to participate in managing the list, enhancing transparency and accountability.
[EGG] Lido Labs BORG Foundation Grant Funding Request (Apr-Dec 2025)
Vote: For
Voting summary
- About: This proposal seeks an approval of $34.88m budget request to the Lido Labs BORG Foundation to advance protocol research, development, and governance initiatives with a focus on Lido v3 implementation, as well as facilitating maintenance of the Lido on Ethereum protocol, till the end of 2025.
- Voting platform: Snapshot
- Reasoning: The Foundation should have resources to execute approved earlier 2025 goals. Full support.
[EGG] Lido Ecosystem BORG Foundation Grant Funding Request (Apr-Dec 2025)
Vote: For
Voting summary
- About: This proposal seeks an approval of $10.61m budget request to the Lido Ecosystem BORG Foundation to advance stETH adoption, liquidity, and utility, as well as Liquidity Observation Lab’s $8.5m grant request for H2 2025.
- Voting platform: Snapshot
- Reasoning: The Foundation should have resources to execute approved earlier 2025 goals. Full support.
Ensuring Compatibility with Ethereum’s Pectra Upgrade
Vote: Support the proposed changes
Voting summary
- About: This proposal outlines an upgrade to the Lido protocol to ensure continuous operation with Ethereum’s upcoming Pectra hardfork with the focus is exclusively on compatibility.
- Voting platform: Snapshot
- Reasoning: Of course yes, as the Pectra upgrade introduces changes to the Ethereum specifications that directly impact components of the Lido protocol. Lido should be fully compatible with the hardforked mainnet to ensure accurately and reliably protocol operations.
Re-endorsement of wstETH on Starknet
Vote: Against
Voting summary
- About: The original proposal from January 2024 to deploy wstETH on Starknet was well received by the community and endorsed by the NEC. But during the final step of governance transfer, the process was mishandled, violating Lido’s bridging standards. As a result, the NEC initiated an offboarding.
Now the Starknet team has deployed a new token and is migrating users from the legacy token to the new one. They are now asking the DAO to formally recognize the wstETH bridge endpoints as canonical and complete the governance transfer to the DAO. - Voting platform: Snapshot
- Reasoning: A dedicated NEC committee was created to handle such requests, providing technical and security expertise and recommendations for the next steps. A couple of concerns were raised (very long periods for disclosures and incident reports, way of dealing with the incident itself), and they sound reasonable.
I really do appreciate the Abstain option, but neither the proposal nor the Snapshot vote makes it clear what will follow if the majority votes for abstain (proposal revision, etc.). Also, I won’t take Against as an ultimate rejection but as an open floor to further improvements.
Nevertheless, wstETH can still function and be used within the Starknet ecosystem, so there are no limits on the ecosystem’s growth and utilization of stETH benefits.
EASY TRACK
There were 12 motions (you may find all of them in my votings database). None of them required to be objected.
If you miss some info, please let me know and I will update this report with it, as well as include it in my next reports 
If you are one of those, delegating your LDO voting power to me, I appreciate your trust and am happy to vote on your behalf to ensure the best for Lido DAO. If you are a tokenholder looking for your delegator, you find a bit more about me, my values and governance approach here (and a short update on my current role here).
With Pectra still around the corner (the current go-live date is April 30), one thing is definite—my next report will be in May 