Irina Delegate Thread

Delegate Platform
16

MAY VOTINGS REPORT :deciduous_tree:

Lido governance in May 2025 was an intense one with planned and emergency votes that addressed critical security, operational, and architectural updates. During the last spring month, in total there were 18 governance votings across all platforms:

Voting platform # of votings
On-chain (prev. Aragon) 3
Snapshot 3
Easy Track 12

Take a quick look at the dashboard below or check a detailed report below :point_down:

image
image1920×1080 130 KB

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 #186
Vote: Yes

Voting summary
  • About: Emergency rotation of compromised Chorus One oracle address in the Lido on Ethereum Oracle set.
  • Voting platform: On-chain Lido DAO Voting UI
  • Reasoning: Although the oracle system requires a 5/9 quorum, it’s absolutely reasonable to replace the compromised one from the system at all.

Vote #187
Vote: Yes

Voting summary
  • About: It is an omnibus vote that contains separate updates approved by Lido DAO via Snapshot voting before:
  1. Post-Pectra update (items 1-9). To adjust Oracle Report Sanity Checker parameters to align with reduced slashing penalty and updated validator churn limits. Audited by MixBytes.
  2. Add Easy Track Factories for managing MEV-Boost Relay Allowed List (items 10-13). Audited and verification deployed by MixBytes.
  3. Reduce keyRemovalCharge for the Community Staking Module (items 14-16).
  4. Increase Easy Track security limit for Liquidity Observation Lab from 2.1k stETH per 3 months to 6k stETH per 6 months (item 17).
  • Voting platform: On-chain Lido DAO Voting UI
  • Reasoning: All changes were approved earlier via Snapshot and audited to be added to the mainnet.

Vote #188
Vote: Yes

Voting summary
  • About: It’s a re-run of Vote #187, which didn’t reach a quorum
  • Voting platform: On-chain Lido DAO Voting UI
  • Reasoning: All changes were approved earlier via Snapshot and audited to be added to the mainnet.

SNAPSHOT

Community Staking Module v2. Architecture and Fee Structure
Vote: For

Voting summary
  • About: This proposal outlines the architecture description and fee structure for the proposed major upgrade of the Lido CSM called CSM v2. A detailed description of CSM v2 architecture and features can be found in LIP-29 and the corresponding landscape document.
  • Voting platform: Snapshot
  • Reasoning: Absolute support and blessings to this proposal! As the CSM matures and attracts more operators, it’s important to keep it attractive for solo and community stakers, as this module was designed for. Proposed validator management, security architecture, and seasonal referral program will also allow enhanced decentralization, scalability, and flexibility.

Establishment of the Auxiliary Proposer Mechanisms Committee
Vote: For

Voting summary
  • About: This proposal aims to establish the Auxiliary Proposer Mechanisms (APM) Committee, which will be responsible for reviewing, approving, and maintaining the list of APMs that Lido Node Operators are allowed to use. The committee should ensure that only secure, value-aligned proposer-layer mechanisms (such as preconfirmations) are permitted, as well as establishing the conditions of fair use. The Committee will be formally established and start operating immediately once approved by the DAO.
  • Voting platform: Snapshot
  • Reasoning: The APM Committee is vital to oversee the vetting process and maintain the Allowed List of approved APMs. The proposed committee structure consists of members with different backgrounds (Lido contributors, technical reviewers, risk experts, APM community contributors, as well as an Ethereum Foundation member for consulting) to ensure the best possible decision-making process.

LIP-28: Dual Governance — Implementation, Parameters, Committees
Vote: For

Voting summary
  • About: This proposal seeks approval on the final Dual Governance proposal, including the mechanism design and implementation outlined in the LIP-28, system parameters, and committees required to ensure system resilience and their proposed powers.
  • Voting platform: Snapshot
  • Reasoning: Finally! Dual Governance is marching towards the mainnet. Looking forward to seeing the benefits it brings both to the protocol and stakers’ governance inclusion.
    Next step - vote to initiate the launch of Dual Governance!

EASY TRACK

There were 12 motions (you may find all of them in my new votings database). None of them required to be objected.

I would like to express my sincere gratitude to all LDO tokenholders for entrusting me as your Public Delegate. Your support have been instrumental in driving Lido’s governance improvements.

Keeping my eyes on the proposals and see you next month!