Folio v0.9 — CEX + On-chain Consolidation is liveSee what's new →

Liquid Staking Token Accounting: Rebasing vs Value-Accruing (2026)

Accounting·

Liquid Staking Token Accounting: Rebasing vs Value-Accruing (2026)

A liquid staking token represents staked ETH plus rewards, but the accounting hinges on its mechanic — a rebasing token grows in units, a value-accruing one grows in price. They are not the same recognition. The LST model, distinct from restaking LRTs, hedged, as an auditor judgement.
Author avatar Wag3s TeamEditorial team specializing in Web3 finance, crypto tax, and DAO operations. Based in Zurich, Switzerland.

Reviewed by Wag3s Editorial Team — verified against the rebasing vs value-accruing receipt-token distinction for liquid staking tokens and its recognition consequences, distinct from restaking LRT accounting · Last reviewed May 2026

Liquid Staking Token Accounting: Rebasing vs Value-Accruing

A liquid staking token represents staked ETH plus rewards while staying transferable — but the accounting hinges on its mechanic. A rebasing LST grows in units; a value-accruing LST grows in price. Those are not the same recognition. This guide is the LST model — distinct from restaking LRTs — hedged, as an auditor judgement.

TL;DR

  • An LST = a token received from a liquid-staking protocol representing staked underlying + accruing rewards, transferable.
  • The mechanic decides the accounting: rebasing = more units over time; value-accruing = stable units, rising value/exchange rate.
  • The holder generally holds the LST, not the underlying directly → LST is typically the recognized asset; distinct-asset vs continuing-interest is a derecognition analysis.
  • Reward recognition follows the reward-at-control principle but surfaces differently (units vs value) per the mechanic.
  • Distinct from a liquid restaking token (LRT) (#144) — the LRT adds a restaking layer + extra slashing/risk.
  • Mechanic-/framework-specific auditor judgement. Not accounting advice.

What an LST is

A liquid staking token (LST) is received when staking through a liquid-staking protocol, representing the staked underlying plus accruing rewards while remaining transferable. The questions: how to recognize the LST relative to the underlying, and how reward accrual is reflected — which depends on rebasing vs value-accruing. It is distinct from a restaking LRT.

Rebasing vs value-accruing

MechanicReward appears asAccounting consequence
RebasingMore units (≈stable peg)Accrual = additional units
Value-accruingStable units, rising value/rateAccrual = price/exchange-rate appreciation

These produce different recognition and measurement patterns under the applicable model, so identifying the mechanic is the first step (consistent with rebasing vs non-rebasing token tracking). Auditor judgement.

Is the LST a separate asset?

Generally the holder holds the LST, not the underlying directly, so the LST is typically the recognized asset; whether it is a distinct asset or a continuing interest in the staked underlying depends on protocol mechanics and the framework's recognition/derecognition analysis. Silently netting the LST against the original asset hides the position — recognition is fact-specific, auditor-confirmed.

Reward recognition through an LST

The reward is recognized consistent with the reward-at-control principle, but the form differs: rebasing → the additional units are the accrual; value-accruing → accrual is embedded in the changing value/exchange rate and surfaces through the applicable measurement model. Whether reward income is recognised separately vs captured through remeasurement is framework-specific, an auditor judgement.

LST vs LRT

An LST = staked assets + base staking rewards. A liquid restaking token (LRT) adds a restaking layeradditional rewards and additional slashing/risk — with extra recognition/risk considerations (#144). Conflating the two understates the LRT's added complexity — each on its own mechanics, auditor-confirmed.

Practical guidance

  1. Identify the mechanic first — rebasing (units) vs value-accruing (value).
  2. Recognize the LST as the held asset; assess distinct-asset vs continuing-interest.
  3. Don't net the LST against the original asset — keep the position visible.
  4. Reflect reward per the mechanic — added units vs embedded value appreciation.
  5. Keep LST and LRT separate — the LRT adds a restaking/slashing layer.
  6. Confirm recognition/measurement with your auditor — mechanic-/framework-specific; not accounting advice.

How vendor tools handle LSTs

Cryptio and Bitwave can track LST positions, distinguishing rebasing unit changes from value-accruing rate changes. Confirm the tool models the specific LST mechanic; the recognition (distinct asset vs continuing interest) and reward treatment are auditor judgements.

How Wag3s helps

Wag3s Ledger tracks LST positions with the rebasing-vs-value-accruing mechanic and reward accrual, distinct from any LRT layer, with an audit trail — while the recognition and measurement stay auditor-confirmed. See the Ledger product page.


Further reading

Sources

  • A liquid staking token (LST) represents staked underlying + accruing rewards while transferable; recognition depends on rebasing (more units) vs value-accruing (rising value/exchange rate) mechanic — identifying the mechanic is the first step (auditor judgement)
  • The holder generally holds the LST not the underlying directly → LST typically the recognized asset; distinct-asset vs continuing-interest is a framework recognition/derecognition analysis (don't silently net against the original asset)
  • Reward recognized consistent with the reward-at-control principle but surfaces differently by mechanic (added units vs embedded value appreciation); separate income vs remeasurement is framework-specific
  • An LST (base staking) is distinct from a liquid restaking token/LRT (adds restaking layer + extra slashing/risk) — accounted on its own mechanics; auditor-confirmed, not accounting advice
Editorial disclaimer
This article is informational and does not constitute accounting advice. LST recognition depends on the token mechanic and the applicable framework and is an auditor judgement. Confirm with your auditor.