Vote #184 (Onchain)
Summary:
This suggests extending on-chain voting duration to 120 hours, which includes changes to GateSeal, and Easy Track setups for Lido Ecosystem & Lido Labs BORG Foundations. Details can be found here.
Vote: Yes
Rationale:
We strongly support this proposal, which includes changes to the on-chain voting duration we initially put forward. This aligns with our ongoing commitment to lowering barriers to Lido DAO governance participation and enhancing DAO security. We have also consistently supported the establishment of the two BORG Foundations since the Snapshot vote (Lido Labs / Lido Ecosystem), and our position remains unchanged. The Easy Track setups are essential for the operational functionality of these two entities.
Ensuring Compatibility with Ethereum’s Pectra Upgrade (Snapshot)
Summary:
This proposal aims to update the Lido protocol for compatibility with Ethereum’s upcoming Pectra hardfork, focusing solely on ensuring continued operation rather than integrating new features. It involves updating oracle algorithms, sanity checker limits, and the CS Verifier contract to align with the new Ethereum protocol specifications.
Vote: Support the proposed changes
Rationale:
We generally support this proposal, recognizing that these changes are necessary for the continued operation of the Lido protocol. It is crucial that the updates proceed safely, and we will be paying close attention to the upcoming audit reports to ensure a secure implementation.
[EGG] Lido Ecosystem BORG Foundation Grant Funding Request (Apr-Dec 2025) (Snapshot)
Summary:
The proposal requests $10.61M in funding to support the Lido Ecosystem BORG Foundation’s efforts to increase stETH adoption, improve liquidity, and expand its utility, aligning with GOOSE-2 goal #3. This amount includes a renewed $8.5M grant for the Liquidity Observation Lab’s H2 2025 operations.
Vote: For
Rationale:
We are in favor of this proposal. Similar to the Labs’ proposal, this covers initiatives that should be undertaken on an ongoing basis. Also, we believe that exploring protocol-owned liquidity (POL) is a significant new endeavor, as it has the potential to be more sustainable than traditional liquidity incentives.
[EGG] Lido Labs BORG Foundation Grant Funding Request (Apr-Dec 2025) (Snapshot)
Summary:
This proposal seeks grant approvals for the Lido Labs BORG Foundation through December 31, 2025, to fund protocol research, development, and governance initiatives focused on implementing Lido v3 and maintaining the Lido on Ethereum protocol. The total budget request is $34.88 million.
Vote: For
Rationale:
This presents a well-rounded approach to addressing Lido’s key priorities, appropriately focusing on the responsibilities of the Lido Labs Foundation after its restructuring. We are particularly pleased with the combination of clearly defined objectives, measurable KPIs, and the stated intention to enhance transparency within the foundation’s operations. This comprehensive approach is essential for Lido’s continued success.
MEV-Boost Relay Allowed List management via Easy Track (Snapshot)
Summary:
The proposal aims to enhance the MEV-Boost Relay Allowed List management by implementing Easy Track EVM script factories, enabling the Relay Maintenance Committee (RMC) to efficiently add, remove, or edit relays with increased governance from LDO tokenholders.
Vote: For
Rationale:
This strikes a good balance between operational efficiency and strong DAO governance through the well-structured implementation of Easy Track. We do not have any outstanding concerns with the Relay Maintenance Committee’s performance, and believe this transition will be beneficial overall.
SSV Lido Module Proposal (Snapshot)
Summary:
The proposal is to integrate the SSV Lido Module (SSVLM) into the Lido protocol, which would enable Node Operators to join the Lido on Ethereum staking ecosystem using Distributed Validator Technology.
Vote: Approve
Rationale:
We have also been utilizing SSV for our node operation and see great potential in it. The automation of validator assignments and cluster management using dedicated oracles represents a significant improvement in terms of scalability and reducing the risk of human error in protocol operations. This would be a substantial step forward for the protocol.
Lido DAO Ops Multisigs Policy 2.0 (Snapshot)
Summary:
Lido DAO’s Multisigs Policy 2.0 aims to enhance security and operational efficiency by establishing clear guidelines for signer requirements, rotation processes, and public transparency, ensuring accountability and alignment with Lido’s mission.
Vote: Adopt multisig policy 2.0
Rationale:
We strongly support the updated policy’s security enhancements, especially requiring use of hardware wallets and the prohibition of using signer wallets for other purposes for certain types of signers. Given recent Safe incidents, we believe prioritizing wallet security is essential, and these changes are a vital step.
There is a more detailed multisig security policy, which we comply with for the multisig operation in Optimism (details). As it has more specific guidelines such as which specific hardware wallets to use, how to prepare the backup wallets, and how to travel with signing keys, this might be useful as a reference in the future policy updates.