Liquid staking

Reading depth

Each view includes the earlier layers; the complete engineer or auditor page is shown by default.

BeginnerCore purpose and mental modelPractitionerAdds mechanisms and economicsEngineer or auditorAdds state and verification

Dependency check

Advanced detail assumes prerequisite knowledge

Before using practitioner mechanisms or engineer and auditor checks, review any unfamiliar dependency. These paths come from canonical depends_on relationships; Web3 Academy does not track completed lessons.

Review 8 dependencies

• AssetRequired through Asset versus claim

  1. Liquid staking
  2. Claim token
  3. Asset versus claim
  4. Asset

• ClaimRequired through Asset versus claim

  1. Liquid staking
  2. Claim token
  3. Asset versus claim
  4. Claim

• TokenRequired through Asset versus claim

  1. Liquid staking
  2. Claim token
  3. Asset versus claim
  4. Token

• Asset versus claimRequired through Claim token

  1. Liquid staking
  2. Claim token
  3. Asset versus claim

• Claim tokenDirect prerequisite

  1. Liquid staking
  2. Claim token

• Proof of stakeRequired through Validator

  1. Liquid staking
  2. Staking return
  3. Validator
  4. Proof of stake

• ValidatorRequired through Staking return

  1. Liquid staking
  2. Staking return
  3. Validator

• Staking returnDirect prerequisite

  1. Liquid staking
  2. Staking return

Liquid staking pools or delegates staked assets and issues a transferable claim whose value reflects the protocol's controlled stake, rewards, fees, and losses.

Category: StakingStacked bars category cue

System record

Start with the economic purpose, participants, resources, and entitlements before studying implementation detail.

Why it exists

Liquid staking lets users hold a composable claim while underlying stake remains active, reducing operational and liquidity barriers without removing validator or redemption risk.

Traditional-finance analogy

Transferable share in a pooled, income-producing asset vehicle is the closest comparison recorded for this concept.

Where the analogy stops

• The token can rebase or accrue a changing exchange rate and can be used as collateral in permissionless protocols before the underlying stake exits.
• Redemption depends on validator exits, queues, protocol accounting, oracles, governance, and available liquidity rather than a guaranteed cash-on-demand claim.

Main actors

• ActorDepositor or claim-token holder
• ActorLiquid-staking protocol or pool
• ActorValidator operators
• ActorOracle or accounting reporters
• ActorWithdrawal queue and liquidity providers
• ActorGovernance or emergency administrator

Assets and claims

Assets — controlled or transformed resources

Assets are resources the mechanism moves, holds, values, or transforms.

• AssetDeposited staking asset
• AssetControlled validator stake
• AssetStaking rewards and fees
• AssetLiquid-staking claim token

Claims — entitlements and corresponding dependencies

Claims are rights to value, repayment, redemption, control, or another party's performance; each depends on an obligation or system that must honor it.

• ClaimPooled share or redeemable staking claim
• ClaimQueued withdrawal claim

Liquid staking keeps underlying assets active in staking while issuing a transferable pooled claim to users.

Why it exists

Direct staking can require technical operation, minimum position sizes, and activation, exit, or unbonding delays. Liquid staking pools operations and gives users a composable token, while preserving rather than eliminating validator, claim-accounting, withdrawal, liquidity, and governance risk.

Traditional-finance analogy

A transferable share in a pooled, income-producing asset vehicle is a useful analogy. A liquid-staking token can rebase or accrue a changing exchange rate and can be used permissionlessly as collateral. Redemption depends on validator exits, protocol queues, accounting, oracles, and governance rather than a guaranteed cash-on-demand claim.

Keep three values separate

1. Controlled staking assets are the protocol’s active, pending, exited, or liquid assets net of obligations.
2. Claim entitlement is the holder’s proportional or rebasing right under protocol accounting.
3. Secondary-market price is what traders currently pay and can be above or below modeled redemption value.

For a non-rebasing share model:

claimValuePerShare
= netControlledStakingAssets / totalClaimShares

netControlledStakingAssets must define pending deposits, rewards, fees, penalties, slashing, withdrawal reserves, and deficits. A rebasing token may change balances instead of the displayed per-share rate, but it still needs a canonical share-accounting unit and explicit rounding.

Actors, assets, and claims

Depositors provide the staking asset and receive a claim token. The protocol selects or delegates to validator operators. Oracles or accounting reporters bring validator and reward state into contract accounting. A withdrawal queue converts claims back to underlying when capacity and network exit rules permit; liquidity providers offer a separate immediate market route.

The deposited and controlled stake are assets of the protocol or position. The liquid-staking token is a pooled share or redeemable claim, not the same asset. A queued withdrawal can become a separate, time-dependent claim.

Step-by-step mechanism

1. Accept an eligible staking asset and validate deposit limits and recipient.
2. Mint claim shares using pre-deposit net assets and supply under the selected accounting model.
3. Activate or delegate underlying stake across authorized validators.
4. Report rewards, fees, penalties, exits, and slashing into controlled-asset accounting.
5. Rebase balances or update the asset-per-share conversion without changing ownership silently.
6. Allow transfer and DeFi use while exposing price, oracle, bridge, and collateral dependencies.
7. On withdrawal, burn or lock the claim, queue any required validator exit, reserve assets, and settle once claimable.

State transition and flows

Table: State transition and flows

Stage	Underlying staking assets	User claim
Deposit	Enter protocol or pending stake	Shares or rebasing claim minted
Active staking	Assigned to validator positions	Entitlement reflects net pooled accounting
Reward or penalty	Controlled assets rise or fall	Balance or conversion rate adjusts
Withdrawal request	Assets may remain bonded until exit	Token locked or burned; queued claim created
Claim	Reserved asset leaves protocol	Withdrawal claim settles

Capital flow moves deposits, stake, rewards, fees, penalties, liquidity trades, and withdrawals. Claim flow mints, transfers, wraps, queues, and burns staking claims. Information flow carries validator balances, share rates, oracle reports, queue state, and market prices. Return flow carries network issuance, user fees, or service payments through operator and protocol deductions into the pooled claim. Risk flow propagates into lending, AMMs, vaults, bridges, and other systems that treat the claim as collateral or principal.

Return source and loss allocation

Underlying return comes from the network’s staking sources, net of operator and protocol fees, penalties, and slashing. A secondary-market premium or discount comes from traders and liquidity, not validator rewards. Validator loss reduces the pool or claim according to accounting; insurance or treasury support is not guaranteed unless coverage and capacity are explicit.

Engineer or auditor lens

Test first deposit, zero assets or shares, donation and rounding attacks, rebases, negative reports, report quorum and freshness, operator fees, validator activation and exit, withdrawal ordering, claim finalization, reserved assets, repeated claims, wrapper conversions, bridge representations, pausability, upgrades, and downstream oracle assumptions. Never mint valuable shares against zero contributed value or settle more underlying than burned entitlement.

Lido’s token integration guide documents one protocol’s rebasing stETH, non-rebasing wstETH shares, oracle reports, and queued withdrawal claims. Those mechanics, controls, and historical behavior do not define every liquid-staking token. The documentation was reviewed 2026-08-10.

Common misunderstandings

• “Liquid staking makes staked assets liquid.” It creates a transferable claim; the underlying can remain bonded and protocol redemption can remain queued.
• “One token always equals one underlying.” Share rate, rebases, fees, penalties, slashing, rounding, and market discounts can separate values.
• “Using the token as collateral is free composability.” It adds oracle, liquidation, liquidity, integration, bridge, and correlated-loss paths.

Compare the token with claim token and added obligations with restaking.

Machine-readable model

Key equations

Canonical expressions come from the structured concept record. KaTeX renders the notation, while the plain-text expression and variable table keep its meaning and units inspectable without JavaScript. Read the narrative above for the model's domain, assumptions, and rounding rules.

1. Equation 1

   $$\mathrm{claimValuePerShare} = \frac{\mathrm{netControlledStakingAssets}}{\mathrm{totalClaimShares}}$$

   Plain-text equation: claimValuePerShare = netControlledStakingAssets / totalClaimShares

   Variables and units for equation 1

   Symbol	Meaning	Unit
   claimValuePerShare	Claim Value Per Share	asset or valuation units per share
   netControlledStakingAssets	Net Controlled Staking Assets	staking-asset units
   totalClaimShares	Total Claim Shares	share or claim units

Assurance contract

Security properties

These structured statements define desired behavior. Their stable IDs can bind tests, invariants, specifications, audit findings, or proof results without turning descriptive review advice into an assurance claim.

Desired · not evaluated: No test, audit, or proof result is implied until scoped evidence is linked to this property.

1. SP-01Desired · not evaluated

   Deposits and withdrawals reconcile controlled staking assets, claim shares, queued claims, fees, rewards, penalties, and losses

2. SP-02Desired · not evaluated

   Rebase and non-rebasing share representations preserve each holder's proportional entitlement subject to explicit rounding

3. SP-03Desired · not evaluated

   A claim token cannot imply immediate one-for-one redemption when queues, losses, fees, or capacity make that untrue

4. SP-04Desired · not evaluated

   Validator, oracle, operator, governance, upgrade, bridge, and withdrawal authorities remain inspectable and bounded

Prerequisites

Direct dependencies recorded by this concept's canonicaldepends_on relationships.

• Claim tokenPath 5

  A claim token records a transferable or account-bound entitlement to assets, income, redemption, governance, or another protocol-defined benefit.

• Staking returnPath 65

  Staking return compensates validation and capital-at-risk through protocol issuance, transaction fees, service payments, or incentives minus costs and losses.

Learn next

Concepts that directly depend on this one, ranked by the recommended learning path. Check each page for additional prerequisites.

No concept directly builds on this page in the current graph; use the guided learning paths to choose another branch.

Knowledge check

Quiz

Answer in your own words, then open the model answer.

What problem does Liquid staking exist to address?

Model answer

Liquid staking lets users hold a composable claim while underlying stake remains active, reducing operational and liquidity barriers without removing validator or redemption risk.

Mark as understood