# Ignas Delegate Thread

**URL:** <https://research.lido.fi/t/ignas-delegate-thread/8135>\
**Category:** Delegate Platform\
**Created:** [August 16, 2024, 11:59am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135 "2024-08-16T11:59:03Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [August 16, 2024, 11:59am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/1 "2024-08-16T11:59:03Z")

</div>

## Contact Information

**Name** : Ignas  
**Address** : ignasdefi.eth / 0x3DDC7d25c7a1dc381443e491Bbf1Caa8928A05B0  
**Twitter** : @DefiIgnas

## Introduction

First and foremost, I’m an active DeFi user and independent researcher. I share my findings and thoughts on X and my personal blog.

I’m also the co-founder of Pink Brains DeFi Creator Studio, which focuses on elevating quality projects through authentic representation.

## Motivation

Currently, DeFi DAOs face several internal issues, such as voter apathy leading to governance attacks, insider voting, and voting concentration among a few active voting addresses. Additionally, they face external challenges like regulatory uncertainty.

I believe in a decentralized future, even if it seems naive. However, the current state of crypto is plagued by misaligned incentives that prioritize short-term speculative gains over the core DeFi values of self-sovereignty and custody.

Equally concerning is the trend of McKinsification in DAOs, where decisions are increasingly made by one or two professional consultant delegates. This discourages individual participation, as their opinions and votes have less impact.

To make DeFi DAOs viable, we must align incentives to encourage active participation in governance from the broader crypto community.

I see potential in Lido DAO’s incentivized delegation approach. It creates career opportunities for individual delegates while strengthening and decentralizing DAOs, making them less prone to corruption.

## Values and Decision-Making Approach

Community must be at the core of every DAO.

Without giving the community a say in protocol governance, we’re no better than the Web2 companies we aim to replace—companies that view their “community” merely as users to extract value from.

I will support initiatives that align token holders with the protocol, such as revenue sharing or other methods to bring value to the token.

Token holders are frustrated with exploitative tokenomics that only benefit early insiders who acquired tokens at much lower prices, leaving no upside for new investors. Without incentives to buy and hold tokens, the attractiveness and health of DAOs decline.

Finally, I will highlight key votes and decisions of the DAO on X and my blog, as I believe the general public is often unaware of important actions being taken.

## Public Acceptance

I accept Lido’s Public Delegate Code of Conduct and our Public Delegate Platform signals my alignment with the mission, vision, and purpose of Lido DAO.

## Disclosures

I am the co-founder of Pink Brains at https:// pinkbrains. io, a DeFi creator studio dedicated to promoting DeFi projects through educational content. You can find the full list of projects we have worked on at our landing page.

I plan to apply as a delegate to other DAOs too, with the same mission of strengthening them and aligning token holders with the protocol.

I always make appropriate disclosures and recuse myself from voting when necessary.

Note: I could not add links as my account is new and will update this post when sharing links is allowed.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [October 9, 2024, 8:03am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/2 "2024-10-09T08:03:10Z")

</div>

Hi everyone! We’ll be sharing our votes and the reasoning behind them in this thread!

1. **Proposal** : [**Increase the Proposal Threshold for Snapshot**](https://snapshot.org/#/lido-snapshot.eth/proposal/0x185d0f90a82fd60c292bd6af34c136556859cc168b373cdf9c769b26f8e42b7b)

- **Vote** : Do nothing
- **Rationale** : As a new delegate on Lido, what I truly want to contribute is a decentralized future in the DAO, where every voice can raise their concerns—not just the voices of large holders.  
That’s why I’ll be voting “do nothing” on this proposal. I agree with Jenya\_K that spam isn’t a real issue on Snapshot. Plus, raising the threshold will unintentionally widen the gap between small and large token holders, which could make us lose valuable potential members.🙂  
Let’s let Lido continue doing what they’ve been doing so far, and I’m so impressed with the operations team’s management to date!

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [October 9, 2024, 8:08am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/3 "2024-10-09T08:08:56Z")

</div>

1. **Proposal** : [**Change Easy Track limits for PML & ATC**](https://snapshot.org/#/lido-snapshot.eth/proposal/0x44bc7db53129ab4048c7f6f5cdc03407ec73444cbb5976c9579cb19bd3b57f7e)

- **Vote** : Support the change
- **Rationale** : I support to change as it ensures that the funding limits for PML and ATC are better aligned with our current operational needs.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [October 9, 2024, 8:11am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/4 "2024-10-09T08:11:06Z")

</div>

1. **Proposal** : [**Lido Community Staking Module Mainnet Release Setup**](https://snapshot.org/#/lido-snapshot.eth/proposal/0xd0d7bfd68f2241524dbb14ae6fe0e8414b9fe3e0dcfc50641a8d28f0067d6693)

- **Vote** : Approve CSM mainnet release
- **Rationale** : I think we can move forward with this proposal to launch CSM on mainnet! The permissionless staking feature is really amazing—it lets anyone join staking without needing approval, as long as they have ETH or stETH. This makes staking open to more people, helps decentralize the network, and makes everything more fair and secure.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [October 10, 2024, 7:27am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/5 "2024-10-10T07:27:58Z")

</div>

1. **Proposal** : [**Vote #179**](https://vote.lido.fi/vote/179) (Onchain)

**Upgrade wstETH on Optimism bridge endpoints to enable rebasable stETH on Optimism alongside wstETH**

- **Vote** : Yes
- **Rationale** : I support this proposal because it will make stETH available on Optimism, helping Lido reach more users on cheaper and faster networks. This upgrade makes staking easier and more accessible for users, bringing more people to Lido. Adding both stETH and wstETH gives users more options and a better experience. So thinking of testing this on Optimism first is a smart way to make sure everything works well, then we can consider to expand to other networks.

**Add Easy Track setup for funding the Lido Alliance Operational Multisig following the Lido DAO Snapshot decision**

- **Vote** : Yes
- **Rationale** : I support the proposal and I think using Easy Track will give Lido DAO the power to approve spending, ensuring our budget is used clearly and with community oversight.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [October 22, 2024, 11:07am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/6 "2024-10-22T11:07:17Z")

</div>

**Date Voted:** October 22, 2024

**5. Proposal:** [Should the Lido DAO recognize the wstETH bridge endpoints on Zircuit as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0xac55c2cd8610c3b72cb769cec6b97891b5880f2f1f458eda2eb17218332cef6f) (Snapshot)  
**- Vote:** Recognize  
**- Rationale:** I vote to recognize the wstETH bridging endpoints for Zircuit. If it’s passed, it will allow users to securely transfer wstETH between Ethereum and Zircuit, boosting liquidity and making wstETH more useful on a secure Layer 2 network like Zircuit.

**6. Proposal:** [Integrate CSM into the Decentralized Validator Vault](https://snapshot.org/#/lido-snapshot.eth/proposal/0xcfb3473f8b91f368cc90218823d490c2a75ef4849bd76e000941d46b263f129c) (Snapshot)  
**- Vote:** Yes, vote for the integration  
**- Rationale:** I support the integration. It’s great to see solutions that enhance the staking experience while promoting decentralization in the Lido protocol like this :). Moreover, it will make it easier for newcomers to DeFi, especially those moving from Web2 to Web3, to stake ETH in the DVV and participate in CSM without needing technical expertise.

**7. Proposal:** [Lido Alliance application: Bolt](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2676108832842e60ca27aa7060b9ca6c09c6d2a9fe308b0ee0decc7a6728e137) (Snapshot)  
**- Vote:** Onboard Bolt to the Lido Alliance  
**- Rationale:** I vote to onboard Bolt to the Lido Alliance. Chainbound has proposed a detailed solution to improve user experience and enhance Lido’s security through preconfirmations. There’s no reason to block this integration.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [October 24, 2024, 11:01am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/7 "2024-10-24T11:01:50Z")

</div>

**8. Proposal:** [Vote #180](https://vote.lido.fi/vote/180) (Onchain)

**Date Voted:** October 24, 2024

**Add Community Staking Module to the Staking Router**  
**- Vote:** Yes  
**- Rationale:** As I mentioned in the Snapshot with “ [Integrate CSM into the Decentralized Validator Vault](https://snapshot.org/#/lido-snapshot.eth/proposal/0xcfb3473f8b91f368cc90218823d490c2a75ef4849bd76e000941d46b263f129c)”, CSM will help Lido bring in new stakers, even those who aren’t too familiar with the technical side.

**Staking Router and related contracts upgrade**  
**- Vote:** Yes  
**- Rationale:** I think upgrading the staking router also makes sense, ensuring compatibility with CSM and improving overall efficiency.

**Rotating the Instadapp Oracle address**  
**- Vote:** Yes  
**- Rationale:** This is also a smart move to boost efficiency and security for the Lido system. It will help protect users from potential risks and enhances overall safety for everyone involved.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [November 22, 2024, 2:04pm UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/8 "2024-11-22T14:04:33Z")

</div>

**Date Voted:** November 22, 2024

**9. Proposal:** [Establish the Network Expansion Committee (NEC)](https://snapshot.org/#/lido-snapshot.eth/proposal/0x7cdf1af7cfeb472ae202c45fb6d7e952bb34bfcbc82113549986b2bc2d5f54c5) (Snapshot)

- **Vote:** Approve NEC
- **Rationale:** I support this proposal. I believe creating NEC will help Lido scale faster, streamline processes, and reduce human error.

**10. Proposal:** [Should Pier Two continue in the Curated Module Set following the acquisition of Numic?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x7fd7879a945ebf95709bb0f5d0679370a06d6d0289b832ef8a100f983373e242) (Snapshot)

- **Vote:** For
- **Rationale:** After going through all the details provided by LNOSG, I believe Pier Two should continue their work.

**11. Proposal:** [Should Alchemy continue in SDVT and LoP following the acquisition of Bware Labs?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x89bf9f39d623ae2e6d1f876f345f59aaecb2cc4c6eec613e3385a5342dc08fa5) (Snapshot)

- **Vote:** For
- **Rationale:** I think LNOSG did a great job evaluating the transition and ensuring there won’t be any disruption in node operations after Alchemy took over Bware Labs. Given that, I believe Alchemy should definitely continue their work as planned.

**12. Proposal:** [Should Nansen continue in SDVT following the acquisition of Stakewithus?](https://snapshot.org/#/lido-snapshot.eth/proposal/0x8fb167fd8b923fb50627d959a603a95135ca05e18da9fd105d17079c14fba702) (Snapshot)

- **Vote:** For
- **Rationale:** I voted “For” because I believe LNOSG did a thorough evaluation, and keeping Nansen involved makes sense since there are no major changes.

**13. Proposal:** [Reevaluation of Lido on Polygon state](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2f745cb0147791cf656ab292f872f8277ff9df5c9585dbc6622dbda88362d402) (Snapshot)

- **Vote:** Sunset Lido on Polygon
- **Rationale:** This is a tough decision, but I agree Lido should focus on its core operations like Ethereum, where they has strong growth and community support. Spreading resources too thin on areas that aren’t showing much value or adoption isn’t sustainable.  
Although polygon has potential with recent ecosystem growth or zkEVM developments, the costs in liquidity incentives or audit expenses and other costs are higher than the returns. So, I vote to “sunset Lido on Polygon” and focus on core activities to minimize financial losses.

**14. Proposal:** [GOOSE 2024 cycle: Lido DAO goals for 2025](https://snapshot.org/#/lido-snapshot.eth/proposal/0xeedef9fea3d782f192410768cabaf6974da40ef36e1d22c7f8fff5fd4cfc7a59) (Snapshot)

- **Vote:** Adopt Goals
- **Rationale:** Voted to adopt the goals on Snapshot. I’ve shared my thoughts in the forum discussion [[Hasu's GOOSE-2 Submission] A Product Line Approach to Grow Lido’s Staking Ecosystem - #14 by Ignas](https://research.lido.fi/t/hasus-goose-2-submission-a-product-line-approach-to-grow-lido-s-staking-ecosystem/8841/14), and I’m looking forward to seeing the actions unfold next year!

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [November 28, 2024, 3:33am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/9 "2024-11-28T03:33:23Z")

</div>

**15. Proposal:** [Vote #181W](https://vote.lido.fi/vote/181) (On-chain)

- **Date Voted:** November 27, 2024

**Change Easy Track limits for PML and ATC**

- **Vote:** Yes
- **Rationale:** Same reason with snapshot vote, I support to change as it ensures that the funding limits for PML and ATC are better aligned with our current operational needs.

**Increase the Lido Stonks stETH limit to 12,000 stETH and reset spent amount**

- **Vote** : Yes
- **Rationale:** I voted in favor because I believe it strikes the right balance. Raising the stETH limit to 12,000 will give Lido enough stable capital to cover ongoing needs while still making the most of our staked assets.

**Update the reward address**

- **Vote:** Yes
- **Rationale:** I agree that its important to keep Node Operator info up-to-date with the correct format.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [December 18, 2024, 7:12am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/10 "2024-12-18T07:12:17Z")

</div>

**Date Voted:** December 17, 2024

**16. Proposal:** [CSM: Enable Permissionless Phase and Increase the Share Limit](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7cbd5e9cb95bda9581831daf8b0e72d1ad0b068d2cbd3bda2a2f6ae378464f26) (Snapshot)

- **Vote:** For

- **Rationale:** More Node Operators through CSM is a great way to decentralize Lido, as control won’t be concentrated in the hands of just a few 🙂

**17. Proposal:** [Lido Alliance Grant Proposal](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7569e4487b7737fa8e98fe708843deb014a61d0dbfeeb6e57ad1f4dba5494598) (Snapshot)

- **Vote:** For

- **Rationale:** Lido Alliance is one of the coolest things to come out of Lido recently 🙂

**18. Proposal:** [[EGG] Multi-EGG Continuity Grant Funding](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x8736420fd3ebecc1aae603c3a49d6805899c38b142c92525169e5bfa95f53b26) (Snapshot)

- **Vote:** For
- **Rationale:** Seeing the key technical goals we’ve discussed are moving forward and will help strengthen the ecosystem long-term. With that reason in mind, I voted **For** on Snapshot.

**19. Proposal:** [Extend On-Chain Voting Duration](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xa58da73cc4257837ae981d8ad861252f4cbbda7a173a577702f8f93561f57825) (Snapshot)

- **Vote:** Extend duration to 3+2 days

- **Rationale:** As for my [previous comment](https://research.lido.fi/t/optimizing-lido-on-chain-voting-timelines-for-inclusive-governance/8265/16), I don’t think the low participation and quorum unmet are solely due to the short onchain voting period. Instead, we should take action to notify people when proposals go live, like setting alerts or keeping active. I understand it’s tough for those busy with conferences, but the operation team has done a great job managing the community and keeping everyone updated on upcoming proposals.

**20. Proposal:** [Update Lido on Ethereum Standard Node Operator Protocol - Validator Exits](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x969f9a3b3f52742b9763d8e128f2418a0ce888433e130a60f7fef809787ffdb4) (Snapshot)

- **Vote:** For
- **Rationale:** I believe these changes will make the system more stable and efficient, while also helping Node Operators follow the process and avoid violations. Voted **For**.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [December 19, 2024, 9:13am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/11 "2024-12-19T09:13:29Z")

</div>

**21. Proposal:** [Vote #182](https://vote.lido.fi/vote/182) (On-chain)

- **Date Voted:** December 18, 2024

**Change Easy Track limits for PML and ATC**

- **Vote:** Yes
- **Rationale:** Same reason with previous votes (Snapshot and on-chain), I support to change as it ensures that the funding limits for PML and ATC are better aligned with our current operational needs.

**Increase the Lido Stonks stETH limit to 12,000 stETH and reset spent amount**

- **Vote** : Yes
- **Rationale** : Increasing the stETH Stonks limit to 12,000 stETH gives Lido DAO more stablecoins to fund their operations. Moreover, the proposal also helps Lido keeps liquidity steady and makes managing funds easier.

**Update the reward address for Node Operator**

- **Vote** : Yes
- **Rationale** : Same reason with previous vote, I agree that its important to keep Node Operator info up-to-date with the correct format.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [January 27, 2025, 5:43am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/12 "2025-01-27T05:43:39Z")

</div>

**Date Voted:** January 26, 2025

**22. Proposal:** [Should Solstice continue in the Curated set following the acquisition of Bridgetower?](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x93baeaa1b3e3ed31df27dc5dbbb729cc562d6766513b01ef59ec8f362d45edd5) (Snapshot)

- **Vote:** For

- **Rationale:** I don’t see any issues with the acquisition. There’s no change to the validator operations, and Solstice has made it clear they’re ready to keep things running smoothly after the takeover.

**23. Proposal:** [Should Attestant continue in the Curated set following the acquisition by Bitwise?](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x58fc14fac3bcdf65c7b9dd871ec555da8c2ff6387b9a443ddf5fce5f41d4db91) (Snapshot)

- **Vote:** For
- **Rationale:** I support Attestant continuing in the Curated set after being acquired by Bitwise. There’s really no reason to stop their participation in Lido’s Curated set, everything remains the same, and they’ve confirmed no changes to their operations.

**24. Proposal:** [Establishment of Lido Labs BORG Foundation as a Lido-DAO-Adjacent Foundation](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xdf648307e68415e7b5cf96c6afbabd696c1731839f4b4a7cf5cb7efbc44ee9d6) (Snapshot)

- **Vote:** For

**25. Proposal:** [Establishment of Lido Ecosystem BORG Foundation as a Lido-DAO-Adjacent Foundation](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7f72f12d72643c20cd0455c603d344050248e75ed1074c8391fae4c30f09ca15) (Snapshot)

- **Vote:** For

**Rationale (24,25):**  
The BORG model clearly addresses the limitations of ATC/PML: scalability, high costs, and legal constraints.

Using BORG brings more transparent and efficient governance with a clear legal structure while reducing financial pressure.

This allows DAOs to focus better on long-term strategies.

I know a few DAOs considered (or implemented) a similar governing body.

At the end of the day the DAO cannot run day to day operations - Less decentralization for the sake of efficiency.

So with this move, hope BORG can make the DAO more efficient.

Lido is in the scaling, war mode. Let’s go for it 🙂

**26. Proposal:** [LEGO: Proposal to replace Tim Beiko with Eric Siu and update council members rotation rules](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x2acd7e052fc5ac2513509f5023975451f69fd488628577fedf369c3da97bef6a) (Snapshot)

- **Vote:** For
- **Rationale:** I support replacing Tim Beiko with Eric Siu on the LEGO Council. Eric has great experience connecting organizations within the Ethereum ecosystem, and I believe he’ll bring valuable insights to the DAO.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [January 30, 2025, 1:59am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/13 "2025-01-30T01:59:13Z")

</div>

**27. Proposal:** [Vote #183](https://vote.lido.fi/vote/183) (On-chain)

- **Date Voted:** January 29, 2025

**Transition Community Staking Module to Permissionless Phase** by activating public release and **increasing the share limit** from 1% to 2%. Alongside the share limit, it is proposed to **raise the priority exit share threshold** from 1.25% to 2.5% to maintain parameter ratios.

- **Vote:** Yes

- **Rationale:** I support the change with same reason on Snapshot vote.  
More Node Operators through CSM is a great way to decentralize Lido, as control won’t be concentrated in the hands of just a few 🙂

**Rename Node Operator ID 17 from BridgeTower to Solstice**

- **Vote:** Yes
- **Rationale:** I support approving rename Node Operator ID 17 from BridgeTower to Solstice

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [March 19, 2025, 11:30am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/14 "2025-03-19T11:30:42Z")

</div>

**Date Voted:** March 19, 2025

**28. Proposal:** [SSV Lido Module Proposal](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x97e858cf28d8287bf268948e71e98bcd7b5b96a75f596260d0c614185b2ef237) (Snapshot)

- **Vote:** For

- **Rationale:** Very detailed proposal. Even though it’s quite technical, I get why SSVLM is important.

**29. Proposal:** [Lido DAO Ops Multisigs Policy 2.0](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x48e552d0dab3d49f72f8618302a68be56afbdfef0d0e7bcf9f73588335d2842b) (Snapshot)

- **Vote:** For

- **Rationale:** This proposal is really important for Lido. With the multisig wallet hacks happening, it’s a good to make things more transparent, secure, and efficient for Lido.

**30. Proposal:** [MEV-Boost Relay Allowed List management via Easy Track](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf1074ec134595ba8ba6f802c5e505fda32e6ab93e9763d1e43001f439241b7c9) (Snapshot)

- **Vote:** For

- **Rationale:** A yes from me.

**31. Proposal:** [[EGG] Lido Labs BORG Foundation Grant Funding Request (Apr-Dec 2025)](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xb58527a05581849b3890ff226fa30f2b5e19f7742fe8f4f94e6c953fe0055c0e) (Snapshot)

- **Vote:** For

**32. Proposal:** [[EGG] Lido Ecosystem BORG Foundation Grant Funding Request (Apr-Dec 2025)](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x90e2f9926e37867d2ef319a8ef7a0257bb5695086b64b88b43b43f00959a0047) (Snapshot)

- **Vote:** For

**Rationale for 31,32:** These are good steps to keep strengthening our position as the #1 staking player by expanding and upgrading its system.

Well, the value of LDO depends on Lido’s growth and community engagement, so as a delegate, I have no reason to oppose this. Shoutout to the team for the great work!

That said, I think the budget is quite large, 45.49M in total. And I also noticed that from April to December 2025, there aren’t many details on how the funds will be used beyond broad goals. So I think a detailed financial report each quarter would be helpful for transparency and tracking progress.

**33. Proposal:** [Ensuring Compatibility with Ethereum’s Pectra Upgrade](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xb6559f0cdb1164ae5d63769827c4a275805bd944392a17b60cf51ddc54429dc6) (Snapshot)

- **Vote** : For

- **Rationale:** Good to see the DAO proactively preparing for Ethereum’s upgrades. I believe this will strengthen trust with users and validators within Lido ecosystem.

**34. Proposal:** [Vote #184](https://vote.lido.fi/vote/184) (Onchain)

**“Extend On-Chain Voting Duration ”**

- **Vote:** Yes

- **Rationale:** Sticking my reason with Snapshot vote. Again, I don’t think the low participation and quorum unmet are solely due to the short onchain voting period. Instead, we should take action to notify people when proposals go live, like setting alerts or keeping active.

**“Deploy Easy Track Factories for Lido Ecosystem & Lido Labs BORG Foundations to streamline operational funding ”**

- **Vote:** Yes
- **Rationale:** Easy Track Factories can automate budget distribution, make on chain transactions less complicated while keeping the process clear and transparent.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [April 1, 2025, 9:09am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/15 "2025-04-01T09:09:49Z")

</div>

**35. Proposal:** [Re-endorsement of wstETH on Starknet](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf752b2dbc9cf8693abf01b29938d7f7e0dd7e1ebe088583fd61da7641b870a36) (Snapshot)

- **Date Voted:** March 27, 2025

- **Vote:** Against

- **Rationale:** I voted against this proposal. The Network Expansion Committee (NEC) has already decided to off-board wstETH on Starknet due to governance transfer issues that made the token irreversibly ownerless and non-upgradeable. This decision aligns with Lido’s bridging guidelines.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [April 23, 2025, 3:36am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/16 "2025-04-23T03:36:21Z")

</div>

**Date Voted:** April 22, 2025

**36. Proposal:** [Increasing LOL Easy Track Limits to align with Grant Requests](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x3ecd09e4c0f22d25c711ca5777c49c22d144385b85dd7f696ca6cc66cc0ca157) (Snapshot)

- **Vote:** For

- **Rationale:** I’m voting yes on Snapshot. This isn’t a new funding request, its a technical tweak to help the Liquidity Observation Lab get the funds that were already approved.

**37. Proposal** : [CSM: stakeShareLimit and keyRemovalCharge parameters adjustment](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xcd1c1a051888efd495d97458ae9fa4fe5198616eb3d92a71d3352d9f25e79c4e) (Snapshot)

- **Vote:** For

- **Rationale:** These changes make sense given the current situation. Lido can activate ~50 new Node Operators if the limit is raised to 3%, which will help diversify and decentralize the network on Ethereum.

**38. Proposal:** [Lido Alliance application: Twyne](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xc67103e65d8bb4e088ddb89e0a7654fa56db5f0162f5870fca41c5dabd937f11) (Snapshot)

- **Vote:** For

- **Rationale:** Big thanks to Nemo from the Lido Alliance for the detailed breakdown of this proposal, including the risk aspects regarding the team and security. Really appreciate the effort!

**39. Proposal:** [Extend Delegate Incentivization Program through 2025](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x2533d8d3903d94daa4de16ef7abf957441439e7867962ce8709a375479f417de) (Snapshot)

- **Vote:** For

- **Rationale:** I’m happy to support this program. It’s a good way to keep delegates engaged and aligned with the DAO’s long-term goals.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [April 25, 2025, 11:12am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/17 "2025-04-25T11:12:23Z")

</div>

**40. Proposal:** [Vote #185](https://vote.lido.fi/vote/185)

- **Date Voted:** April 24, 2025

**“Ensure Compatibility with Ethereum’s Pectra Fork”**

- **Vote:** Yes

- **Rationale:** Voted yes with same reason on snapshot. I believe this will strengthen trust with users and validators within Lido ecosystem.

**“Update CS Verifier Contract on the Community Staking Module”.**

- **Vote:** Yes

- **Rationale:** I support the removal of the slashing report functionality and the update to the gIndexes structure in the CSM!

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [May 14, 2025, 7:26am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/18 "2025-05-14T07:26:29Z")

</div>

**41. Proposal:** [Vote #186](https://vote.lido.fi/vote/186) (Onchain)

- **Date Voted:** May 11, 2025
- **Vote:** Yes
- **Rationale:** This is a necessary and well coordinated mitigation. Good to see the oracle rotation moving swiftly and transparently, with no impact on stakers or protocol integrity.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [May 23, 2025, 7:29am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/19 "2025-05-23T07:29:18Z")

</div>

**Date Voted:** May 22, 2025

**42. Proposal:** [Community Staking Module v2. Architecture and Fee Structure](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf7b718e7807f763ba826735781145dd06b79b0228b37b74a22dd5ac252e03c40) (Snapshot)

- **Vote:** Yes

- **Rationale:** CSM v2 can address key limitations of v1, including the lack of operator differentiation, the inability to penalize consistently underperforming validators, and the risk of exploitation by large operators due to the fully permissionless design.

**43. Proposal:** [Establishment of the Auxiliary Proposer Mechanisms Committee](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf7630cd2bfe47e892f8293cd68be277fefc33ba19f43c756747fe1113456ac4b) (Snapshot)

- **Vote:** Yes

- **Rationale:** Proposer layer innovation is evolving rapidly, having an APM Committee will position Lido to not just keep up, but lead in safely adopting these new mechanisms.

**44. Proposal:** [LIP-28: Dual Governance — Implementation, Parameters, Committees](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x26a66c9b91ff46aeac74b6f6714467993edc6840a8f292fb5c1366fc44dec2a6) (Snapshot)

- **Vote:** Yes

- **Rationale:** Some of these parameters might seem confusing at first, but Dual Governance can actually make Lido stronger and more stable long term.

**45. Proposal:** [Vote #187](https://vote.lido.fi/vote/187) (Onchain)

- **Vote:** Yes
- **Rationale:**

**For “Post-Pectra update: adjust Oracle Report Sanity Checker parameters to align with reduced slashing penalty and updated validator churn limits.”**  
 → Support the proposal with same reason on Snapshot vote. I believe this will strengthen trust with users and validators within Lido ecosystem.

A two phase approach can ensure a smooth and secure transition, minimizing risks before the hardfork.

Lastly, keeping Lido aligned with Pectra will lay the groundwork for future Ethereum upgrades.

**For “ Add Easy Track Factories for managing MEV-Boost Relay Allowed List”**  
 → Voted in favor onchain. With Easy Track, changes will be faster and more efficient.

Also, the new system updates the list quickly and accurately, helping to keep the protocol stable and efficient. Node operators can rely on relays with confidence, improving staking performance and Lido’s overall returns.

**For “ Reduce keyRemovalCharge for the Community Staking Module.”**  
 → Voted yes. Lido can activate ~50 new Node Operators if the limit is raised to 3%, which will help diversify and decentralize the network on Ethereum.

Also lowering the keyRemovalCharge from 0.05 → 0.02 ETH will remove a barrier for smaller or newer operators joining CSM.

**For “Increase Easy Track security limit for Liquidity Observation Lab from 2,100 stETH per 3 months to 6,000 stETH per 6 months.”**  
 → Voted in favor with same reason on Snapshot. This isn’t a new funding request, its a technical tweak to help the Liquidity Observation Lab get the funds that were already approved.

---

<div class="post-metadata">

**Author:** ![Ignas](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/ignas/32/4798_2.png) [@Ignas](https://research.lido.fi/u/Ignas)\
**Post date:** [May 29, 2025, 9:50am UTC](https://research.lido.fi/t/ignas-delegate-thread/8135/20 "2025-05-29T09:50:13Z")

</div>

**46. Proposal:** [Vote #188](https://vote.lido.fi/vote/188) (Onchain)

- **Date Voted:** May 28, 2025
- **Vote:** Yes
- **Rationale:** This vote is a re run of vote #187, which did not reach quorum. The compliance and rationale for the proposal remain unchanged.

> [@Ignas](#):
>
> **For “Post-Pectra update: adjust Oracle Report Sanity Checker parameters to align with reduced slashing penalty and updated validator churn limits.”**  
> → Support the proposal with same reason on Snapshot vote. I believe this will strengthen trust with users and validators within Lido ecosystem.
> 
> A two phase approach can ensure a smooth and secure transition, minimizing risks before the hardfork.
> 
> Lastly, keeping Lido aligned with Pectra will lay the groundwork for future Ethereum upgrades.
> 
> **For “ Add Easy Track Factories for managing MEV-Boost Relay Allowed List”**  
> → Voted in favor onchain. With Easy Track, changes will be faster and more efficient.
> 
> Also, the new system updates the list quickly and accurately, helping to keep the protocol stable and efficient. Node operators can rely on relays with confidence, improving staking performance and Lido’s overall returns.
> 
> **For “ Reduce keyRemovalCharge for the Community Staking Module.”**  
> → Voted yes. Lido can activate ~50 new Node Operators if the limit is raised to 3%, which will help diversify and decentralize the network on Ethereum.
> 
> Also lowering the keyRemovalCharge from 0.05 → 0.02 ETH will remove a barrier for smaller or newer operators joining CSM.
> 
> **For “Increase Easy Track security limit for Liquidity Observation Lab from 2,100 stETH per 3 months to 6,000 stETH per 6 months.”**  
> → Voted in favor with same reason on Snapshot. This isn’t a new funding request, its a technical tweak to help the Liquidity Observation Lab get the funds that were already approved.

[Next page](https://research.lido.fi/t/ignas-delegate-thread/8135.md?page=2)
