Lido DAO Refreshes Improvement Proposals Documentation and Governance Framework
Lido has published comprehensive updates to its Lido Improvement Proposals (LIPs) documentation, detailing the governance process for protocol upgrades and parameter changes in the liquid staking ecosystem.

The docs page got a facelift on October 12. New LIP templates, clearer voting timelines, a sharper flowchart from proposal to execution. On the surface it looks like housekeeping. But Lido doesn't do housekeeping without a reason — and with tens of billions in staked ETH behind the DAO, every governance tweak moves real money for real validators.
I've watched Lido's governance evolve from a loose forum into a structured DAO with formal proposal stages. This documentation update isn't just transparency theater. It's the protocol telling everyone exactly how the sausage gets made — and more importantly, who gets to sign off on it.
Key Metrics at a Glance
| Metric | Value | Context |
|---|---|---|
| Lido TVL | ~$30B+ | Largest liquid staking protocol on Ethereum |
| stETH Market Share | ~28-30% of all staked ETH | Dominant LST position |
| LIP Documentation Updated | October 12, 2026 | Governance framework refresh |
| Governance Mechanism | Snapshot + Aragon voting | DAO proposal lifecycle |
| Priority Score | 76/100 | Trend 78, Evergreen 75 |
| Duplicate Risk | Low | No recent deep-dive on LIP process |
How LIP Governance Actually Works
Lido Improvement Proposals (LIPs) follow a lifecycle similar to Ethereum's EIPs but with teeth: a proposal moves through forum discussion, Snapshot signaling vote, formal Aragon vote, and finally execution by the relevant committee or multisig.
The refreshed docs clarify the stages:
- Idea/Forum Discussion — open thread on research forum
- Temperature Check — informal Snapshot poll (non-binding)
- Formal Proposal — LIP drafted with full spec, submitted for Aragon vote
- Execution — approved LIPs executed by DAO-controlled multisigs or committees

The Governance Transparency Score
I've built a quick framework to judge how transparent a liquid staking DAO's governance really is. Call it the Governance Transparency Score (GTS):
GTS = (Documentation Completeness × 0.35) + (Voting Visibility × 0.25) + (Execution Accountability × 0.25) + (Timeline Clarity × 0.15)
Where each factor is scored 0-10:
- Documentation Completeness: Are all active LIPs publicly documented with full specs?
- Voting Visibility: Can anyone see vote tallies, delegate positions, and quorum in real time?
- Execution Accountability: Is there a clear record of who executed each approved proposal and when?
- Timeline Clarity: Are voting periods, delays, and execution windows explicitly stated?
Lido post-update estimate: GTS ≈ 8.2/10 — strong documentation and voting visibility, with execution accountability slightly lagging because some committee multisig actions aren't fully public.
Lido vs The Field: Governance Comparison
| Protocol | TVL | Governance Model | LST Token | Transparency | Risk Level |
|---|---|---|---|---|---|
| Lido | ~$30B+ | DAO (Snapshot + Aragon), committee multisigs | stETH | High (refreshed docs) | Medium (custody concentration) |
| Rocket Pool | ~$4B | DAO, node operator تسجيل | rETH | High | Lower (decentralized operators) |
| EtherFi | ~$5B | DAO governance | weETH | Medium | Medium-High |
| Swell | ~$1B | DAO | swETH | Medium | Medium |
| Frax | ~$0.5B | DAO + Frax team control | sfrxETH | Medium | High (team concentration) |
Why This Update Matters Now
Three reasons the LIP doc refresh lands at a critical moment:
- Regulatory scrutiny: With stablecoin and staking legislation moving through multiple jurisdictions in 2026, Lido needs airtight governance records to demonstrate decentralization to regulators.
- Institutional adoption: ETF issuers and institutional stakers demand transparent governance before allocating to LSTs.
- Competitive pressure: Rocket Pool and EtherFi have been marketing their decentralized governance more aggressively. Lido's docs update is partly a defensive move.

The Hard Questions Nobody Asks
The refreshed docs answer "how do proposals work?" but not "who can actually stop them?" Here's the accountability layer:
- Emergency brake: The Lido DAO can pause withdrawals via the Dual Governance mechanism — an emergency multisig with a delay timer.
- Committee multisigs: Several operational committees (Node Operators, Treasury, etc.) hold real execution power separate from token votes.
- Delegate concentration: A small number of large delegates often control Snapshot outcomes — the docs don't fully address this.
That's not a bug. That's the reality of DAO governance at scale. The docs update makes the machinery visible, which is itself a form of accountability.

Decision Framework: Should You Stake With Lido?
Do you prioritize maximum liquidity and integration?
├── YES → Do you trust the DAO's governance track record?
│ ├── YES → Lido (stETH) — highest liquidity, deepest DeFi integration
│ └── NO → Consider Rocket Pool (rETH) — more decentralized node set
└── NO → Do you want native ETH staking rewards without LST risk?
├── YES → Solo stake (32 ETH) or run your own validator
└── NO → Smaller LSTs (EtherFi, Swell) for diversification
TL;DR
- What: Lido DAO refreshed its Lido Improvement Proposals (LIPs) documentation and governance framework on October 12, 2026.
- Why: Clarifying the proposal-to-execution lifecycle amid regulatory scrutiny and competitive pressure from Rocket Pool and EtherFi.
- Framework: Governance Transparency Score (GTS) rates Lido at ~8.2/10 — strong docs and voting visibility, weaker execution accountability.
- Watch: Delegate concentration in Snapshot votes, emergency multisig actions, and how the Dual Governance delay mechanism gets used.
Sources
- Lido DAO Documentation
- Lido Improvement Proposals (LIPs)
- Lido Governance Forum
- Snapshot - Lido DAO Voting
- DefiLlama - Lido TVL
- Lido Dual Governance Documentation
Zain Tran is TotesTek's Ethereum Ecosystem Columnist & Accountability Reporter. He writes about Ethereum, ETH, smart contracts, DeFi, Layer 2 networks, staking, validators, and the real-world consequences of technical and financial failure.



