Lido DAO

Lido began on Ethereum in December 2020 as a pooled route into Beacon Chain validation. A depositor received stETH instead of operating a 32 ETH validator. stETH represented a share of pooled ether and changed balance as oracle reports brought rewards, penalties and fees into the accounting.

wstETH later packaged that same economics for systems that cannot handle rebases. Its wallet amount stays still while each unit converts into more or less stETH. It is a wrapper, not a second validator balance or a second claim on the pool.

LDO sits outside both receipt forms. One billion LDO was minted at DAO launch and the current explorer state still reports that total. Voting uses committed LDO, but the verified MiniMe token remains controlled by an Aragon TokenManager with permissioned mint and issue functions. One billion describes launch and current supply, not an immutable cap. LDO neither enters the ETH withdrawal queue nor accrues validator rewards merely because the protocol earns them.

The 2021 allocation put 36.32% in the DAO treasury, 22.18% with investors, 6.5% with validators and signature holders, 20% with initial developers, and 15% with founders and future employees. Those figures describe origin and vesting, not current addresses; transfers and treasury programs mean present concentration must be measured on-chain.

In August 2026, NEST added a new treasury route. Under DAO-set conditions, surplus protocol revenue buys LDO; launch mode sends the acquired tokens to the DAO treasury. That can affect treasury inventory and market demand, but it does not distribute revenue to wallets, burn every purchased token, or guarantee a market floor.

Lido V2 went live on 2023-05-15 with the Staking Router and protocol withdrawals. A holder locks stETH or wstETH in the FIFO WithdrawalQueue and receives a transferable unstETH NFT. The request cannot be canceled; once sufficient ETH is reserved and an oracle report finalizes it, the NFT holder claims ETH and the position is burned.

Finalization depends on buffer liquidity, validator exits and Ethereum queues. A penalty or slashing event can produce a final rate below the request-time expectation, and a queued position stops receiving positive staking rewards. A secondary-market swap is faster only because another buyer accepts the token and price risk.

Core routing and V3 vaults now coexist. Staking Router allocates pooled deposits among registered modules, while each stVault owner selects its own operator and settings. Hash Consensus gathers committee reports, AccountingOracle applies accounting and withdrawal finalization, and ValidatorsExitBusOracle reports requested validator exits. VaultHub and DAO-set caps connect external shares to the same stETH supply.

Lido V3 added a second route on 2026-01-30. stVaults hold segregated, overcollateralized ETH and can mint external stETH shares through VaultHub. A vault owner chooses the operator, fees and risk settings and can manage minting, repayment, deposits and exits for that vault. Those choices do not grant custody of Core deposits or a general LDO vote.

LDO votes set fees, install modules, approve upgrades and direct treasury policy. Easy Track handles pre-authorized routine actions through narrow factories. An eligible actor starts a motion, which becomes executable after 72 hours unless objections reach 0.5% of the entire LDO supply. Holders may still object after that wait until execution. Reducing the voting burden therefore makes continued attention part of the safety model.

Dual Governance, activated in July 2025, inserts staker opposition into the execution path. stETH, wstETH and unstETH holders can escrow positions; enough support extends the timelock, and the higher seal leads toward rage quit before the disputed motion can execute. This is a delay-and-exit right. It does not let stETH cast an LDO parameter vote.

Lido’s core system uses upgradeable proxies whose admins are assigned to the DAO Agent. The DAO can change implementations and privileged roles through governance. V3 adds VaultHub and an external-share cap: vault owners manage their own vault paths, while DAO administration controls shared protocol limits and can govern disconnection or upgrades.

Emergency roles are narrower. CircuitBreaker committees can pause designated contracts once for a bounded duration and cannot resume them or manage funds through that role. Deposit Security participants can halt deposits when malicious deposit data appears. Dual Governance emergency multisigs handle specified failure paths. Calling all of them a single security administrator would hide their different quorums, limits and escalation routes.