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

Lido stETH vs wstETH Tracking: The Rebase Is the Whole Problem (2026)

Portfolio·

Lido stETH vs wstETH Tracking: The Rebase Is the Whole Problem (2026)

stETH is a rebasing token — your balance grows daily as staking rewards accrue. wstETH is non-rebasing — the balance is fixed and value rides an increasing exchange rate. Why the rebase is a stream of balance changes a portfolio must characterise, and why wstETH moves the same value into a price.
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 Lido stETH rebasing model and the wstETH non-rebasing share/exchange-rate model · Last reviewed May 2026

Lido stETH vs wstETH Tracking: The Rebase Is the Whole Problem

stETH and wstETH are the same staked-ETH exposure with opposite on-chain behaviour: one grows your balance every day, the other never changes it. A tracker that does not know which it is holding gets either a stream of phantom inflows or a hidden gain. This guide is the rebase, the wrapper, and the tracking line between them.

TL;DR

  • stETH = rebasing: balance grows (≈ daily) as rewards accrue — no transfer, a recurring rebase.
  • wstETH = non-rebasing: balance fixed; value via an increasing wstETH↔stETH exchange rate (share system).
  • The rebase is a stream to characterise (reward accrual vs balance change), not a matchable receipt.
  • wstETH moves the value into a price — gain shows on unwrap/disposal (rate then vs at acquisition).
  • Tax of a rebase is jurisdiction-specific — track the signal, confirm tax separately.
  • Same exposure, two behaviours — a tracker must know which token it holds.

stETH: a balance that rebases

stETH is rebasing: as Lido staking rewards accrue, the stETH balance in the wallet increases, typically daily, with no transfer. The economic meaning is "rewards accrued," but the on-chain signal is a recurring balance change. A tracker must:

It is a continuous stream, not an event matched to one transaction — the recurring rebase is the defining tracking challenge.

wstETH: the value moves into a rate

wstETH is the non-rebasing wrapper: the balance is fixed, and rewards are reflected by an increasing wstETH→stETH exchange rate via an underlying share system. So there is no daily rebalance to track — but the value still grows, hidden in the rate. The gain surfaces when you unwrap or dispose of wstETH: the rate then versus the rate at acquisition. wstETH is often preferred in DeFi (lending, collateral, bridges) precisely because fixed balances integrate more cleanly.

Two behaviours, one exposure

stETHwstETH
BalanceGrows (rebase, ~daily)Fixed
Where value livesUnitsExchange rate
Tracking signalStream of rebase increasesRate change at unwrap/disposal
DeFi integrationHarder (rebasing)Cleaner (fixed balance)

A tracker that assumes the wrong one produces either phantom inflows (treating wstETH as if it rebased) or a hidden gain (treating stETH as static). It must detect which token is held and apply the matching model.

Tax is jurisdiction-specific

Whether each rebase is taxable income, and when (the rebase complicates "received/controlled"), is jurisdiction-specific and must not be hard-coded either way (see staking rewards accounting and yield farming tracking). The rebase/rate is the tracking signal; the tax characterisation is a separate, adviser-confirmed question, and the cost-basis method remains the jurisdiction-mandated one.

Practical guidance

  1. Detect stETH vs wstETH — never assume; the balance behaviour differs fundamentally.
  2. For stETH, model the rebase stream — read balances, characterise the accrual.
  3. For wstETH, track the exchange rate — gain realises on unwrap/disposal.
  4. Don't book rebases as acquisitions/inflows or wstETH as static-with-no-gain.
  5. Confirm rebase tax treatment per jurisdiction; apply the mandated cost-basis method.
  6. Reconcile to Lido (rebase index / wstETH rate) with an audit trail.

How vendor tools handle stETH/wstETH

Koinly and CoinTracker handle rebasing and wrapped staking tokens. Confirm the tool detects stETH vs wstETH, models the stETH rebase as accrual (not inflows/acquisitions), tracks the wstETH exchange rate for unwrap/disposal gain, and leaves the rebase tax characterisation to the jurisdiction setting — assuming the wrong token model is the recurring error.

How Wag3s helps

Wag3s Folio detects stETH vs wstETH, models the stETH rebase as characterised accrual rather than phantom inflows, tracks the wstETH↔stETH rate so the gain surfaces correctly on unwrap or disposal, and applies your jurisdiction's cost-basis method and rebase tax treatment. See the Folio product page.


Further reading

Sources

  • Lido — stETH is a rebasing token (balance changes, typically daily, as staking rewards accrue)
  • Lido — wstETH is the non-rebasing wrapper (fixed balance; value via an increasing wstETH↔stETH exchange rate using an underlying share system)
  • wstETH generally preferred in DeFi (lending/collateral/bridges) due to fixed balances; rebase tax treatment is jurisdiction-specific
Editorial disclaimer
This article is informational and does not constitute tax or accounting advice. Whether a rebase is income is jurisdiction-specific. Confirm treatment with a qualified adviser.