Liquid Staking Token Accounting: Rebasing vs Value-Accruing

Two entities can stake the same amount of ETH, hold liquid staking tokens worth the same yield, and still need entirely different bookkeeping — because the reward shows up in a different place depending on the token's mechanic. A rebasing LST like stETH grows in units: the balance on-chain climbs as rewards accrue. A value-accruing LST like rETH keeps the unit count fixed and lets its exchange rate to ETH rise instead. Same economics, different signal, and a system tuned to one will misread the other. This article works through the LST recognition model around that distinction, kept separate from the further complexity of restaking tokens, and hedged because the recognition is an auditor judgement.

The short version

• A liquid staking token (LST) is received from a liquid-staking protocol, represents the staked underlying plus accruing rewards, and stays transferable.
• The mechanic decides the accounting: a rebasing LST gains more units over time; a value-accruing LST keeps units stable while its value or exchange rate rises.
• The holder generally holds the LST, not the underlying directly, so the LST is typically the recognised asset; whether it is a distinct asset or a continuing interest is a derecognition analysis.
• Reward recognition follows the reward-at-control principle but surfaces differently — as added units or as embedded value — depending on the mechanic.
• An LST is distinct from a liquid restaking token (LRT), which adds a restaking layer and extra slashing and risk.
• This is a mechanic- and 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

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 represents staked assets plus base staking rewards. A liquid restaking token (LRT) adds a restaking layer — additional rewards alongside additional slashing and risk — and so carries extra recognition and risk considerations, covered in liquid restaking token accounting. Conflating the two understates the LRT's added complexity; each is accounted for 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.

Choosing and configuring a tool

The single most important thing an LST tool must do is tell the two mechanics apart, because a uniform rule will either double-count or miss rewards. Tools such as Cryptio and Bitwave can track LST positions and distinguish rebasing unit changes from value-accruing rate changes; before relying on one, confirm it can:

• identify each LST's mechanic from its contract type before applying any recognition logic, rather than assuming every position behaves the same way;
• read rebasing positions (stETH and similar) by their daily or periodic unit growth, valuing each incremental unit at the price on the accrual date;
• read value-accruing positions (rETH, cbETH, wstETH) by the change in exchange rate, not by balance, so a flat unit count is not mistaken for zero reward;
• keep the LST visible as its own asset rather than netting it against the original underlying, and keep any LRT (restaking) layer separate.

The tool models the mechanics; the recognition conclusion — distinct asset versus continuing interest — and the reward treatment remain auditor judgements.

How Wag3s fits in

Wag3s Ledger tracks LST positions by their rebasing or value-accruing mechanic, captures reward accrual in the right form for each, and keeps any LRT layer separate, with an audit trail throughout. The recognition and measurement conclusions stay with the entity's auditor — Ledger supplies the mechanic-aware record and is built to support that review rather than replace it. See the Ledger product page.

Worked example: stETH (rebasing) vs rETH (value-accruing)

These two LSTs are the canonical examples of the two mechanics. The same ETH staked through different protocols produces fundamentally different records.

stETH (Lido — rebasing). An entity deposits 100 ETH into Lido. It receives 100 stETH. Each day, Lido's rebasing mechanism credits additional stETH to the holder's balance in proportion to accrued staking rewards. After 30 days, the entity's stETH balance has grown from 100.000 stETH to, say, 100.320 stETH. The additional 0.320 stETH represents approximately 30 days of staking rewards.

In accounting terms, the 0.320 stETH units materialise as new token quantity — they are visible on-chain as an increased balance. The accounting question is: at what point is reward income recognised, and at what value are the additional units recorded? The common answer is recognition consistent with the reward-at-control principle: each day's reward accrual (the incremental units) is recognised as income at fair value when the holder obtains control. In practice this means daily accrual entries if the entity applies accrual accounting, or periodic entries at period-end, valued at the market price of stETH on each accrual date. The unit count is the accrual signal.

rETH (Rocket Pool — value-accruing). An entity deposits 100 ETH into Rocket Pool. It receives a quantity of rETH. The rETH quantity does not change over time — it stays fixed, for example at 95 rETH. Instead, the exchange rate between rETH and ETH increases: on day 1 the rate might be 1 rETH = 1.05 ETH; after 30 days it might be 1 rETH = 1.063 ETH. The reward is embedded in the rising exchange rate, not in new units.

In accounting terms, no new tokens appear in the wallet. The signal of reward accrual is the change in the exchange rate. Recognition depends on the framework: under a fair-value model, the position is remeasured at each period end at the new rETH/ETH exchange rate, and the change in value is recognised through profit or loss (or OCI, depending on classification). Under a cost model, the position is carried at cost and the reward is only recognised on redemption. Whether reward income is recognised periodically through remeasurement or only on exit is a framework-specific and fact-specific question — the point is that the trigger is the exchange rate, not a balance change.

The core accounting difference. For a portfolio that holds both stETH and rETH: the stETH balance will grow visibly on-chain, and each incremental unit is a recognisable reward event. The rETH balance will not grow — a naive balance scan would report no reward — but the exchange-rate increase is the reward. Both produce the same economic result (staked ETH earning yield), but the accounting signal is in a completely different place. A system that does not distinguish the two mechanics will either double-count stETH rewards (by treating the rebase as a new acquisition) or miss rETH rewards entirely (by seeing no new tokens).

Practical guidance for mixed LST portfolios

An entity holding both rebasing LSTs (stETH, wstETH unwrapped) and value-accruing LSTs (rETH, cbETH, ankrETH) in the same portfolio must apply different tracking logic to each:

• Configure the tracker to identify each LST's mechanic from its contract type before applying any recognition logic.
• For rebasing LSTs, capture daily or periodic unit changes as the reward signal; value each incremental unit at the market price on the accrual date.
• For value-accruing LSTs, track the exchange rate (e.g. rETH/ETH ratio from the contract) at each period-end; use the rate change as the remeasurement input.
• Never apply a uniform "token-count increased = reward received" rule across the portfolio — it works only for rebasing tokens and will produce zero reward recognition on all value-accruing positions.
• Note that wstETH is the wrapped, non-rebasing version of stETH; its mechanics resemble rETH (stable unit count, rising exchange rate) even though the underlying protocol is Lido. An entity that switches between stETH and wstETH will need both mechanics in its system.

Further reading

• Liquid Restaking Token Accounting (LRT)
• Staking Rewards Accounting
• Rebasing vs Non-Rebasing Token Tracking
• Validator / Node Operation Accounting
• Crypto Asset Account Classification
• DeFi Position Chart of Accounts

Sources

• IFRS — IAS 38 Intangible Assets: the cost and revaluation models under which a held LST is commonly measured, including how a value-accruing token's reward surfaces through remeasurement.
• IFRS — IFRS 9 Financial Instruments: the derecognition analysis for whether the LST is a distinct asset or a continuing interest in the staked underlying.
• FASB — ASU 2023-08: fair-value measurement for in-scope crypto assets under US GAAP, relevant to remeasuring LST positions.
• IRS — Rev. Rul. 2023-14 (staking rewards in gross income at dominion and control) and the Digital assets hub. US tax treatment of staking rewards through an LST is confirmed separately with a tax adviser.