# Anthony Leuts - Delegate Thread **URL:** \ **Category:** Delegate Platform\ **Created:** [August 9, 2024, 2:45pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019 "2024-08-09T14:45:15Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [August 9, 2024, 2:45pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/1 "2024-08-09T14:45:15Z")
**Name:** Anthony L **Address:** leuts.eth (0x42E6DD8D517abB3E4f6611Ca53a8D1243C183fB0) **Forum:** [@leuts](https://research.lido.fi/u/leuts/summary) **Twitter:** [Leuts](https://x.com/A_Leutenegger) **Introduction:** I am the CEO of Aragon. Previously a contributor at Vocdoni. I am an LDO holder and Lido DVT Simple Home Staker. My expertise is in onchain governance technology. I am a University of Waterloo alumni. **Motivation:** Lido is the most important project in web3, with the most at stake ;). As a long term partner, supporter, token holder, and user I am happy to put myself forward as a delegate to the Lido DAO to help support and secure the Ethereum network. **Values and Decision-Making Approach:** The future of humanity will be decided at the frontier of technological innovation and human coordination. We will either see deeper levels of censorship and oppression, or new and greater amounts of freedom. Lido has the power, capability, and responsibility to change the world by securing Ethereum and supporting the latter and as a delegate at Lido my goal will be to ensure Lido stays true to its mission, vision, and to uphold its values. Thus my approach is to ensure the Lido DAO: Keeps Ethereum decentralized, accessible to all, and resistant to censorship and do this by supporting making staking simple, secure, and decentralized. I’ll do this by communicating openly and focusing on being pragmatic in my decision making. **Public Acceptance:** I accept Lido DAO delegate Сode of Сonduct ([link](https://ipfs.io/ipfs/QmPwqjn5NiNVFKjxxBnYHivgempeyNNpMNotGYMCXitRd3)) and Aligned with [Lido’s Vibe (Purpose, Mission, Vision)](https://snapshot.org/#/lido-snapshot.eth/proposal/0x739fbe56425d355b5e41c22bb346b7a8217afd9e84aa49863648b1c641a482e3) **Disclosures:** I am the CEO of Aragon. I own LDO. I own an extremely small amount of shares in Diva now known as Nektar. I work in the onchain governance tooling space, our largest users include Lido, Curve, Polygon, and Taiko. **Waiver of Liability:** _By delegating to me, Anthony Leuts, you acknowledge and agree_ _to the following:_ 1. _I do not control_ _or represent_ _the DAO_ _or the LIDO project_ _and do not assume any responsibility_ _or liability_ _for_ _the DAO’s or LIDO’s_ _actions or decisions._ 2. _I do not take over any responsibilities of the DAO_ _or the LIDO project_ _, and my participation is limited to the role of a delegate._ 3. _I am not bound by any particular opinion when voting. Instead, I will vote in a manner that I believe is in the best interest of the_ _LIDO_ _project._ 4. _By delegating your vote to me, you grant me the freedom to vote at my discretion with your delegation_ _, which means_ _you have no right to restrict me in forming my opinions or in how I cast my votes_ _._ 5. _I disclaim any liability for any loss, damages, or claims arising from your delegation of votes to me, including but not limited to, unfavorable decisions of the DAO, lack of development of the LIDO project, or other unfavorable or unforeseen circumstances. By delegating votes to me, you fully understand and accept the risks associated with interacting with decentralized smart contracts._ 6. _All my activities and the relationship with you are exclusively subject to Swiss laws and Swiss courts._ ---
**Author:** ![kadmil](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/kadmil/32/1958_2.png) [@kadmil](https://research.lido.fi/u/kadmil)\ **Post date:** [August 13, 2024, 1:44pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/2 "2024-08-13T13:44:37Z")
Happy to see your proposal, ser, and doubly so given the continuous support of Lido DAO from Aragon team =) ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [August 14, 2024, 6:29am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/3 "2024-08-14T06:29:30Z")
Thank you! Looking forward to the continued success and bright future of Lido DAO and the Ethereum ecosystem. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [October 7, 2024, 3:38pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/4 "2024-10-07T15:38:59Z")
**Decision rationale on the last 3 votes:** ## 1. [Increase the Proposal Threshold for Snapshot](https://snapshot.org/#/lido-snapshot.eth/proposal/0x185d0f90a82fd60c292bd6af34c136556859cc168b373cdf9c769b26f8e42b7b) ### Vote: **Abstain** ### Rationale: I had no strong feeling on whether it should have been increased or not. I always lean toward not making change for the sake of making change. As the DAO Ops team did not report the spam being problematic, and already had an agreement with Snapshot to reduce these issues. I do not believe it was necessary. That being said, Lido’s requirement for putting up a vote is much lower and more open than most other DAOs in the industry. This has tradeoffs. I entrust the DAO Ops team to put up a proposal if they see this becoming a problem. I also voted before there was much feedback in the forum and the vote was live, thus I went with abstain. ## [2. Change Easy Track limits for PML & ATC](https://snapshot.org/#/lido-snapshot.eth/proposal/0x44bc7db53129ab4048c7f6f5cdc03407ec73444cbb5976c9579cb19bd3b57f7e) ### Vote: **Support the Change** ### Rationale: Based on the information provided [here](https://research.lido.fi/t/new-easy-track-motion-setups-with-limits-rcc-pml-atc-gas-funder-lego-rewards-with-limits/3264/10) and [here](https://research.lido.fi/t/new-easy-track-motion-setups-with-limits-rcc-pml-atc-gas-funder-lego-rewards-with-limits/3264/11) by Steakhouse it seems there is underspend meaning the changes are sensible. ## 3. [Lido Community Staking Module Mainnet Release Setup](https://snapshot.org/#/lido-snapshot.eth/proposal/0xd0d7bfd68f2241524dbb14ae6fe0e8414b9fe3e0dcfc50641a8d28f0067d6693) ### Vote: **Approve CSM mainnet release** ### Rationale: CSM continues to ship! As a user myself and with my team we are very pleased with the outcome of the program so far. Very happy to continue to see it flourish and grow. It perfectly fits Lido’s mission in decentralizing Ethereum and overlaps with the GOOSE goals put forward by Hasu. I am a big advocate for CSM at this stage! **Disclosures** : 1. None 2. None 3. I am a CSM user Thank you to @Lanski for providing a format for decision rationale! Much appreciated. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [October 11, 2024, 6:18am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/5 "2024-10-11T06:18:04Z")
## 1. [Vote #179](https://vote.lido.fi/vote/179) 1. Upgrade **wstETH on Optimism bridge endpoints** to enable **rebasable stETH** on Optimism alongside wstETH. Following Snapshot vote and proposed action plan. Solution audited by MixBytes and Ackee Blockchain. Items 1-5. 2. Add **Easy Track setup** for funding the Lido Alliance Operational Multisig following the Lido DAO Snapshot decision. Item 6. ### Vote: **Yes** ### Rationale: Both votes are non-contentious with near unilateral agreement across the DAO to vote yes. I see no reason to vote no. Audits are in order, standard procedure, and payload looks good. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [October 22, 2024, 11:33am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/6 "2024-10-22T11:33:21Z")
## 1. [Should the Lido DAO recognize the wstETH bridge endpoints on Zircuit as canonical?](https://snapshot.org/#/lido-snapshot.eth/proposal/0xac55c2cd8610c3b72cb769cec6b97891b5880f2f1f458eda2eb17218332cef6f) Forum post [here](https://research.lido.fi/t/wsteth-deployment-to-zircuit-and-ownership-acceptance-by-lido-dao/8602) ### Vote: **Yes** ### Rationale: Zircuit is a respected upcoming L2 with traction and high-TVL. Lido contributors have reviewed the code and offered suggestions for improvement, thus stamping their approval. ## 2. [Integrate CSM into the Decentralized Validator Vault](https://snapshot.org/#/lido-snapshot.eth/proposal/0xcfb3473f8b91f368cc90218823d490c2a75ef4849bd76e000941d46b263f129c) Forum post [here](https://research.lido.fi/t/integrate-csm-into-the-decentralized-validator-vault/8621) ### Vote: **Yes** ### Rationale: More ETH flow into CSM. More decentralized. Lindy is growing and thus safety. ## 3. [Onboard Bolt to Lido Alliance](https://snapshot.org/#/lido-snapshot.eth/proposal/0x2676108832842e60ca27aa7060b9ca6c09c6d2a9fe308b0ee0decc7a6728e137) Forum post [here](https://research.lido.fi/t/proposal-onboard-bolt-to-the-lido-alliance/7724/2) ### Vote: **Yes** ### Rationale: Preconfirmations were an integral part of the Alliance wishlist. This is a step forward in realizing this wishlist. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [December 20, 2024, 12:19pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/7 "2024-12-20T12:19:00Z")
## Aragon Onchain Votes: December 20, 2024 ## 1. [**Change Easy Track limits for PML and ATC**](https://vote.lido.fi/vote/182) Forum post [here](https://research.lido.fi/t/egg-st2024-v2-continuity-grant-funding-to-achieve-goose-goals/7697) ### Vote: **Yes** **Rationale:** In order to support the goals set by the Continuity Grant Funding initiative and adjust token flows that haven’t changed since 2022, it makes sense to alter these onchain parameters. ## 2. [**Increase the Lido Stonks stETH limit to 12,000 stETH and reset spent amount**](https://vote.lido.fi/vote/182) Forum post [here](https://research.lido.fi/t/tmc-4-increase-stonks-execution-limits/8616) ### Vote: **Yes** **Rationale:** Makes sense, the higher limits are in line with execution of TMC-1 and improve their operations. ## 3. [**Update the reward address**](https://vote.lido.fi/vote/182) Forum post [here](https://research.lido.fi/t/node-operator-registry-name-reward-address-change/4170/36) ### Vote: **Yes** **Rationale:** As requested in the forum. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [December 24, 2024, 1:23pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/8 "2024-12-24T13:23:55Z")
Just an update on my delegate thread updates: as I have no delegation via Snapshot I will no longer provide updates on Snapshot signalling. I don’t want to create more unnecessary noise that has no impact on anyone. I will continue to update my decisions and rationale here on Aragon onchain votes for now. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [March 16, 2025, 4:05pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/9 "2025-03-16T16:05:49Z")
Gm! An update: As I have received more delegation both offchain via Snapshot and onchain via Aragon I will once again begin providing rationale for both types of votes here in the forum. Looking forward to it and thank you to anyone who has entrusted their delegation in me. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [March 18, 2025, 6:58pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/10 "2025-03-18T18:58:48Z")
March 18 vote updates and reasoning: 1. **[Onchain Vote 184](https://vote.lido.fi/vote/184)**: **Optimizing Lido On-chain Voting Timelines for Inclusive Governance** **Vote: YES** I have reviewed the payload and all the onchain changes seem correct including the vote times. It’s important to note when reviewing that the TOTAL vote duration is 5 days (call data: 432000) and the objection period 2 days (172800). This is correct with the main phase being “full voteTime - objectionTime”. In relation to the social parameters of extending the vote duration, it makes sense. It was sadly too short before for voters to react and reach quorum. **Offchain Signals:** 1. **[# Lido DAO Ops Multisigs Policy 2.0](https://research.lido.fi/t/lido-dao-ops-multisigs-policy-2-0/9574)** **Vote: YES** This is a good start in increasing the security and opsec of the Lido DAO multisigs, however, I have followed-up with further [questions](https://research.lido.fi/t/lido-dao-ops-multisigs-policy-2-0/9574/12) as I believe there is room for improvement. 1. **[# SSV Lido Module Proposal](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x97e858cf28d8287bf268948e71e98bcd7b5b96a75f596260d0c614185b2ef237)** **Votes: YES** This should increase decentralizatiom both via an increase in permissionless participation as well as more robustness of the total validator set. Anytime we can reduce barriers to entry for independent stakers and smaller node operators is a net positive for the Ethereum ecosystem. 1. **[# MEV-Boost Relay Allowed List management via Easy Track](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf1074ec134595ba8ba6f802c5e505fda32e6ab93e9763d1e43001f439241b7c9)** As @polar said: “Streamlining and improving governance, what more could one ask for. FOR.” 1. **[# Ensuring Compatibility with Ethereum’s Pectra Upgrade](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xb6559f0cdb1164ae5d63769827c4a275805bd944392a17b60cf51ddc54429dc6)** **Vote: YES** Essential for Lido and Ethereum that Lido safely and securly is compatible with Ethereum’s Pectra Upgrade. This is a massive undertaking and proposal to review. I don’t even think many people can reasonably do this. Everything seems to make sense, and it’s being performed in a safe and staged way. 1. **[# [EGG] Lido Labs BORG Foundation Grant Funding Request (Apr-Dec 2025)](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xb58527a05581849b3890ff226fa30f2b5e19f7742fe8f4f94e6c953fe0055c0e)** **Vote: YES** 1. **[# [EGG] Lido Ecosystem BORG Foundation Grant Funding Request (Apr-Dec 2025)](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x90e2f9926e37867d2ef319a8ef7a0257bb5695086b64b88b43b43f00959a0047)** **Votes: YES** It’s essential the Lido BORGS are well funded to carry-on the mission of the Lido DAO. However, I would be remiss to note that these costs are exporbinant compared to any other project in web3. Lido is without question a leader, that generates revenue, and has high-costs due to the nature of it’s product and offering. Lido has to continue to not only be the leading liquid staking provider, BUT, it also has to take market share from centralized parties such as Coinbase that put Ethereum at risk. Finally it also needs to diversify and reach new markets for its own growth and sustainability. All that being said, I think it would be extremely wise to determine how to reduce costs where possible. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [April 1, 2025, 3:30pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/11 "2025-04-01T15:30:41Z")
I voted Against [Re-endorsement of wstETH on Starknet.](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf752b2dbc9cf8693abf01b29938d7f7e0dd7e1ebe088583fd61da7641b870a36) Poor incident response and weak retrospective. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [April 25, 2025, 10:32am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/12 "2025-04-25T10:32:03Z")
April vote updates and reasoning: ## [Aragon On-chain vote 185](https://vote.lido.fi/vote/185) Verification guide [here](https://hackmd.io/@lido/BJn9b91Jgl) ### Vote: Yes ### Rationale: Ensuring continued compatibility with Ethereum’s upcoming Pectra hardfork is essential and this is a first step in ensuring operability. I have reviewed the payload and verification guide and have voted yes. Thank you to the DAO Ops team for always providing incredible guides and information to ensure we have an easier time of verifying everything. **Snapshot Signals:** ## [Extend Delegate Incentivization Program through 2025](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x2533d8d3903d94daa4de16ef7abf957441439e7867962ce8709a375479f417de) Forum post [here](https://research.lido.fi/t/establish-a-public-delegate-platform-and-delegate-incentivization-program/7858/60) ### Vote: For ### Rationale: Disclaimer: I am a new delegate and have not financially benefited from this program to date. With this vote I may be eligible in the future for rewards for my work. I have provided more information [here](https://research.lido.fi/t/establish-a-public-delegate-platform-and-delegate-incentivization-program/7858/54) that I do not agree with all the changes to the program, however, I am not going to stop or halt the program for these minor recommendations seeing as in general the program is achieving its goals. I will consider being more forward and aggressive in the future about these recommendations based on another quarter of data and information. ## [Lido Alliance application: Twyne](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xc67103e65d8bb4e088ddb89e0a7654fa56db5f0162f5870fca41c5dabd937f11) Forum post [here](https://research.lido.fi/t/twyne-lido-alliance-proposal/9901) ### Vote: For ### Rationale: The project albeit extremely early seems promising and the conditions are very beneficial to Lido if they are successful. - 10% of Twyne’s token supply subject to a 1 year cliff and 2 years vesting - 50% revenue share on stETH pools where revenue share for Lido Alliance is primarily used for incentives and liquidity on Twyne They are also incubated and invested in by Euler, followed by Angel backing from names like Daedalus who are well known to the Ethereum ecosystem and have great track records. ## [CSM: stakeShareLimit and keyRemovalCharge parameters adjustment](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xcd1c1a051888efd495d97458ae9fa4fe5198616eb3d92a71d3352d9f25e79c4e) Forum post [here](https://research.lido.fi/t/community-staking-module/5917/104) ### Vote: For ### Rationale: CSM is a great initiative that is having amazing early traction. Increasing from 2 to 3% is an easy and conservative change which is safe. In fact, I agree with @Lanski that this hopefully can be accelerated in the future. ## [Increasing LOL Easy Track Limits to align with Grant Requests](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x3ecd09e4c0f22d25c711ca5777c49c22d144385b85dd7f696ca6cc66cc0ca157) Forum post [here](https://research.lido.fi/t/increasing-lol-et-limits-to-align-with-egg-lido-ecosystem-borg-foundation-grant-funding-request/9881/2) ### Vote: For ### Rationale: At this stage I don’t see why not. I’d recommend being very careful though with this mentality: “provide a comfortable buffer above the anticipated spend to support the committee’s operations over upcoming periods” as there are always costs associated with large buggers. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [May 14, 2025, 9:40am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/13 "2025-05-14T09:40:36Z")
[Vote #186:](https://vote.lido.fi/vote/186) **Emergency rotation of compromised Chorus One oracle.** ### Vote: Yes ### Rationale: Reviewed the payload, looks good. Obvious why this must be changed. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [June 2, 2025, 12:32pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/14 "2025-06-02T12:32:08Z")
# [187/188](https://vote.lido.fi/vote/188) **ONCHAIN VOTE** ### Vote: For ### Rationale: Aligned with Snapshot signal rationale above. I double checked the voting guide and references, had one piece of feedback to the Lido DAO ops team, all looked good. # Community Staking Module v2. Architecture and Fee Structure ### Vote: For ### Rationale: Seems like an intelligent and smart remodel. Modularity is still the smartest architectural design in our industry until it is mature enough. ## Establishment of the Auxiliary Proposer Mechanisms Committee ### Vote: For ### Rationale: Bit worried about the continuous fragmentation of too many committees although it seems to have served Lido DAO very well from an external perspective allowing smaller groups to be more focused with less overhead. ## LIP-28: Dual Governance — Implementation, Parameters, Committees ### Vote: For ### Rationale: I’ve spoken at length about the thoughtful, intelligent, and rigorous design of Dual Governance. I have the utmost confidence that all the research and audits will ensure the deployment is safe both technically and socially, there is a lot at stake (haha)! It’s finally time to execute on this and put some defensive power of stETH into the hands of stETH holders. It will now be as important as ever to move forward in ensuring LDO is not forgotten as it’s only major utility before was the control and governance of Lido DAO and its permissions including stETH. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [June 30, 2025, 8:31am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/15 "2025-06-30T08:31:43Z")
## Aragon Onchain [Vote #189](https://vote.lido.fi/vote/189) ### Vote: Yes ### Rationale: Potentially the most important onchain vote in Ethereum history. Dual governance creates: 1. Extra independent defense layer against the system taking particularly harmful actions 2. Involvement of Ethereum users as stakeholders It’s one of the best use-cases of onchain user protection in the industry. ## [Proposal for Updating Block Proposer Rewards Policy to Lido on Ethereum SNOP on Block Proposals v3](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x8b6addc4be1a9ef4b2a1591be5ac4909aa82c868cd9b7871494b626539a99a8e) Forum post [here](https://research.lido.fi/t/proposal-of-lido-on-ethereum-snop-on-block-proposals-v3/10192) ### Vote: For ### Rationale: Should enhance clarity to Node Operators’ roles and responsibilities. ## [Decision on Kyber Network’s position in the Oracle Set: rotate to Caliber or remove and change the quorum](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xdc208507ca0f659c7f9e38056288aedb7610816ea4020ca751c3422434780de8) Forum post [here](https://research.lido.fi/t/kyber-network-propose-rotation-to-caliber-in-the-oracle-set/10089) ### Vote: Rotate Kyber to Caliber ### Rationale: Seems like a requirement to continue continuity. “Caliber has been operating an oracle for Lido on Ethereum over the past 12 days on the Hoodi testnet. During this period, the Oracle has performed consistently and reliably, with all oracle reports being delivered on time. The infrastructure setup appears robust.” - Raman in the forum ## [DVT Integration Guidelines for the Curated Module Node Operators](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x15cdcb4881d85d48e363bcc449cabfc26b627ac395e2515d65d6637453c35ab3) Forum post [here](https://research.lido.fi/t/proposal-curated-module-intra-operator-dvt-guidelines/10197) ### Vote: Approve ### Rationale: This change should reduce some risks and adds diversity to setups. i.e. using the existing-key-sharding approach. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [July 23, 2025, 9:00am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/16 "2025-07-23T09:00:29Z")
# [# CSM v2 Final Rollout](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xc3f92bcdf8926cfa7528ca6a979c0fdce1e4d0cfaaa72dd6410a76a2e1e55766) Forum post [here](https://research.lido.fi/t/community-staking-module/5917/139) ### Vote: For ### Rationale: CSM is an important direction to decentralize staking on Ethereum and led by the most competent group of contributors. CSM has proven to be valuable and successful so far. The framework makes sense and this seems like an intelligent V2 rollout plan. # [# Triggerable Withdrawals Framework in the Lido Protocol](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x7d7f0e1a6d181310f8752af37e20515a9be258f30b211872f9acca99bc478851) Forum post [here](https://research.lido.fi/t/triggerable-withdrawals-framework-in-the-lido-protocol/10299) ### Rationale: Incredibly important framework that improves some issues with delegated staking. I’m very pro permissionless execution, entry, etc. for defi protocols. Although there are some risks here, they can be mitigated with sensible governance and eventually immuteable or automated rules. The analysis was very helpful, thank you. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [July 24, 2025, 6:44am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/17 "2025-07-24T06:44:41Z")
# [Aragon onchain Vote 190](https://vote.lido.fi/vote/190) ![Screenshot 2025-07-24 at 08.40.15](https://europe1.discourse-cdn.com/flex013/uploads/lido/original/2X/b/b1ac88c9da2786a9a6cd70f2f35430b0c4f82cae.png) ### Vote: For ### Rationale: These are all executions of signals confirming yes. Everything looks fine in the payload from my point of view. **Rotate Lido on Ethereum Oracle Set member Kyber Network for Caliber** **Increase CSM stake share limit from 2% to 3%**. Snapshot. Item 1.7. **Enable a grace period for CSM Node Operators** by setting `keyRemovalCharge = 0`. Proposed on the Forum. Items 1.8-1.10. **Introduce a simplified CSVerifier for CSM**. Proposed on the forum. Items 1.11, 1.12. **Update the reward address and name for Node Operator ID 2 `P2P.ORG - P2P Validator`**. Requested on the forum. Items 1.13, 1.14. **Switch off Easy Track environment for PML, ATC, RCC entities** Easy admin/operational changes. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [September 8, 2025, 4:11pm UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/18 "2025-09-08T16:11:56Z")
## [Nethermind NO Curated Validator set transfer to Twinstake](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x3f68e9bc69850da419211c3d9f0a76d006ed044abc0f8bc845bc1d1cf3db0a8d/discussion) Forum post [here](https://research.lido.fi/t/nethermind-no-curated-validator-set-transfer-to-twinstake/10288) ### Vote: Yes ### Rationale: There are no security problems related to this change and clearly Lido DAO contributors have verified that the transition will be smooth. ## Aragon [Vote #191](https://vote.lido.fi/vote/191) Forum post [here](https://research.lido.fi/t/dual-governance-security-upgrade-plan-ragequit-eth-withdrawal-delay-fix/10543) ### Vote: Yes ### Rationale: Yes to fixing vulnerability discovered by a white hat hacker in the Dual Governance upgrade. The griefing attack could, although unlikely, to block the normal governance flow by overwhelming the system. I’m glad nothing more serious was found and it’s also great this white hate discovered it and reported it for a fix. Yes to the fix. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [September 27, 2025, 8:39am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/19 "2025-09-27T08:39:39Z")
## [Establish the stVaults Committee](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x0e8b53944051321d2cedf8881b546427bc6a22c9fe16f7d150af62fd837ff7da) Forum post [here](https://research.lido.fi/t/stvaults-committee-proposal/10608) ### Vote: Yes ### Rationale: Committees allow smaller factions to work with more autonomy and more quickly. The committee is high-context, professional, and the best individuals to cohesively work together to ensure stVaults is successful. I vote yes to empower them to do this. ## [NEST](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x4267fe277e52a3550e82286af96948a258392ddd303df6b479c4d8f4664acdd0) Forum post [here](https://research.lido.fi/t/nest-network-economic-support-tokenomics/10648) ### Vote: Yes ### Rationale: Although Lido should continue to focus on growth it’s evident that LDO holders are expecting Lido DAO to follow the general route the industry is following and accruing value to the token. A first and easy step to do this while following general compliance is through buy-backs. The more automated and governance minimized the better. My hope is that this mechanism is only a start and that value can accrue using more sophisticated tokenomic mechanisms later such as a ve/guage model. This would ensure long-term alignment, increase token holder paticipation, decrease governance overhead, and decentralized token value accrual to the right actors. Aragon has offered its support in both the design and shipping of the auto-buyback mechanism and beyond. ## [Lido V3 — Design & Implementation Proposal](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x01cd474645cc7c3ddf68314d475d421ef833499297f508fee5f7411fafff3954) Forum post [here](https://research.lido.fi/t/lido-v3-design-implementation-proposal/10665) ### Vote: Yes ### Rationale: Lido V3 is the next stage in Lido’s strategy creating more flexibility and a better impactful user experience for nearly all stakeholders and users of Lido. The key will be ensuring we don’t get lost in the complexity. Aragon [Vote 192](https://vote.lido.fi/vote/192) ### Vote: Yes ### Rationale: 1. **Upgrade to CSM v2 and increase CSM stake share limit from 3% to 5%** , as per Snapshot decision. Items 1.34-1.59. Audit & deployment verification by: Statemind | Ackee. 2. **Activate Triggerable Withdrawals** , as per Snapshot decision. Items 1.1-1.33, 1.60-1.66, 2-4. Audit & deployment verification by Statemind | Audit by Ackee. 3. **Update the reward address and name for Node Operator ID 25 `Nethermind`** , as per Snapshot decision. Items 1.67, 1.68. 4. **Rotate Deposit Security Committee address for `Kiln`**. Requested on the forum. Items 1.69, 1.70. All these issues have been approved by a Snapshot signal as before and we now ratify onchain. The onchain transaction looks good. ---
**Author:** ![Leuts](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/leuts/32/4427_2.png) [@Leuts](https://research.lido.fi/u/Leuts)\ **Post date:** [October 16, 2025, 6:52am UTC](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019/20 "2025-10-16T06:52:37Z")
## [Update the Lido on Ethereum Validator Exits SNOP to v3](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0x62eb338c6d256d43ee54e2b79e9442b58fcfda4ecdcd817ff6422d564d153e9a) ### Vote: Yes ### Rationale: With staking router architecture evolving and the Pectra upgrade the Lido DAO must ensure that the SNOP on Validator Exits remains up to date and provides NOs with consistent operational expectations aligned with the future of Ethereum and the Lido protocol. ## [Empower Lido Ecosystem Foundation to Lead Bridge-Related Partnerships](https://snapshot.box/#/s:lido-snapshot.eth/proposal/0xf842517c2ffba082efac87ec43365e86548adb38e24d1446d850c7d7b979c423) ### Vote: Yes ### Rationale: Growth, partnership, and BD related initiatives often need to move quickly and not fully in the public eye. The optimal individuals to enact these initiatives are high-context Lido DAO contributors. Therefore, giving optimistic power to a committee to optimistically engage and enforce these bridge related partnerships makes sense. Allowing the DAO to veto certain decisions still creates safety an decentralization. [Next page](https://research.lido.fi/t/anthony-leuts-delegate-thread/8019.md?page=2)