Lido DAO (LDO)

Lido DAO: How LDO Governs Ethereum’s Liquid-Staking Infrastructure

Lido combines pooled Ethereum staking, transferable stETH, validator operators, oracle reporting and token-based governance. LDO controls the DAO, but withdrawals, upgrades and stETH-holder protections depend on a wider system of contracts, committees and exit processes.

What Lido does

Lido is a liquid-staking protocol for Ethereum. Users deposit ETH into Lido contracts and receive stETH, a transferable token representing a claim on pooled staked ETH and its variable staking rewards or penalties. The protocol coordinates deposits, validator operations, accounting and withdrawals, while users can continue using stETH in wallets and decentralized applications instead of holding an otherwise illiquid validator position. Lido describes this arrangement as non-custodial because node operators do not receive direct access to users’ deposited assets; however, users remain exposed to the protocol’s contracts, operators, accounting process and governance decisions.

The system’s main components

The core system has three principal participants: staking users, node operators and the Lido DAO. Users supply ETH; node operators run validators using pooled capital; and the DAO sets important parameters, selects or manages operator modules, oversees oracle arrangements and approves protocol changes. Lido’s open-source core repository describes the Ethereum contracts as handling deposits, reward distribution and withdrawals. The wider architecture also includes the Staking Router, Accounting Oracle, withdrawal contracts and modular staking components. This means Lido is not simply an ERC-20 token or a single staking contract, but a collection of contracts and off-chain operational services that must work together.

stETH, rewards and withdrawals

stETH is a rebasing liquid-staking token: its balance is designed to reflect the holder’s share of pooled ETH and accumulated staking performance. Ethereum’s staking documentation identifies stETH as an example of a rebasing liquid-staking token, in contrast with exchange-rate tokens whose balances remain constant while their redemption value changes. Lido also supports wrapped stETH for applications that prefer a non-rebasing balance model. The practical benefit is composability, but the token is not identical to immediately available ETH. Its secondary-market price can diverge from the value of underlying assets, particularly during stress.

Protocol redemption is asynchronous. A user sends stETH or wstETH to the WithdrawalQueueERC721 contract, receives an unstETH NFT representing the queue position, waits for the request to be finalized through the accounting process, and then claims reserved ETH. Requests are processed on a first-in, first-out basis, subject to available ETH, timing requirements and the protocol’s reported share rate. The withdrawal documentation says that rewards do not continue accruing to a request after its tokens enter the queue, and that severe validator losses could result in a finalization rate below one ETH per stETH. Secondary-market sales may provide a faster exit, but introduce market-price and liquidity risk instead of removing risk altogether.

What LDO actually does

LDO is an ERC-20 governance token for the Lido DAO. Its primary documented function is voting power rather than a claim on stETH, staking rewards or protocol revenue. LDO holders participate in decisions covering fees, node-operator arrangements, oracle sets, treasury spending, protocol parameters and upgrades. The official DAO documentation states that voting weight is proportional to the LDO balance used for the vote, while the Lido website says the token uses balance snapshotting to reduce the effect of last-minute transfers before voting begins. Holding LDO therefore gives governance influence, but does not by itself provide the economic exposure of holding stETH.

Governance, safeguards and upgrade control

Lido’s governance process separates discussion, off-chain signaling, on-chain voting and execution. Proposals generally begin in the Research Forum, may proceed to Snapshot, and then move to Aragon-based on-chain voting when contract actions or treasury execution are required. Easy Track provides an optimistic process for defined routine operations, normally allowing a motion to pass after a waiting period unless enough LDO holders object. The protocol-levers documentation identifies the Aragon voting contract as the LDO governance mechanism and the Lido DAO Agent as the administrator for upgradeable core proxies. It also states that upgrades require a successful DAO vote, making governance participation and contract administration material parts of the security model.

Dual Governance adds a separate protection for stETH holders. After certain LDO-approved actions pass, stETH holders can signal opposition through an escrow mechanism that delays execution, with stronger opposition able to pause governance and create a path for affected stakers to exit. This does not give stETH holders ordinary voting power over every DAO decision, and the governance page distinguishes Dual Governance from routine LDO voting and Easy Track operations. The arrangement is therefore best understood as a veto or delay layer for eligible actions, not as a replacement for token governance.

Users, dependencies and practical limits

Lido is intended for ETH holders who want exposure to Ethereum staking without operating validators themselves, as well as applications that use a liquid-staking token as collateral, liquidity or a settlement asset. Its operation depends on Ethereum’s consensus-layer validator exits, Lido’s node-operator modules, oracle reports, withdrawal liquidity, upgradeable contracts and the DAO’s ability to coordinate emergency or routine actions. The architecture can broaden through modular components such as stVaults, but additional modules also create more configuration, role-management and integration surfaces to evaluate. LDO holders govern the system, yet the protocol’s practical operation still relies on specialized committees, operators and permissioned roles documented by the project.

Key takeaways

• Lido turns pooled Ethereum staking into transferable stETH rather than issuing LDO as the staking receipt.
• LDO is primarily a governance asset; it does not represent a direct claim on staked ETH or automatically accrue staking rewards.
• Withdrawals use a first-in, first-out queue, an unstETH NFT and oracle-driven finalization rather than instant protocol redemption.
• The DAO can change important parameters, manage operators and approve upgrades through Aragon-based governance and related operational processes.
• Dual Governance gives stETH holders a delay and opposition mechanism for eligible decisions, but it does not replace LDO voting.
• Lido’s risk profile depends on smart contracts, validator performance, oracle reporting, liquidity, governance and Ethereum’s withdrawal process.

Risks and open questions

• Smart-contract and upgrade risk remain material because core contracts and related modules are upgradeable and controlled through governance-linked roles.
• Validator downtime, slashing, inaccurate accounting or delayed exits could reduce returns or affect the amount and timing of ETH available for withdrawals.
• stETH can trade below the value of its underlying ETH in secondary markets, especially when protocol withdrawals or market liquidity are stressed.
• Governance concentration is a continuing question because voting power is proportional to LDO holdings and routine operations may use committees or optimistic mechanisms.
• The withdrawal queue can impose a waiting period, and the amount ultimately claimable can be affected by the share rate used at finalization.
• Additional modules, integrations and operational committees expand Lido’s functionality but also increase the number of dependencies users and integrators must assess.