Irina Delegate Thread

Delegate Platform
1

Name

Irina

Address

0x06A90756e57bC7A016Eed0aB23fC36d11C42bBa0

Introduction

Hello, Lido community! My name is Irina. I am the Segment Lead within the Everstake team. Before setting the anchor at Everstake, I was part of marketing teams in Web2, working for tech corporations such as Microsoft and Google, and contributing to the growth of the artificial intelligence (AI) ecosystem in Ukraine.

Many of you may know me from my regular Node Operators Community Call recaps, but besides these, I do tons of educational content around Ethereum for the community, as I believe that fighting informational asymmetry and biases will help make this space better. I cover covers not only the latest things around Ethereum and explain novel, complicated concepts in simple words but also touch on the broader landscape that shapes the Ethereum we know today and will face tomorrow. More solid materials from my side include Ethereum ecosystem reports within our reports hub, articles, and talks on the crypto conferences (the last one was on Ethereum governance).

Thanks for considering my application! Below, you can find out more about my motivation, values, and decision-making approach. If any questions, I will be happy to answer them.

Contact Information

Motivation

The recent Compound governance attack proved once more the importance of true voters’ dedication and accountability to the governance process, thus, in my opinion, the introduction of a Public Delegate Platform is just in time to enforce a sustainable governance process within Lido DAO itself.

I have been within the Lido ecosystem for a long time, so I see this initiative as a great opportunity to contribute my expertise and usefulness to the protocol evolution, community, and LDO token holders. For the latter, keeping track of all proposals and voting deadlines may be a burden, which may create a perception of centralization, underrepresentation, and the worst—FOMO, as it’s pretty challenging to be on top of everything given the speed of projects within Web3 space.

As soon as within my Everstake role I also take care of Everstake representation in the Lido governance process, thus if I become a Public Delegate, it won’t be an extra effort for me, as it is something I used to do on a daily basis.

Besides, I find the governance process itself interesting, as this concept matures across the Web3 industry (maybe that’s one of the reasons I write so much about it and my recent conference talk was dedicated to it).

Below are some examples of my participation in the Lido governance across past few years:

Objectives as a Public Delegate
These are focused on three main pillars of the Lido ecosystem:

  1. Serve to protocol. Ensure Lido safe and sound sustainable growth as a leading liquid staking solution, with best-in-class security, deepest liquidity and competitive rewards in accordance with Lido Vibe trinity (purpose, mission, and vision) that benefit both the protocol and the broader Ethereum ecosystem.
  2. Serve to DAO. Provide in-depth analysis, qualitative discussions, and feedback on the numerous proposals on the forum, as well as active voting participation to minimize not-reached-quorum on-chain voting.
  3. Serve to LDO, stETH and stMATIC tokenholders. While under the current governance design, only the first are eligible to participate, I aim to represent the voices of various interested parties, as all their interests are crucial to the protocol’s long-term success. For LDO tokenholders specifically, I want to be a reliable and helpful mediator in expressing their will and power of Lido future.

With a good understanding of the Lido governance process and a set process of allocating time for it, I will be a great delegate for your voting power. With your support, my commitment and track record of taking part in Lido governance will continue to make a significant impact within this ecosystem.

Values and Decision-Making Approach

My values
Core values that will define my decision-making approach:

  • Stay true to the Lido Vibe:
    • Purpose: Keep Ethereum decentralized, accessible to all, and resistant to censorship.
    • Vision: A world in which Ethereum is the co-ordination and value layer of the internet.
    • Mission: Make staking simple, secure, and decentralized.
  • Holistic and sustainable growth: all decisions will be made with the focus on protocol, tokenholders and stakers security and long-term success.
  • Integrity, transparency and accountability: I will provide clear reasoning for the decisions I will make with the delegated voting power and the live publicly accessed database of all ongoing and completed votings in the form of a table (see the example below—it is the one I currently use for internal purposes that has all Lido governance votings since 2022):
    1600Ă—1122 447 KB
  • Active participation and voting: I commit to voting in at least 70% of the votes per quarter and providing feedback on the proposals on the forum while continuing active community engagement and informing on the governance process through my X / Twitter.

What will define my decision-making process?
I am attentive to details and have an analytical mindset. Thus, if you select me as a delegate, you can be sure of a thorough analysis of the proposals. While analyzing the proposal, I always consider the decision’s impact on protocol security and sustainability, as well as its effects on the broader Lido ecosystem.

It’s worth adding that I have an economic degree, which allows me to consider potential implications for Lido’s growth. Unfortunately, I have 0 code expertise, thus, my choices will be based on the audits’ provided results and the reputability of the teams that delivered them.

Public Acceptance

I am fully aware of the requirements and expectations of a Public Delegate. If I am selected as a Public Delegate, I will act in accordance with the Public Delegate Code of Conduct, which includes the below, as well as ensure the best for Lido protocol:

Also there is absolute alignment with the mission, vision, and purpose of Lido DAO, as well as I am aware of updated 2024 goals for Lido, ReGOOSE.

Disclosures

  • As mentioned straightforwardly in the intro, I am part of Everstake, a staking service provider and a node operator within the Lido on Ethereum and Polygon Curated set. As part of my role in Everstake, I am in charge of Everstake operations with Lido.
  • Earlier this year, specifically in March 2024, I received a LEGO (Lido Ecosystem Grants Organization) grant for my social media posts on Lido, which allowed me to participate in the Lido governance process as a voter.
  • I am staking ETH with Lido (one more reason why I do care about Lido protocol and ecosystem sustainable development).

You can find examples of my past Lido governance activity in my Snapshot voting profile (0 missed proposals brought to Snapshot voting since I got the privilege to join the governance process following the recipience of the LDO grant), or check all the screenshots here.

6 Likes
2

Hello my lovely delegators and the broader Lido community :wave:

As I mentioned in my application:

Thus I am sharing with you a table (comment access via the link) with all my votes since I received a LEGO grant, allowing me to take part in the governance, till the moment you will open it (this database will update with new votings as they appear).

Please find below a short instruction and hints that will make the most of this table for you:

Voting dashboard tab:

  • On the top left you may find my Delegate voting address and amount of delegated LDO voting power.
    If you want to delegate your LDO voting power to me, copy the address, go to Delegation | Lido DAO Voting UI, insert it into “Delegate address” field and click Delegate on Aragon & Snapshot button. This will add your voting power to my future votes.

    image
    image1276Ă—94 14.9 KB

  • On the top right you may find voting stats for the current month (a total number of votings per specific voting platform that has already ended and is currently going):

    image
    image864Ă—126 9.37 KB

  • The main table that includes the name of a proposal or voting, number if any, the link to it, what and when I voted, the voting platform and additional information.
    At the beginning of the table you will find this month’s votings, and the longer-standing one below:

    image
    image2098Ă—456 108 KB

  • What does No objection vote for Easy Track mean? An Easy Track motion is considered to have passed if the minimum objections threshold (0.5% of the total token supply) hasn’t been exceeded (more about Easy Track here). Thus No objection status means that I do support the motion and have no objection against it

Useful links:

  • For your convenience, I have added (and will add more!) various links that I believe may be helpful for LDO delegators.
    image
    image1642Ă—510 83.5 KB

NB. This table is not immutable and will mature and improve as I will polish it during usage and based on your feedback. Thus if you miss something or like something, let me know :pray:

3 Likes
3

AUGUST VOTINGS REPORT :sunrise:

Here’s a quick glance at my governance activity in August. The last summer month was hot for Lido DAO. During it, in total there were 23 governance votings across all platforms:

Voting platform # of votings
On-chain (prev. Aragon) 2
Snapshot 5
Easy Track 16

A detailed report is below in this comment :point_down:

photo_2024-09-03_12-06-24 copy
photo_2024-09-03_12-06-24 copy1280Ă—798 125 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 (PREV. ARAGON)

Vote #177
Vote: Yes

Voting summary
  • About: This vote is aimed at implementing on-chain:
  1. Replace Rated Labs with MatrixedLink in Lido on Ethereum Oracle set
  2. Rename CryptoManufaktur Node Operator to “Galaxy” (due to acquisition) and update the reward address
  3. Add On-Chain Delegation as a part of contract upgrade within the Public Delegate Platform
  • Voting platform: On-chain (prev. Aragon) – Lido DAO Voting UI
  • Reasoning: All the suggested to implement were earlier supported via Snapshot. This vote will enact the supported proposals on-chain.

Vote #178
Vote: Yes

Voting summary
  • About: Vote #177 re-run. Please see above for details.
  • Voting platform: On-chain (prev. Aragon) – Lido DAO Voting UI
  • Reasoning: All the suggested to implement were earlier supported via Snapshot. This vote will enact the supported proposals on-chain.

SNAPSHOT

Establish a Public Delegate Platform and Delegate Incentivization Program
Vote: Approve platform & incentives

Voting summary
  • About: A proposal aimed to increase active governance process participation, improve the quality of discussions and feedback, and enhance Lido on Ethereum safety by involving new participants in governance through the Delegation Program, which will be incentivized via a 6-month pilot.
  • Platform: Snapshot
  • Reasoning: Given the nature of the recent Compound governance attack, it is a timely proposal to enforce a sustainable governance process.

LIP-25: Staking Router 2.0
Vote: Yay

Voting summary
  • About: The proposal aimed to upgrade existing Staking Route architecture and includes improvements to both on- and off-chain parts of the following components: the Deposit Security Module, the Validator Exit Bus Oracle, the Accounting Oracle and reward distribution mechanisms in curated-based staking router modules.
  • Voting platform: Snapshot
  • Reasoning: The suggested changes will really make the Staking Router better. Audits will be completed by Ackee and Mixbytes, reputable Web3 auditors

Decision on Rated Labs’s position in the Oracle Set: rotate or remove and change the quorum
Vote: Rated Labs → MatrixedLink

Voting summary
  • About: Rated Labs expressed their intention to depart from the Lido oracle set. MatrixedLink would like to replace them. The transition is expected to occur in Q3 2024.
  • Voting platform: Snapshot
  • Reasoning: The rotation is an optimal option. As per DAO Ops workstream note, MatrixedLink went through the testnet and is a good fit for this role.

Should the Lido DAO recognize the wstETH Bridge Endpoints on BNB as canonical?
Vote: Recognize

Voting summary
  • About: The proposal is to recognize the wstETH token bridging endpoints for BNB by the Lido DAO as canonical. When passes, the Lido DAO will control the endpoints of wstETH token contract as a proxy admin.
  • Voting platform: Snapshot
  • Reasoning: Time to enhance wstETH on L2.

Should the Lido DAO recognize the wstETH Bridge Endpoints on Mode as canonical?
Vote: Recognize

Voting summary
  • About: The proposal is to recognize the wstETH token bridging endpoints for Mode by the Lido DAO as canonical. When passes, the Lido DAO will control the endpoints of wstETH token contract (including the token contract on Mode itself) as a proxy admin.
  • Voting platform: Snapshot
  • Reasoning: Time to enhance wstETH on L2.

EASY TRACK

There were 16 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 into my next reports :relieved:

See you next month!

3 Likes
4

SEPTEMBER VOTINGS REPORT :leaves:

A perfect recipe to enjoy the autumn season? Pumpkin late and a report, covering the Lido governance and my activity within it in September. During it, in total there were 20 governance votings across all platforms:

Voting platform # of votings
On-chain (prev. Aragon) 0
Snapshot 7 (only 2 non-scam)
Easy Track 18

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

image
image1760Ă—990 163 KB

Also there were in total 7 Snapshot votings, 5 of them were a scam one with the proposal of a same fake airdrop. I won’t review them below, but you can check them in the table. Please see a breakdown of the legitimate ones with the voting name, my vote and a short reasoning, as well as a short summary of what the vote was about:

SNAPSHOT

Should Galaxy continue in the Curated Module set following the acquisition of CryptoManufaktur?
Vote: For

Voting summary
  • About: In July, it was announced that Galaxy had acquired CryptoManufaktur, one of the node operators of the Curated set. The forum discussion resulted in the community and Lido Node Operator Subgovernance Group (LNOSG) not seeing any reason to object to Galaxy staying on in the Curated Module as the successor to CryptoManufaktur. This voting aimed to formalize acceptance of the proposal that Galaxy should remain in the Curated Module.
  • Voting platform: Snapshot
  • Reasoning: CryptoManufaktur validator operations (infra, people, geographic distribution and jurisdictional location) remain the same, showcasing a benchmark for many fellow operators. Torsten and the team are professionals pushing boundaries of Ethereum excellence (I don’t know anyone who has done for EL client diversity more than Thorsten), so it is an absolute pleasure and honour to have them in the Curated NO set, now as a part of Galaxy team.

Organize the Lido Alliance Program as a Lido-DAO-Adjacent BORG
Vote: Approve the Lido Alliance BORG

Voting summary
  • About: This proposal aims to formalize and legalize the creation of a LIDO Alliance workgroup through the incorporation of a Lido DAO BORG (cybernetic organization or CybOrg) powered by MetaLeX to legally cover the Alliance workgroup and its related assets, operations and activities.
  • Voting platform: Snapshot
  • Reasoning: As soon as Lido DAO can’t enter into agreements, as it lacks legal personality, this is a valid solution to set up everything and ensure smooth operations of Lido Alliance…

EASY TRACK

There were 18 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 :relieved:

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.

Have a great October, and look for another report after Halloween :ghost:

1 Like
5

OCTOBER VOTINGS REPORT :jack_o_lantern:

Spooky season for everyone? Delegates had no time for being scared or distracted, as lots of proposals to vote for this month. During it, in total there were 28 governance votings across all platforms:

Voting platform # of votings
On-chain (prev. Aragon) 2
Snapshot 6
Easy Track 20

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

image
image1760Ă—990 193 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 (PREV. ARAGON)

Vote #179
Vote: Yes

Voting summary
  • About: This vote is aimed at implementing on-chain:
  1. Upgrade wstETH on Optimism bridge endpoints to enable rebasable stETH on Optimism alongside wstETH.
  2. Add Easy Track setup for funding the Lido Alliance Operational Multisig. Line
  • Voting platform: On-chain (prev. Aragon) – Lido DAO Voting UI
  • Reasoning: All the suggested to implement were earlier supported via Snapshot. This vote will enact the supported proposals on-chain.

Vote #180
Vote: Yes

Voting summary
  • About: This vote is aimed at releasing the Community Staking Module (CSM) for permissionless staking and upgrading the Staking Router to ensure compatibility with CSM and future modules, improving system efficiency. Also it includes the rotatation the Instadapp Oracle address, as requested on the forum.
  • Voting platform: On-chain (prev. Aragon) – Lido DAO Voting UI
  • Reasoning: All the suggested to implement were earlier supported via Snapshot. The Staking Router 2.0 and CSM release were properly audited by Ackee Blockchain and Mixbytes. This vote will enact the supported proposals on-chain.

SNAPSHOT

Lido Community Staking Module Mainnet Release Setup
Vote: Approve CSM mainnet release

Voting summary
  • About: A signal vote from the Lido DAO members to get approval on CSM parameters, their configuration for use in the mainnet release, and the granting of some CSM management permissions to the CSM committee.
  • Voting platform: Snapshot
  • Reasoning: This inclusion into the Lido mainnet is a milestone making node operators set more decentralized, diversified and accessible to join by community and solo stakers. Parameters are thoroughly checked before being proposed.

Change Easy Track limits for PML & ATC
Vote: Support the change

Voting summary
  • About: This proposal suggests updating the Easy Track limits for two multi-signature addresses in LCG (Lido Contributors Group) to reflect changes in PML (Pool Maintenance Labs Ltd.) from 6M to 4M and ATC (Argo Technology Consulting Ltd) from 1.5M to 7M USDC/USDT/DAI per quarter (for both) funding needs and token redistribution. These changes aim to align on-chain security constraints with operational needs.
  • Voting platform: Snapshot
  • Reasoning: This will allow to achieve the goals set by the 2024 v2: Continuity Grant Funding and to ensure healthy and sound utilization of cash flows, as well as to align on-chain security constraints with operational needs…

Increase the Proposal Threshold for Snapshot
Vote: Do nothing

Voting summary
  • About: This proposal seeks to increase the Snapshot proposal threshold to 5k-15k LDO to prevent spam and encourage higher-quality submissions.
  • Voting platform: Snapshot
  • Reasoning: I do NOT support this community proposal, because the suggested design may decrease accessibility to submit proposals by individuals, while at the same time give additional burden to DAO Operations Workstream, as fair actors who do not own enough tokens will reach to them to create a proposal.

Lido Alliance application: Bolt
Vote: Onboard Bolt to Lido Alliance

Voting summary
  • About: In this proposal, Chainbound asks for the onboarding Bolt (enables sub-second preconfirmations on Ethereum) as a part of Lido Alliance. Among other benefits, Chainbound plans to allocate 6.5% of Bolt’s total token supply to the Lido Alliance. At the same time Chainbound is seeking from this membership: endorsement, integration, and communication support; support and consultation.
  • Voting platform: Snapshot
  • Reasoning: Pre-confirmations are the next big topic. Bolt is a great addition to the Alliance and will benefit the protocol. It’s design (open-sourced, permissionless and moving towards censorship resistance) aligns with Lido Vibe and enables moving towards reGOOSE.

Integrate CSM into the Decentralized Validator Vault
Vote: Yes, vote for the integration

Voting summary
  • About: This proposal aims to integrate the CSM into the DVV alongside the Simple DVT Module, benefiting stakers using the CSM, Mellow DVV users, and the overall decentralization of the Lido on Ethereum protocol.
  • Voting platform: Snapshot
  • Reasoning: This is a cool idea because the Mellow Decentralized Validator Vault will be a great resource for additional ETH inflow into CSM, in addition to directly from the Lido protocol itself. Thus, it will allow all participants willing to join the Lido operator set as a CSM operator to deposit faster, overall boosting Lido operator set decentralization and diversification.

Should the Lido DAO recognize the wstETH bridge endpoints on Zircuit as canonical?
Vote: Recognize

Voting summary
  • About: The proposal is to recognize the wstETH token bridging endpoints for Zircuit by the Lido DAO as canonical. The DAO will control the endpoints of wstETH token contract (including the token contract on Zircuit itself) as a proxy admin, and will only have the upgrade authority of the wstETH proxy contract, and will not be able to manage the native bridge itself.
    Vote for: “Recognize”
  • Voting platform: Snapshot
  • Reasoning: Time to enhance wstETH on L2 :smirk:

EASY TRACK

There were 20 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 :relieved:

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… or we can meet at person on the DevCon :thailand:. DM me, if you are interested.

Have a great November, and look for another report at the end of the month!

1 Like
6

The end of 2024 was crazy, but still I would like to catch up on my monthly reports.

NOVEMBER VOTINGS REPORT :fallen_leaf:

Devcon was not an excuse to delay votings. Lido governance in November 2024 saw key proposals addressing strategic goals for 2025 and direction of Lido on Polygon, as well as operational improvements. During this month, in total there were 24 governance votings across all platforms:

Voting platform # of votings
On-chain (prev. Aragon) 1
Snapshot 6
Easy Track 17

A helivopter view on the image or check a detailed report below :point_down:

image
image1920Ă—1080 112 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 (PREV. ARAGON)

Vote #181
Vote: Yes

Voting summary
  • About: This vote is aimed to:
  1. reduce the PML limit from 6M to 4M, and increase the ATC limit from 1.5M to 7M in USDC/USDT/DAI per quarter to reflect operational changes;
  2. increase the Lido Stonks stETH limit to 12,000 stETH and reset spent amount, as per the Treasury Management Committee’s decision.
  3. update the reward address for Simply Staking Node Operator as per their request.
  • Voting platform: On-chain (prev. Aragon) – Lido DAO Voting UI
  • Reasoning: All the suggested to implement were earlier supported via Snapshot (1) or are operationa changes to improve the processes (2 and 3). This vote will enact the supported proposals on-chain.

SNAPSHOT

GOOSE 2024 cycle: Lido DAO goals for 2025
Vote: Adopt Goals

Voting summary
  • About: This vote presents for approval Lido goals for 2025 suggested by @Hasu as follow:
  1. Expand stETH’s ecosystem with a diverse product line to meet the diverse needs of Ethereum stakers and reignite growth.
  2. Establish an open market for validators to align validator rewards with contributions against Lido’s mission.
  3. Strengthen LDO’s role in governance by aligning incentives with Lido’s long-term success, promoting stability and sustainability for the protocol.
  • Voting platform: Snapshot
  • Reasoning: Nobody says it better than Hasu. The suggested objectives can really help ensure that Lido will grow, evolve and succeed…

Reevaluation of Lido on Polygon state
Vote: Initiate reevaluation

Voting summary
  • About: This proposal outlines the request to reevaluate the economics of Lido on Polygon middleware or to transition towards sunsetting.
  • Voting platform: Snapshot
  • Reasoning: I do believe that we need to make a re-evaluation first, and then have on the scales the closure and reanimation plan (efforts, costs, outcomes). Existing reasoning that the Lido on Polygon state has been caused by market conditions is not sound:
  1. we see successful other MATIC/POL LSTs;
  2. there were absolutely NO marketing and growth efforts from the managing team confirmed by their comment (no guess that user have no idea about stMATIC opportunities).

Should Nansen continue in SDVT following the acquisition of Stakewithus?
Vote: For

Voting summary
  • About: Stakewithus is now part of Nansen. This proposal seeks suggest the DAO to decise whether or not to allow Nansen.ai to continue Node Operations in Lido on Ethereum Simple DVT as-is.
  • Voting platform: Snapshot
  • Reasoning: All of Stakewithus’s validators and related staking resources will remain fully operational by the exact same team with NO operational changes (personnels + geographical distribution of nodes + vendors utilized).

Should Alchemy continue in SDVT and LoP following the acquisition of Bware Labs?
Vote: For

Voting summary
  • About: Bware Labs was acquired by Alchemy. This proposal seeks suggest the DAO to decise whether or not to allow Alchemy to continue Node Operations in Lido on Ethereum Simple DVT and Lido on Polygon as-is.
  • Voting platform: Snapshot
  • Reasoning: Bware Labs “Blockchain Validators businesses will continue to operate as they have been” as per their blog, so no reason to stop their participation in both Lido on Ethereum and Lido on Polygon.

Should Pier Two continue in the Curated Module Set following the acquisition of Numic?
Vote: For

Voting summary
  • About: Numic was acquired by Pier Two. This proposal seeks suggest the DAO to decise whether or not to allow Pier Two to continue Node Operations following a trial run on testnet and then (upon successful completion) commences a slow ramp-up on mainnet.
  • Voting platform: Snapshot
  • Reasoning: Pier Two is a current Simple DVT operator. As soon as Numic had a security incident earlier, the proposed approach with testnet and gradual increase on the mainnet has lots of sense.

Establish the Network Expansion Committee (NEC)
Vote: Approve NEC

Voting summary
  • About: This proposal aims to establish a Network Expansion Committee that will be assigned to formally recognize (w)stETH token bridging endpoints and denominations on new networks as canonical, acting on behalf of Lido DAO.
  • Voting platform: Snapshot
  • Reasoning: The introduction of the Network Expansion Committee (NEC) will simplify and speed up the process, transferring decision-making from the DAO to the committee. This will smooth the deployment and review processes and reduce the potential for human error. At the same time, the DAO retain full control - the DAO vote that will reach a quorum can override any NEC decision at any time.

EASY TRACK

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

December report is being cooked and will be shared :soon:

7

DECEMBER VOTINGS REPORT :christmas_tree:

A hot end of year. December governance was focused on the protocol decentralization and further operational improvements. During the last 2024 month, in total there were 22 governance votings across all platforms:

Voting platform # of votings
On-chain (prev. Aragon) 1
Snapshot 5
Easy Track 16

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

image
image1920Ă—1080 93.6 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 (PREV. ARAGON)

Vote #182
Vote: Yes

Voting summary
  • About: This vote is a re-run of November vote #181 (please see details via the link), which didn’t gain the quorum.
  • Voting platform: On-chain (prev. Aragon) – Lido DAO Voting UI
  • Reasoning: All the suggested to implement were earlier supported via Snapshot (1) or are operationa changes to improve the processes (2 and 3). This vote will enact the supported proposals on-chain.

SNAPSHOT

Update Lido on Ethereum Standard Node Operator Protocol - Validator Exits
Vote: For

Voting summary
  • About: This proposal seeks the community’s approval to update the currently in effect Lido on Ethereum Validator Exits Policy 1.0, as the previous is outdated as it does not reflect protocol improvements made in Staking Router, and the addition of the Simple DVT and CSM modules which are now live on mainnet.
  • Voting platform: Snapshot
  • Reasoning: Its ancestor, Lido on Ethereum Validator Exits Policy, is outdated and does not include the protocol changes throughout the past two years. Thus the updated version will close all the gaps.

Extend On-Chain Voting Duration
Vote: Extend duration to 3+2 days

Voting summary
  • About: This proposal is aimed to extend on-chain voting duration for better participation and security.
  • Voting platform: Snapshot
  • Reasoning: Proposed extended timeframes for voting may allow more LDO token holders not to miss the on-chain votes, so we may decrease a number of re-runs of the same vote due to lack of quorum.

[EGG] Multi-EGG Continuity Grant Funding
Vote: For

Voting summary
  • About: This proposal seeks funding approval:
  1. to advance towards set goals and preparation ahead of updates to deliver 2025 plans (3 months)
  2. for development, audit and deployment of Dual Governance, along with preparing and enabling the permissionless CSM entry (6 months)
  3. to maintain rollout and node operator onboarding for Simple DVT and CSM modules (6 months)
  4. to support continuity for the Bug Bounty program (12 months)
  • Voting platform: Snapshot
  • Reasoning: Budget for Lido Contributors Group activities throughout the next quarter (moving towards 2024 and 2025 goals), the first half of the year (for ecosystem growth) and the year (Bug Bounty program).

Lido Alliance Grant Proposal
Vote: For

Voting summary
  • About: This proposal seeks funding approval to continue the activities of the Lido Alliance BORG through 2025.
  • Voting platform: Snapshot
  • Reasoning: Alliance plays an important role in building and expanding stETH’s Ecosystem through other projects. To enable their work it should be properly funded.

CSM: Enable Permissionless Phase and Increase the Share Limit
Vote: For

Voting summary
  • About: It is proposed to complete the Early Adoption phase and transition CSM to a fully permissionless mode and increase a share from 1% to 2% to ensure further expansion of the Lido protocol decentralization.
  • Voting platform: Snapshot
  • Reasoning: CSM proved to be a successful solution to improve Lido validator decentralization. Time to scale!

EASY TRACK

There were 16 motions (you may find all of them in my 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.

I am deeply committed to upholding the highest standards of governance and working tirelessly to ensure Lido’s continued excellence. In 2025 I will continue to actively participate in all governance discussions, carefully evaluate proposals, and always prioritize the long-term growth and sustainability of the Lido ecosystem :saluting_face:

2 Likes
9

Hello dear Lido DAO and the broader community, LDO tokenholders, my delegates, contributors team and everyone who may find this message. With it I would like to share an important update regarding my professional transition. I have resigned from my role as Segment Lead at Everstake and will now be contributing as Ecosystem Manager at Lido. Given this new position, I want to be fully transparent with the community as this may present a potential conflict of interest, and I will update my Delegate profile accordingly.

That said, there will be no changes in my participation as a Public Delegate. My recent silence on the forum was due to the transition process, but I am happy to be back with the same enthusiasm, experience, and commitment to my stated values—now with even greater passion for driving Lido’s protocol improvement forward.

If any questions or concerns, please share here or reach out to me in DM here.
As usual, at your service :saluting_face:

3 Likes
10

JANUARY VOTINGS REPORT :snowman:

What a start to the year! Lido governance in January was focused on organisational restructuring, LEGO council member’s changes and decisions on the Node Operators’ participation following acquisitions. Furthermore, positive on-chain voting allowed the Community Staking Module to transition to a permissionless phase, accompanied by operational adjustments to the Node Operator naming conventions.

During the first 2025 month, in total, there were 20 governance votings across all platforms:

Voting platform # of votings
On-chain (prev. Aragon) 1
Snapshot 5
Easy Track 14

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

image
image1920Ă—1078 122 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 #183
Vote: Yes

Voting summary
  • About: This vote is aimed to:
  1. enable Permissionless Phase of Community Staking Module by activating public release and increasing the share limit from 1% to 2%.
  2. Rename Node Operator BridgeTower to Solstice following their acquisition.
  • Voting platform: On-chain Lido DAO Voting UI
  • Reasoning: The first of the suggested to implement was earlier supported via Snapshot (1), and another is an operational change to align the Node Operator naming (2). This vote will enact the supported proposals on-chain.

SNAPSHOT

LEGO: Proposal to replace Tim Beiko with Eric Siu and update council members rotation rules
Vote: For

Voting summary
  • About: Tim Beiko asked to be rotated for potential other candidates in LEGO council. It is proposed to replace him with Eric Siu, the Ecodev Coordinators team at the Ethereum Foundation (EF).
  • Voting platform: Snapshot
  • Reasoning: Tim will be truly missed, but it’s nice to see such a good replacement. Eric has experience with grant revision, as well as he appreciates Lido role within the broader Ethereum ecosystem.

Establishment of Lido Ecosystem BORG Foundation as a Lido-DAO-Adjacent Foundation
Vote: Support the proposal

Voting summary
  • About: It is proposed to incorporate the Lido Ecosystem BORG Foundation that supports Lido DAO’s goals by fostering institutional and ecosystem growth. The proposal specifies benefits of this foundation and what committees and multisigs will be wrapped within it from its inception. No funding is requested in this proposal.
  • Voting platform: Snapshot
  • Reasoning: Similar to Lido Alliance BORG and Lido Labs BORG Foundation, this one will also support the goals set by the Lido DAO in the field of enabling ecosystem growth to increase the adoption of Lido protocol and stETH, with a core focus of addressing and meeting institutional requirements. This is important and one of the goals within GOOSE-2, so support enabling its successful delivery.

Establishment of Lido Labs BORG Foundation as a Lido-DAO-Adjacent Foundation
Vote: Support the proposal

Voting summary
  • About: It is proposed to incorporate the Lido Labs BORG Foundation that supports Lido DAO’s goals by fostering research, development, deployment and facilitating maintenance of the Lido protocol, smart contracts, applications and infrastructure. The proposal specifies benefits of this foundation and what committees and multisigs will be wrapped within it from its inception. No funding is requested in this proposal.
  • Voting platform: Snapshot
  • Reasoning: A new BORG will serve Lido DAO and the broader Lido community, allowing Lido DAO to have a more active role in its governance and minimize reliance on traditional decision-making processes and rules. Foundation is limited to engage only in the activities identified in the purposes, bringing solid benefits of additional accountability and transparency, easier compliance and reducing potential liability risks of Lido contributors.

Should Attestant continue in the Curated set following the acquisition by Bitwise?
Vote: For

Voting summary
  • About: Node operator Attestant was acquired by Bitwise.This proposal seeks suggest the DAO to decide whether or not to allow Attestant as a part of Bitwise to continue Node Operations in Lido on Ethereum Simple DVT as-is.
  • Voting platform: Snapshot
  • Reasoning: According to Attestant, the infrastructure and geographical location will remain unchanged. The only change is in their ultimate shareholder, so no reason to cease their operator’s participation in Lido on Ethereum Curated set.

Should Solstice continue in the Curated set following the acquisition of Bridgetower?
Vote: For

Voting summary
  • About: Node Operator Bridgetower was acquired by Solstice Staking AG, a Swiss public limited company and Deus X Capital Enterprise company. This proposal seeks suggest the DAO to decide whether or not to allow Solstice to continue Node Operations in Lido on Ethereum Curated set.
  • Voting platform: Snapshot
  • Reasoning: Bridgetower validator operations (infra, people, geographic distribution and jurisdictional location) remain the same as per their forum post (the only thing that changes is the Node Operator’s name to “Solstice” to align naming), so no reason to stop their participation in both Lido on Ethereum Curated set.

EASY TRACK

There were 14 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 :relieved_face:

February report is on the way…

11

FEBRUARY VOTINGS REPORT :heart_hands:

Tbh, February was an easy one for all the Delegates and LDO tokenholders. During it, in total there were 12 governance votings across all platforms (spoiler: all of them were on Easy Track):

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

EASY TRACK

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

What is Easy Track and why are there so many motions each month?

The Easy Track (https://easytrack.lido.fi/) has been developed as a mechanism to assist with routine and uncontentious governance proposals for the Lido DAO. Only authorized addresses can start the Easy Track motion (a voting within Easy Track) and usually, this role is granted to the committee multisig. Some examples of a motion are Node Operators increasing staking limits, Funds being allocated to the LEGO program, and Funds being allocated to reward programs.

Easy Track motions are cheaper and easier to manage. A motion is considered to have passed if the minimum objections threshold (0.5% of the total token supply) hasn’t been exceeded.

An Easy Track motion lasts 72 hours, and the objections threshold is 0.5% of the total token supply.

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 :relieved_face:

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 spring and Pectra around the corner, I have a gut feeling that this March will be really h🥵t. See you next month!

3 Likes