1. Ensuring Compatibility with Ethereum’s Pectra Upgrade
Forum post here
Vote: Support the proposed changes
Rationale:
The changes are well thought and backed by other sectors of the Lido ecosystem. They are not the only modifications to the protocol that can be done after Pectra, but they are the ones that must be done to ensure continuity. Changes that include new functionality / streamlining of current functionality thanks to the new additions to Ethereum coming with Pectra will have to wait for now.
The on-chain vote here will be absolutely critical - so I’ve requested a guide to properly check it so anyone can verify that the params have been properly implemented.
2. and 3. EGG Lido Ecosystem BORG Foundation Grant Funding Request (Apr-Dec 2025) and EGG Lido Labs BORG Foundation Grant Funding Request (Apr-Dec 2025)
Vote: For and For
Rationale:
I’m combining the explanation for both as it is easier for me to look at it as the operational funds for the year at large.
It comes after the temporary grant extension voted in December, and now adjusted for the 2 new entities (BORGs) that have been created to streamline operations: the Ecosystem (external-facing) and Labs (internal/product-facing).
They total 45.49M, distributed as follows:
If we think in yearly cycles, we also need to add the 11M and 8.8 M requested for continuity for the 1st 3 months of the year, amounting to 65.29 M in total.
We also have this beautiful graph from the Lido team:
But… here’s where I think it gets very hard to follow. Some of this money is “duplicated” because it’s a rollover of the underspend funds from previous EGG grants.
Speaking of previous periods, thinking again in yearly cycles, we saw a budget of 47.1 M for the previous cycle.
And what I’m missing is some end-of-period reporting with better milestones / deliverables, not just “spent/underspent”…
But overall, even if the reporting and clarity can be improved, the teams get a 
from me to keep Lido improving and growing!
4. MEV-Boost Relay Allowed List management via Easy Track
Forum post here
Vote: For
Rationale:
Here:
5. SSV Lido Module Proposal
Forum post here
Vote: Approve
Rationale:
Very exciting! A new module to Lido! This proposal approves the collaboration and the allocation of resources to supporting Clusterform (SSV network) to develop and test the module. LFG decentralization of the validator set!
Beyond decentralization, we should acknowledge that the Lido SDVTM, powered by SSV and Obol clusters, holds the highest RAVER score of the 3 modules, above the curated module formed by professional operators.
But SDVTM is also permissioned, so I’m excited for seeing whether the SSVLM, which will put permissionlessness into the mix, will be equally performant.
6. Lido DAO Ops Multisigs Policy 2.0
Forum post here
Vote: Adopt Multisig Policy 2.0
Rationale:
As a member of the Community Staking Module Committee, I am bound by this policy.
I find it perfectly reasonable and acceptable.