Lido: Liquid Staking for Ethereum

Document “Lido: Ethereum Liquid Staking”
Publisher Lido
Date October 2020
Subject A proposed pooled liquid-staking design for Ethereum’s Beacon Chain launch
Original paper Lido: Ethereum Liquid Staking (PDF)

This page summarizes Lido’s October 2020 design paper. It describes the protocol as it was proposed around the launch of Ethereum’s Beacon Chain, when withdrawals from validator deposits were not yet available. It is a historical design document, not a complete description of today’s Lido or Ethereum. CryptoGloss summarizes the paper and current documentation; it does not claim authorship of the original work.

Original paper Original paper
Directories Ethereum Whitepapers & Research

Lido’s central idea was to pool ETH from users who did not want to operate validators or meet the then-required 32 ETH solo-staking deposit. In return, the protocol issued stETH, a transferable receipt token representing a share of pooled, staked ETH and its net rewards. The proposal aimed to make staking more usable while the Beacon Chain was still separate from Ethereum’s execution layer and users could not directly withdraw their validator deposits.

What the 2020 paper proposed

Under the initial design, users submitted ETH to Lido’s contracts and received stETH. The Lido DAO selected node operators, who ran validators using the pooled deposits. The paper describes stETH accounting as reflecting the pooled ETH, rewards, and penalties such as slashing. It also proposed a starting protocol fee of 10% on staking rewards, with the DAO able to change it. That is a statement about the 2020 proposal; it should not be read as a current, universal fee split.

The paper’s key tradeoff was liquidity: stETH could be transferred or used in other applications while the underlying ETH remained in validator staking. That token did not remove staking risk or make every holder’s position identical to cash. It added a smart-contract and governance layer between the holder and Ethereum’s validator system.

How stETH accounting differs from its market price

In Lido Core, stETH uses share-based accounting. Oracle reports update protocol balances and normally change holders’ displayed stETH balances as rewards or penalties are reflected. The daily balance change is called a rebase. It describes the token’s accounting, not a promise that one stETH will always sell for one ETH on an exchange.

That distinction matters. Lido’s protocol redemption and a secondary-market trade are separate exit routes. A holder may request ETH through Lido’s withdrawal process, subject to its queue and Ethereum’s validator-exit throughput, or sell stETH on a trading venue. The venue price can move below or above the protocol’s accounting value, particularly when liquidity is thin or redemption takes time. Ethereum’s withdrawals were enabled in April 2023, so the paper’s original “withdrawals are not yet available” setting is no longer current.

wstETH is a non-rebasing wrapper used by applications that prefer a fixed token balance. Its balance does not grow with each stETH rebase; instead, the amount of stETH represented by each wstETH changes over time. Wrapping changes token format, not the underlying staking, market, or protocol risks.

Operators, modules, and governance

The 2020 proposal centered on DAO-selected operators. Today’s Lido Core uses a StakingRouter that allocates deposits among staking modules, including curated and community-oriented designs. Modules have their own operator sets and parameters, and are registered through DAO governance. This is more flexible than describing Lido as one fixed list of professional operators, but it still means the protocol’s governance and module structure matter to users.

Concentration is therefore a legitimate network-level topic, but it needs precise language. Lido’s governance, the operators running validators, and the validators’ consensus-layer signing keys are different actors. A protocol’s share of pooled stake alone does not establish that one person can directly command all validators. Relevant questions include how widely operators and infrastructure are distributed, how modules are admitted and limited, and what happens during correlated failures or governance disputes.

What changed with Lido V3

Lido V3 launched on Ethereum mainnet on January 30, 2026, introducing stVaults alongside the existing Lido Core pool. A stVault can have a defined owner or curator, selected node operators, and configurable operating and fee parameters; it may use stETH liquidity, depending on its design. A stVault is not simply another name for the original pooled Core model, and its specific rules and risks depend on the vault.

It is useful to keep three things separate: the October 2020 paper’s proposed Core design; the current Core pool and its modular staking system; and V3’s configurable stVaults. The paper remains useful for understanding the original motivation and token model, while current documentation is needed for present-day contracts and product behavior.

Risks and limits

  • Smart-contract and oracle risk: pooled staking depends on contracts and accounting reports behaving as intended.
  • Validator risk: downtime, penalties, or slashing can reduce staking outcomes under protocol rules.
  • Liquidity and timing risk: direct protocol withdrawals can wait on Lido’s process and Ethereum’s exit capacity.
  • Market risk: a tradable stETH or wstETH price can diverge from ETH, and a swap may incur slippage.
  • Governance and operator concentration: module choices, fees, and operator distribution influence the system’s risk profile.

Liquid staking is also different from solo staking: a token holder relies on a protocol, its contracts, operators, and governance rather than directly controlling a validator. The 2020 paper explains why Lido was proposed; it cannot by itself answer whether a user should stake today.

Related Terms

Related Articles

See Also

Sources