OCTOBER VOTINGS REPORT ![]()
A spooky month can’t scare any Public Delegate. Lido governance in October focused on streamlining operational processes and updating core protocol guidelines. During October in total there were 14 governance votings across all platforms:
| Voting platform | # of votings |
|---|---|
| On-chain | 1 |
| Snapshot | 4 |
| Easy Track | 9 |
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 #193
Vote: No
Voting summary
- About: Someone launched a vote with 0x00000001 entry (“test”).
- Voting platform: On-chain Lido DAO Voting UI
- Reasoning: Test vote with no clear purpose.
SNAPSHOT
Proposal for Updating Lido on Ethereum Validator Exits SNOP to v3
Vote: For
Voting summary
- About: This proposal has the goal to update the currently in effect Standard Node Operator Protocol (SNOP) on Validator Exits v2 to the version 3.
- Voting platform: Snapshot
- Reasoning: I’m voting in favor of this proposal, as the current SNOP version reflects a time when Ethereum’s validator exits and withdrawals were relatively static. With the introduction of Triggerable Withdrawals on Ethereum mainnet as part of the Pectra upgrade and within the Lido protocol (activated in October), along with the launch of new modules such as Simple DVT and the Community Staking Modules via the Staking Router architecture, the landscape has evolved significantly. This update ensures the SNOP remains relevant and actionable, offering Node Operators clear and consistent guidance on exits — aligned with both Ethereum’s roadmap and Lido’s decentralization goals.
Empowering Lido Ecosystem Foundation to Lead Bridge-Related Partnerships
Vote: For
Voting summary
- About: This proposal seeks DAO authorization for the Lido Ecosystem Foundation to lead all bridge-related strategic partnerships and negotiations involving stETH and wstETH, to improve competitiveness and resilience of the Lido protocol in an evolving market landscape.
- Voting platform: Snapshot
- Reasoning: I support this proposal, as it streamlines strategic decision-making by authorizing the Lido Ecosystem Foundation to negotiate and execute key partnerships on behalf of the DAO — similar to how the Network Expansion Committee (NEC) previously accelerated such processes.
Under this new structure, the NEC will continue to act as an expert advisory group, offering guidance and best practices, while a newly formed Bridging Security Committee will serve as a safeguard, empowered to pause or block any partnership that presents risks and escalate such cases to the DAO.
Importantly, the Lido DAO maintains full authority to cancel, amend, or override any agreement executed by the Foundation, ensuring accountability and DAO oversight remain intact.
Lido Ecosystem Grants Organization (LEGO) — Framework Update 1 October 2025
Vote: For
Voting summary
- About: This proposal introduces several updates to the LEGO framework, which aim to optimize fund allocation to $250k per quarter (1/2x to the prev quarterly budget), simplify the budget structure to USD-pegged stablecoins only (prev also LDO token allocations available), discontinue the LEGO Nominees program and refresh the LEGO Council composition.
- Voting platform: Snapshot
- Reasoning: All proposed changes make sense, as they reflect operational learnings and spending patterns over the past two years. This will enhance the LEGO efficiency and ensure more accurate budgeting.
Transfer TRP to Lido Labs Foundation and Amend TRP Terms
Vote: For
Voting summary
- About: This proposal seeks to have Lido Labs Foundation assume the Token Reward Plan (“TRP”) and the TRP Committee’s responsibilities for administering any LDO-based TRP. The TRP proposed to be amended as of 8 November 2025 with reduced allocations for Lido contributors as well as a reduced vesting term. Lido Labs Foundation will have the right to modify the TRP’s terms as needed to address market conditions.
- Voting platform: Snapshot
- Reasoning: Delegator decision (see here context).
EASY TRACK
There were 9 motions (you may find all of them in my votings database). None of them required to be objected.

