The Lido DAO governs Lido, the largest liquid-staking protocol on Ethereum. Users deposit ETH and receive stETH, a transferable token that accrues staking rewards while remaining usable across DeFi — so a staker keeps liquidity instead of locking ETH in a validator. The protocol is run by holders of the LDO governance token, who set the node-operator set, protocol parameters, and the fee — currently 10% of staking rewards, split between node operators and the DAO treasury. Because Lido stakes a very large share of all ETH, its governance is not just a protocol matter but a live question about the decentralization of Ethereum itself. (Lido docs)

stETH and the liquid-staking model

Solo staking on Ethereum requires 32 ETH, dedicated hardware, and a locked position. Lido removes all three constraints: any amount of ETH can be deposited, the protocol routes it to a curated set of professional node operators, and the depositor receives stETH that rebases daily with rewards and can be traded, lent, or used as collateral. That composability is why stETH became one of the most widely integrated assets in DeFi — and why it anchors the collateral base of protocols like Aave.

The trade-off is trust in Lido's operator set and smart contracts. Historically the operators were a DAO-curated whitelist; to widen participation Lido added the permissionless Community Staking Module (CSM), letting independent operators join with a bond rather than a governance vote. Node-operator selection, module parameters, and withdrawal mechanics are all controlled by LDO governance. (docs.lido.fi)

The centralization debate

Lido's success created the problem it is best known for. Because it pools stake from many users behind one protocol, Lido at times controlled roughly a third of all staked ETH — close to the one-third threshold at which a single actor can affect Ethereum's finality, and well within sight of the two-thirds level that matters for consensus safety. Critics argued that a single liquid-staking protocol approaching these thresholds undermines the very decentralization staking is meant to secure; a widely debated 2021 research-forum proposal even asked whether Lido should self-limit its share of the network. Lido's answer has been to decentralize within the protocol — more independent operators, the CSM, distributed-validator technology — rather than cap deposits. The debate remains one of the sharpest governance questions in Ethereum. (Lido research forum; Lido blog)

Dual Governance — giving stakers a veto

LDO holders decide, but the people most exposed to a bad decision are stETH holders, who may hold no LDO at all. Dual Governance, approved by an LDO vote in mid-2025 (about 53.6M LDO in favour against a 50M-LDO quorum, with a single dissenting vote) and rolled out to Ethereum thereafter, closes that gap by inserting a dynamic timelock that stETH holders can extend. It is one of the most closely watched governance mechanisms in DeFi because it grafts an exit-based safeguard onto a token-weighted DAO. (The Block; Dual Governance 101)

Mechanically, every governance action affecting Lido on Ethereum now faces a minimum delay, and stETH holders register dissent by depositing stETH into an escrow contract:

• Veto Signalling — once escrowed stETH exceeds ~1% of the stETH supply, execution is delayed on a sliding scale, from about five days up to a maximum of roughly 45 days as more stETH piles in, buying time to scrutinise the proposal.
• Rage Quit — if escrowed stETH crosses ~10% of supply, governance is frozen: no queued proposal can execute until the dissenting stakers have fully withdrawn their ETH from the protocol. Stakers who disagree can leave before the change binds them.

The design was audited by multiple firms (Certora, OpenZeppelin, Statemind, Runtime Verification) and lives in the lidofinance/dual-governance contracts. It borrows the name and spirit of Moloch's rage quit, applied to a two-token structure: LDO proposes, stETH can veto or exit. (Dual Governance overview)

How Caper approaches this

Dual Governance is a retrofit: Lido started as a token-weighted DAO and later bolted on a second constituency (stETH) with a veto and an exit, because the holders bearing the risk had no direct say. A caper reaches the same destination from the opposite direction — it is built so voice and exit are the same right from day one. There is no separate escrow, no 1%/10% thresholds to organise, and no second token class: every member's voting weight and their pro-rata claim on the treasury at exit are one and the same number, combining the stake they hold with the participation they have shown. A member who dislikes where a caper is heading does not need to accumulate a veto quorum; they can always exit for their share, immediately. Lido's mechanism is the more general fix for the enormous installed base of one-token DAOs; a caper is what that safeguard looks like when it is native rather than grafted on. The exact exit math is on the linked governance pages, verified against the contract — no additional guarantees are implied here.

References

• Lido documentation — protocol, staking modules, and governance reference.
• Lido research forum — proposals and the decentralization debate (primary source).
• Dual Governance 101: Explainer and Dual Governance: An Overview — the veto/rage-quit mechanism and thresholds.
• lidofinance/dual-governance — the audited contracts.
• The Block, Lido DAO votes to enable dual governance (2025) — the approving vote.