Skip to content
Financial Context Wiki

Liquid Staking

Liquid staking pools stake assets through validators and issue transferable tokens that represent a claim on the pooled position. Understand LST accounting, rewards, redemption, market discounts, smart-contract risk, validator risk and DeFi composability.

Updated

For educational purposes only; not investment advice. An LST can lose value through protocol, validator, liquidity, market and DeFi risks.

Direct answer

Liquid staking is pooled staking that gives a participant a transferable token representing a claim on staked assets and, according to the protocol’s rules, their rewards and losses. This token is commonly called a liquid staking token (LST). It lets the holder transfer, trade or use the position in DeFi while validators continue operating the underlying stake.

An LST is not a second copy of the deposited asset and is not guaranteed to trade one-for-one with it. The protocol’s accounting rate, the amount and timing available through native redemption, and the secondary-market price are separate values. Fees, validator penalties, slashing, contract or oracle failures, withdrawal queues and market liquidity can make the holder receive less or wait longer than expected.

Ethereum itself does not natively provide pooled staking or an LST. Third-party protocols create those products, so their contracts, operators, governance, accounting and redemption rules add assumptions beyond Ethereum’s proof-of-stake protocol. The same analytical distinction applies to liquid staking on other proof-of-stake networks, although the exact validator and withdrawal rules differ by chain.

How it works

  1. Deposit or acquire the LST. A user deposits the native staking asset into a pool and receives an LST, or buys an existing LST from another holder. Buying on the market does not itself add new assets to the staking pool.
  2. Pool and operate stake. The protocol allocates assets to validators or node operators. The base chain determines validator activation, rewards, ordinary penalties, slashing and exit constraints; the liquid-staking protocol determines operator selection and how results are shared.
  3. Update the claim. Validator rewards and any execution-layer rewards included by the product increase pool assets. Penalties, slashing and other losses reduce them. Protocol and operator fees reduce the amount passed to LST holders.
  4. Choose an exit. A holder may sell the LST on a secondary market or request redemption under the protocol’s rules. A market sale depends on available liquidity and price; native redemption may require an asynchronous queue, validator exits and a later claim transaction.
  5. Use it in DeFi. A transferable LST may serve as collateral, enter a liquidity pool, be bridged or be restaked. Each additional contract and leverage layer adds risks that are not part of the underlying staking return.

Token accounting models

  • Rebasing model: the wallet’s token balance changes as the pool reports rewards or losses. Lido’s stETH is an implementation example.
  • Value-accruing model: the token balance normally stays fixed while the protocol’s amount of underlying assets per token changes. Lido’s wstETH is an implementation example.

Both models can represent similar economics, but integrations must use the correct balance or share accounting. The token contract, protocol dashboard and market quote may display different units; users should never infer redeemable value from the ticker alone.

Three values to keep separate

  • Accounting rate: the protocol-reported share of pooled assets attributable to each LST, after its accounting rules.
  • Redemption value: what the holder can actually claim, after fees, loss allocation, limits and queue rules, and when it becomes claimable.
  • Market price: what a buyer will pay now. Urgent selling, shallow liquidity, redemption delays or concern about the protocol can create a discount; strong demand for collateral or incentives can create a premium.

Staking yield is variable, not fixed interest promised by the token. A useful reconciliation is: base-chain rewards plus any disclosed execution rewards, minus validator losses, protocol and operator fees, and other product-specific deductions. Incentive tokens, lending interest or leveraged farming yield should be analyzed separately because they introduce different issuers and loss paths.

Worked example

Assume a hypothetical value-accruing pool receives 10 ETH, charges no entry fee and mints 10 LST, so its initial accounting rate is 1 LST = 1 ETH. This equality is a starting accounting convention, not a market guarantee.

After a period, suppose net validator rewards after fees are 0.50 ETH. With no other changes, pool assets become 10.50 ETH, the token supply remains 10 LST, and the accounting rate becomes 1 LST = 1.05 ETH. A holder of 4 LST therefore has a protocol-accounted claim of 4.20 ETH.

Now suppose native redemption is delayed and the deepest market quote is 1 LST = 0.97 ETH. Selling 4 LST immediately returns about 3.88 ETH before trading fees and slippage, even though the protocol accounting shows 4.20 ETH. Waiting for redemption may recover more, but exposes the holder to queue duration, further rewards or losses, and protocol operation. The apparent discount is not free arbitrage unless redemption eligibility, time, costs and failure risks are all included.

Risks and review checklist

Contract, accounting and governance

  • A bug, upgrade, compromised privileged role or incorrect integration can block redemption, misprice shares or lose assets. Audits reduce uncertainty but do not prove safety.
  • Oracle or accounting failures can report the wrong validator balance or apply rewards and losses incorrectly. Check who reports data, how disagreement is handled and what can be paused.
  • Governance may change fees, operators, modules, redemption rules or risk limits. Identify upgrade authority, timelocks, emergency powers and whether users can exit before a change takes effect.

Validators, operators and custody

  • Downtime reduces rewards and may incur ordinary penalties; slashable behavior can destroy part of validator stake and force an exit. Correlated failures can affect many validators together.
  • Operator, client, cloud, geographic or key-management concentration makes apparently separate validators share one failure mode.
  • Determine who controls deposit, signing and withdrawal credentials, how operators are admitted or removed, and whether losses are socialized across all holders.

Redemption, liquidity and price

  • Protocol redemption may be unavailable, capped, paused or queued. The LST may stop earning rewards while a request waits, depending on the protocol.
  • Secondary-market liquidity can disappear when many holders want the native asset at once. A displayed quote may not be executable for the intended size.
  • Do not call every discount a stablecoin-style “depeg.” First compare accounting rate, redemption entitlement and market price, then identify which one changed and why.

DeFi composition and leverage

  • Using an LST as collateral adds oracle, liquidation and lending-market risk. A market discount can trigger liquidation even if eventual redemption remains possible.
  • LST/native-asset liquidity pools add automated-market-maker, liquidity concentration and impermanent-loss exposure; advertised fees do not guarantee compensation.
  • Bridging, wrapping or restaking adds contracts, governance domains and withdrawal clocks. Trace the complete path back to the native asset rather than assuming every wrapper is equivalent.

Due-diligence questions

  • Is the LST a direct protocol claim, a custodial liability, a wrapper or a derivative of another LST?
  • Which rewards are included, which fees are deducted, and how are penalties and slashing allocated?
  • Is redemption permissionless, and what are the minimum, maximum, queue, pause and claim rules?
  • Are contracts verified and audited, and who can upgrade, pause, mint, burn or change accounting inputs?
  • How concentrated are stake, operators, clients, governance votes, oracles and market liquidity?
  • What would happen to a leveraged position if the LST traded below its accounting rate for longer than the loan can remain open?

Common misconceptions

  • “Liquid” means instantly redeemable at par. Transferability provides one exit route, but price and depth are market-dependent; protocol redemption can still be asynchronous.
  • The LST creates an extra copy of the asset. It represents a claim or share subject to product rules. Using both the asset claim and borrowed funds increases leverage rather than creating risk-free capital.
  • A rising token balance or exchange rate is guaranteed yield. Rewards vary, and fees, penalties, slashing or accounting losses can reduce net value.
  • A discount must close through arbitrage. Arbitrage requires a reliable redemption path, sufficient size, acceptable delay, funding and confidence that the claim will remain valid.
  • Using an LST in DeFi is the same risk as staking. It combines staking risk with the contracts, oracles, liquidity, leverage and governance of every added protocol.

Sources

Navigation

Search the wiki...