Hi everyone! TL;DR As part of the Triggerable Withdrawals upgrade on mainnet, we’ve reworked the “stuck” functionality. Previously, Oracles were responsible for reporting stuck keys, which were then used to penalize node operators. We’ve now made this functionality permissionless and developed a bot that will automatically report such delays. I propose that the Gas Supply Committee compensate gas fees for proving validator late actions. Tech details As described in LIP-30, staking mod...| Lido Governance - Latest posts
As part of the GOOSE 2025 retrospective, the progress report is now published. It covers outcomes against the goals set for the period from January 1 to September 16 2025. The report is meant to give the community clear context on what’s been achieved, where challenges remain, and how this informs the next cycle. Transparency and accountability are central to the GOOSE framework, and this publication is part of keeping that record open. Read the full report here| Lido Governance - Latest posts
As part of the GOOSE 2025 retrospective, we’re publishing this detailed progress report that covers the period from January 1 to September 16 2025. It provides a look at outcomes against the goals set in last year’s cycle. The report is intended to serve as context for the community as we enter the new GOOSE cycle. Full report here What is GOOSE The Guided Open Objective Setting Exercise (GOOSE) framework was adopted by the Lido DAO in September 2023. Each GOOSE sets one-year and three-ye...| Lido Governance - Latest posts
Next GOOSE cycle notice This is a notification regarding the beginning of the new GOOSE cycle. What is GOOSE The Guided Open Objective Setting Exercise (GOOSE) framework was adopted by the Lido DAO in September 2023. Each GOOSE sets one-year and three-year goals aligned with the DAO’s mission and vision, making them public for anyone to work towards. Goals serve as reference points for contributors and guide funding decisions from the DAO’s treasury. Following the adoption of the framewor...| Lido Governance - Latest posts
Read about Blockdaemon’s support for Distributed Validators through Lido’s Curated Module in our latest blog, where we outline the role of Obol DVs in enhancing resilience and security for Ethereum staking. https://www.blockdaemon.com/blog/support-for-obols-dv-integration| Lido Governance - Latest posts
Dear All, A small update to our post Innovation grant request : NGO Doctors Without Borders / Medecins Sans Frontieres (MSF) to let you know that access to our Multisig is done through our public wallet address 0x462F351EE8b10Cc21B161ad698eF3CEba957FE65 and not through stake2care.eth As we did not need the ens in the end, we did not renew the domain registration. Thanks to @gdr1123 for spotting it, and our apologies for not clarifying earlier!| Lido Governance - Latest posts
Voting Actions - September 22nd - 26th Proposal: Establish the stVaults Committee Vote: For Reasoning: As Lido moves towards V3 and the launch of stVaults, a dedicated committee provides the necessary structure to balance protocol safety with operational flexibility. The design, which combines consensus-based committee actions, DAO oversight through Easy Track, and conflict-of-interest safeguards, creates a robust governance layer. This setup will help manage risk parameters effectively while...| Lido Governance - Latest posts
Curia Lab Delegate ENS: curia-delegates.eth Delegate Address: 0x17296956b4E07Ff8931E4ff4eA06709FaB70b879 Twitter: https://twitter.com/curia_gov Website: https://www.curialab.xyz/ About Us Curia Lab is a team of seasoned DAO governance researchers, data analysts, blockchain engineers, and developers. We are committed to strengthening the DAO ecosystem through specialized tools, insights, and delegate services. Our mission extends beyond tool creation; we actively engage in DAO governance as a ...| Lido Governance - Latest posts
Name: Anthony L Address: leuts.eth (0x42E6DD8D517abB3E4f6611Ca53a8D1243C183fB0) Forum: @leuts Twitter: Leuts 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 forwa...| Lido Governance
Snapshot: Nethermind → Twinstake Validator Operations Migration Vote: Approve the migration Summary: We voted in favor of the approval, as we think that the outlined motivation for the migration is reasonable and sound, such as delegation of operations to purpose-built staking providing and alignment with long term decentralization strategy. We also think that the migration plan is reasonable and happy with the conclusion of LNOSG. Establish the stVaults Committee Vote: Support Summary: We ...| Lido Governance - Latest posts
Establish the stVaults Committee Vote: For Rationale: We voted for this proposal as it proposes a governance mechanism that’s a must for Lido V3. The stVaults Committee seems well-balanced, with expertise from contributors from different areas of the protocol. Their responsibilities are well-defined, and relying on Easy Track makes sense. Lastly, the Committee members seem to be qualified for their role. NEST - Network Economic Support Tokenomics Vote: For Rationale: We voted for this propo...| Lido Governance - Latest posts
Establish the stVaults Committee Forum post here Vote: Support Rationale: Excited about moving the stVaults forward. The committee is a great bootstrapping mechanism for a new part of the protocol that might need adjusting and overseeing. I also trust the members of the committee, but if they took decisions that me or other governance participants disagreed on, a new vote can be put forth to change the committee’s role, its configuration or dissolve it entirely. NEST - Network Economic Supp...| Lido Governance - Latest posts
Establish the stVaults Committee --- A temporary committee is being proposed that will adjust the parameters of new stVaults within Lido v3. This seems like a good solution for setting up the new system, but there are no clear deadlines for this “temporary” committee, and therefore no elections for its members. It seems like a useful feature, but it lacks decentralization and governance from the DAO. So, I expect a clearer timeline for the on-chain phase. --- Vote: FOR Platform: Snapshot| Lido Governance - Latest posts
This post is proof to High Signal that I am the owner of this Lido forum account. My authentication code is: HCW-VHN-ZHP| Lido Governance - Latest posts
Date Voted: September 23, 2025 56. Proposal:Establish the stVaults Committee (Snapshot) Vote: Support Rationale: I voted Yes on establishing the stVaults Committee. This structure is needed to launch stVaults in V3 safely and efficiently. A dedicated group can move faster on non standard requests while still prioritizing protocol security and DAO revenue. I see the risks of concentrated decisions but as long as the committee disclose any conflicts of interest, and set a review timeline so the...| Lido Governance - Latest posts
Looking to join the Lido Alliance BORG partners multisig on Neutron with address: neutron13twhd5wxtg40zq48ym984hmrn2qzvaqpdr9z4n Verification: Mintscan| Lido Governance - Latest posts
Proposals Lido V3 — Design & Implementation Proposal (Snapshot) voted:Yes Reasoning: Me vote YES pon Lido V3 cause it turn dee protocol from one little lane into a whole super highway, sin? More choice, more resilience, more strategies, more DVT clusters, and more operators with stVaults. V3 mek Lido a true staking infrastructure! Respekt. NEST - Network Economic Support Tokenomics (Snapshot) voted:Approve Reasoning: Me vote to approve because surplus stETH route to LDO repurchase via STONK...| Lido Governance - Latest posts
TL;DR This proposal outlines implementing the Triggerable Withdrawal framework within the Lido protocol to enable permissionless, secure, and verifiable validator exits via the Execution Layer - enhancing the protocol’s fault tolerance, reducing trust assumptions, and paving the way for truly permissionless staking in Lido. Abstract The Triggerable Withdrawals (TW) mechanism is a critical extension of Lido’s architecture, enabling the initiation of validator exits without requiring the in...| Lido Governance
Preface This is a follow-up thread for the already published rewards distribution architecture decision record. Today we present an on-chain design implementing the chosen options. Simple summary The Lido protocol upgrade that re-stakes newly appeared rewards after the Ethereum Merge will happen to achieve rewards compounding. Abstract We introduce the rewards distribution mechanism which consists of a dedicated vault contract acting as a coinbase (i.e. fee recipient) for the newly appeared...| Lido Governance
The purpose of this thread is to collect discussion and community alignment with regards to min-bid usage by Node Operators participating in in the Lido Protocol. As a start, I propose we begin the discussion based on Irina’s post from the relay voting proposal thread. In general I think that ~28-40% of blocks produced locally sounds about high but isn’t a prohibitive starting point, although a maximum APR decrease of 15% sounds high, given that it’s currently not easily discernable wha...| Lido Governance
Snapshot vote started The Establish the stVaults Committee Snapshot has started! Please cast your votes before Mon, 29 Sep 2025 16:00:00 GMT| Lido Governance - Latest posts
Hi, I submitted a transaction to withdraw my stETH to ETH 8 days ago. The waiting period was 7 days when I did this and gradually dropped down to 2 days. Then it jumped back up to 9 days and is now going down slowly again. So what is the expected withdrawal time right now? Since I’ve already committed to the withdrawal, it would be nice to know.| Lido Governance
Summary NEST is a modular extension of STONKS that, when filled with stETH, incentivizes a keeper to fire a STONKS Cowswap order of stETH for LDO and routes it back to the Lido DAO treasury, effectively taking it out of circulation. The net effect it has is essentially to change the respective share over governance rights that holders enjoy, including over future ‘value distribution’ proposals. Introducing NEST NEST proposes a modular and future-proof system that can automatically trigger...| Lido Governance
Yielding Yellowthroat Incident Report - 24/08/25 On August 24th, it came to the attention of SDVT coordinators that narko2t1 from the SDVT Yielding Yellowthroat Obol cluster had their node operator address compromised (the Individual Manager address, which is the same as their Rewards Address). This is an address related to cluster participation and receipt of rewards, and is not attached to any kinds of validator operations. While the scope of the hack is still under investigation, as the cl...| Lido Governance
Summary With the increasing adoption of Distributed Validator Technology (DVT) on Ethereum, discussion has increased within the Lido Node Operator set regarding how Curated Node Operators might start to utilize the technology. In light of the adoption of DVT across Ethereum, its strong performance both in SDVT and CSM, as well as in other staking protocols, NOM workstream contributors would like to propose that: Node Operators in the Curated Set may opt-in to intra-operator DVT setups (utiliz...| Lido Governance
Hi CSM committee, For proof of engagement, I spoke at ETHBelgrade 2025 on the topic “Stablecoins are eating finance: A frontline report” (you can search it on yt, otherwise I would have linked it here) - could someone please check if this would be considered sufficient?| Lido Governance - Latest posts
Answering the CSM and SDVTM integration RFP, here is Dappnode’s proposal: Dappnode Overview Dappnode is Free Open Source software with the purpose of making deploying, operating and maintaining web3 infrastructure accessible to anyone, regardless of their technical level. Its design principles uphold self-sovereignty, privacy and ease of use. In the spirit of highly enhancing the ease of use, the Free Open Source Software Dappnode also comes preinstalled in plug-and-play hardware under the ...| Lido Governance
TLDR The Ethereum staking industry has become increasingly competitive in the 4.5 years since the launch of Lido. Especially for large amounts of stake over long time periods, Node Operators are now able to offer staking, including (partial) insurance, with take rates as low as 1-3% in some cases. Given the increasingly competitive nature of the market, generally favorable market tailwinds for ETH, and the need for the Lido protocol to become both more robust and adaptive to market conditions...| Lido Governance
TL;DR V3 is near-ready. Following the whitepaper vision, the first production-ready Lido V3 build has run through two public testnets and is in late audits. Final testnet and follow-up changes from the audits are still to come. stVaults introduce a non-custodial, over-collateralized way to choose how and with whom to stake while still minting stETH. The existing 1:1 staking path continues as the Core Pool. Why it matters. V3 turns the Lido protocol from a single pool into Ethereum staking inf...| Lido Governance
Hi, Nethermind would like to change the Node Operator name and the Reward Address: operator id: #25 new Name: Twinstake (from Nethermind) new Reward Address: 0x36201ed66DbC284132046ee8d99272F8eEeb24c8 (from 0x237DeE529A47750bEcdFa8A59a1D766e3e7B5F91) Link to operator: https://operators.lido.fi/module/1/25 Published signed messages: The Ethereum Verified Signed Message from old wallet The Ethereum Verified Signed Message from new wallet| Lido Governance - Latest posts
Following an investigation yesterday regarding a Solana incident involving SwissBorg, Kiln has decided to take precautionary measures to safeguard client assets across all networks it runs validators in. As part of this response, Kiln today began the orderly exit of all of its Ethereum (ETH) validators, including validators run using the Lido protocol. The exit process is a precautionary measure designed to ensure the integrity of the staked assets.stETH holders do not need to perform any act...| Lido Governance - Latest posts
Hey! We at P2P.org are interested in test participation here! I will try to apply the change in out infrastructure in Hoodi| Lido Governance - Latest posts
This post is proof to High Signal that I am the owner of this Lido forum account. My authentication code is: LHV-RYP-MTL| Lido Governance
The governance platform for the Lido DAO.| Lido Governance
As per the post in the call for relays thread and communications between bloXroute and various Node Operators who utilize the Lido protocol, there has been an interested expressed by some NOs to try out using the bloXroute validator gateway (blog post) [docs] products. Due to this interest, I’ve created this post so that NOs who are keen to test these services can post below in order to inform the community of the possible usage of these services and results from the testing. There are esse...| Lido Governance
Ensuring Compatibility with Ethereum’s Pectra Upgrade This post outlines the technical details of the proposed upgrade to the Lido protocol to ensure continuous operation with Ethereum’s upcoming Pectra hardfork. The focus is exclusively on compatibility, rather than integrating any new features introduced by Pectra. Pectra-related new functionalities, such as Triggerable Withdrawals via EIP-7002 and increasing the MAX_EFFECTIVE_BALANCE & validator consolidations via EIP-7251, will be add...| Lido Governance
TL;DR A Dual Governance weakness was reported through Immunefi. The issue was not exploited; existing “training-wheels” safeguards and the DG Emergency Committee allow for effective mitigation, and user funds remain safe. Users do not need to do anything, and the vulnerability is expected to be fixed in the scheduled onchain voting slot for August. Introduction A potential griefing vulnerability was reported on July 13th affecting the current implementation of the Dual Governance RageQuit...| Lido Governance
In an effort to further facilitate the alignment of Lido contributors, stakers, node operators, and LDO token holders, a set of Lido DAO contributors created this Manifesto to serve as a reference point for past, present, and future decision-making regarding Lido’s evolving operator and validator set. Lido DAO is always aligned with the Ethereum values and puts a lot of effort into bringing Ethereum closer to these values. A list of current and completed activities is presented at the end o...| Lido Governance
🚀 Vote #188 has just started! This is a rerun of Vote #187, featuring the same set of proposals. 🗓 Voting is open until the end of the main phase: May 30, 09:00 UTC. Follow this guide for instructions on reviewing and verifying vote items. Your voice matters! 💕| Lido Governance
Community Stakers Identification Framework The Community Staking Module (CSM) Early Adoption mechanics have proven immensely effective by ushering in the onboarding of 340 Node Operators to the Lido NO Set while preventing major sybil-related incidents. Since becoming fully permissionless, CSM has seen high demand from large players, leaving less room for independent stakers to join CSM and get their validators deposited to. In CSM v2, this is meant to be addressed through the implementation ...| Lido Governance
Summary With the increasing adoption of Distributed Validator Technology (DVT) on Ethereum, discussion has increased within the Lido Node Operator set regarding how Curated Node Operators might start to utilize the technology. In light of the adoption of DVT across Ethereum, its strong performance both in SDVT and CSM, as well as in other staking protocols, NOM workstream contributors would like to propose that: Node Operators in the Curated Set may opt-in to intra-operator DVT setups (utiliz...| Lido Governance
Hi everyone. Below is an updated version of the full text of the proposal, following some suggestions from team members at Obol and SSV, as well as community members. The new full text has been made available here (below), on hackmd, github, and IPFS. The snapshot proposal will go live with the Summary from the text below and key excerpts, but please refer to the full text for all the details. The following proposal is the final draft that will be put forth for Snapshot vote to the Lido DAO o...| Lido Governance
Hi there! As a contributor to the analytical workstream, I’d like to share my vision of the framework that could be used to evaluate the risks involved with validation. The purpose of this valuation is to provide a quantitative approach to determining risk mitigation strategies for future staking module development, considering all actors involved. I view this framework vision as a necessary tool for making informed decisions on managing risks and implementing mechanics for mitigation. In p...| Lido Governance
In this communication, Lido DAO Community Staking team contributors are inviting proposals from software providers specializing in node/validator setup to enhance their existing tools by incorporating a user-friendly pathway for community stakers to engage with the Lido Community Staking Module (CSM) and Lido Simple DVT Module (SDVTM) as Node Operators (NO). Parties interested in developing an integration with CSM and/or SDVTM should share a proposal with an overview of a potential integratio...| Lido Governance
Lido DAO’s mission is to make Ethereum staking simple, secure, and decentralized. Lido on Ethereum launched with a curated validator set, which has enabled the protocol to grow to its current size robustly but leaves some room for improvement from the perspective of allowing a bigger range of independent node operators to more easily interact with the protocol. Recent long-range goals approved by the Lido DAO (proposed by @Hasu) suggest the introduction of a permissionless staking module. G...| Lido Governance
Staking Router Module Proposal: Simple DVT EDIT Feb 12, 2024 The Simple DVT Module Committee multisig has been created and all members of the committee have verified their signing addresses. The Safe’s address is 0x08637515E85A4633E23dfc7861e2A9f53af640f7 and visible at this link. EDIT Oct 26, 2023 A revised version of this proposal has been put together below based on feedback and is proposed to go to Snapshot on Thu Oct 26th. It is suggested that the snapshot proposal go live with the Sum...| Lido Governance
Lido DAO currently has governance power over most of the protocol code and parameters. In this post, we discuss the current scope of governance, the associated risks, and how these risks can be minimized by reducing the governance scope (via ossification) and by aligning incentives between the DAO and stakers (via dual governance structure). Table of contents Current governance mechanics Scope of governance Worst-case scenarios stETH holders Ethereum network The problem Reducing th...| Lido Governance