Monetary systems

Liquid staking

Liquid staking gives the depositor a transferable claim while validators earn rewards. Lido’s claim is a share of pooled ether. stETH rebases. wstETH does not. Getting ETH back is a queue finalized by an oracle, and the operators running validators are a separate trust assumption.

Published
Last verified
Reading time
About 2 min

Staking locks an asset in a validator so the consensus protocol will pay rewards and charge penalties. Liquid staking issues a token against that lock so the depositor can transfer the claim. The lock remains. The token is not the validator key, and selling the token does not exit the validator.

Lido is the concrete system. The shape is general: a pool, a share, an operator set, a reporter, and an exit queue.

Simplified model Liquid staking deposit and exit
  1. DepositThe user sends the staking asset and receives a liquid claim. The claim is a share of the pool, not a receipt for a named validator.
  2. DelegationThe protocol assigns stake to operators or validators. Rewards and penalties land in the pool.
  3. Accounting reportAn oracle or similar reporter updates the pool’s asset balance. Share value changes for every holder.
  4. ExitWithdrawal is a request, then a wait, then a claim. It is not the same transaction as a transfer of the liquid token.

This is the pooled shape, such as Lido Core. A Lido V3 staking vault is one owner and one operator, and its validator exit is not this queue. The reporter and the operator set remain trust boundaries. Transferring the liquid token does not by itself unstake the underlying asset.

The share

Lido Core mints shares when ETH is submitted. The stETH balance is shares times pooled ether over total shares. Rewards increase pooled ether. A slashing decreases it. Every Core holder is in one pool, so a penalty is socialized across shares rather than charged to a validator that user picked. Users do not pick a validator in the basic Core deposit. The protocol assigns stake to operators.

Lido V3 staking vaults are the documented exception to that socialization. One vault has one owner and one operator. It can mint stETH against its own reported value, up to a reserve ratio, and the technical design says operator-group losses are supposed to stay in that group up to a DAO-set level. The minted token is still stETH. The exit of the underlying validators is the vault’s exit, described on the Lido page, not a second share token.

That socialization is the product. It is also the risk. One operator’s slashing changes the share rate for holders who never chose that operator. Module design and operator limits are how the protocol tries to bound the blast radius. They are governance parameters. The share math will apply whatever the report contains.

wstETH is the same share with a fixed balance. The wrapper locks stETH and mints the share count. Use it where a rebase would corrupt internal accounting. Do not use it as if it were a different asset with a different exit. Unwrapping or requesting withdrawal returns to the same queue.

The exit

A transfer finds a buyer. A withdrawal asks the protocol for ETH. Lido’s queue mints an NFT, waits for the accounting report to finalize the request, and pays ETH on claim. The wait includes Ethereum’s own exit limits. Before protocol withdrawals existed, the only exit was the market, and stETH could trade below the share value. That discount is not available as a historical curiosity only. Any time the queue is long or paused, the market price and the share rate can diverge again. A lending protocol that prices stETH at the share rate and ignores the queue is assuming an exit the seller may not have.

What liquid staking is not

It is not a stablecoin. The token tracks ether, including penalties, not a dollar. It is not an AMM LP token. There is one underlying asset, not a pair. It is not a custody receipt for a named machine. The oracle that reports consensus balances, and the governance that can upgrade the staking contracts or change operators, sit beside the ERC-20 interface. Dual Governance is Lido’s attempt to give the stakers time when those upgrades are contentious. It is described in the exit guide. It does not remove the operators or the oracle.

Sources

  1. Lido tokens integration guide
    Documentation · Lido
  2. wstETH contract documentation
    Documentation · Lido
  3. WithdrawalQueue ERC-721
    Documentation · Lido
  4. AccountingOracle.sol at core v3.0.2
    Source code · Lido
  5. stVaults technical design
    Documentation · Lido