Rebasing vs Non-Rebasing Token Tracking: Where the Yield Hides

The same staked-ETH or lending yield can reach you two ways: as more tokens (a rebase) or as a higher price per token (a wrapper). They are economically identical and mechanically opposite — and a tracker that confuses them reports a fiction. This guide is the general model behind stETH/wstETH and aTokens.

TL;DR

• Rebasing: balance changes with no transfer — units grow to reflect yield (stETH, Aave aTokens).
• Non-rebasing wrapper: balance fixed; value via an increasing exchange rate / index (wstETH-style).
• Same exposure, opposite balance behaviour — the tracker must detect which before tracking.
• Confuse them → phantom inflows (wrapper treated as rebasing) or a hidden gain (rebasing treated as static).
• A rebase is not a transaction — read derived balance / index, not transfer events.
• Tax of a rebase is jurisdiction-specific — track the signal, confirm tax separately.

Two ways to deliver the same yield

Yield-bearing crypto reaches the holder in one of two shapes:

stETH rebases (units grow daily); wstETH wraps it (fixed units, rising rate). An Aave aToken accrues interest into the balance (rebasing-style). Different tokens, one underlying pattern: yield as units vs yield as price.

Why confusing them produces a fiction

• Wrapper treated as rebasing → the tracker invents inflows that never happened (the fixed balance "should" be growing, so it fabricates).
• Rebasing treated as static → the tracker hides the yield until disposal and misstates both balance and gain.

This is not cosmetic: it changes the reported position and, downstream, every gain/income figure derived from it. Detecting the model is the prerequisite, exactly as in the stETH/wstETH case generalised.

A rebase is not a transaction

The core challenge: a rebase changes the balance with no discrete transfer, so transfer-only ingestion misses it. A correct tracker:

• for a rebasing token, reads the derived balance and attributes the change;
• for a wrapper, reads the index / exchange rate and values accordingly;
• never waits for a transaction that never comes.

The same "don't trust a transfer-only view" rule as Aave V3 accrual and DeFi position reconciliation.

Tax is jurisdiction-specific

Whether each rebase is income (and when) is jurisdiction-specific and must not be hard-coded either way (see staking rewards accounting and cost-basis methods). For a wrapper, the gain typically surfaces on unwrap/disposal via the rate change. The rebase/rate is the tracking signal; the tax characterisation is separate and adviser-confirmed. The cost-basis method stays the jurisdiction-mandated one — the models only change where the value appears (units vs rate).

Practical guidance

1. Detect rebasing vs non-rebasing per token — never assume.
2. For rebasing, read derived balances and attribute the accrual.
3. For wrappers, track the index/exchange rate; gain realises on unwrap/disposal.
4. Never invent inflows for a fixed-balance wrapper, or treat a rebaser as static.
5. Confirm rebase tax treatment per jurisdiction; apply the mandated cost-basis method.
6. Reconcile to the protocol (rebase index / wrapper rate) with an audit trail.

How vendor tools handle rebasing tokens

Koinly and CoinTracker handle rebasing and wrapped yield tokens. Confirm the tool detects the model per token, reads derived balances / index (not transfer-only), does not invent inflows for wrappers or hide yield for rebasers, and leaves the rebase tax characterisation to the jurisdiction setting — model confusion is the recurring error across stETH, aTokens and their wrappers.

How Wag3s helps

Wag3s Folio detects rebasing vs non-rebasing per token, reads derived balances for rebasers and the index/rate for wrappers, avoids both phantom inflows and hidden gains, and applies your jurisdiction's cost-basis method and rebase tax treatment — one consistent model across stETH/wstETH, aTokens and similar. See the Folio product page.

Further reading

• Lido stETH vs wstETH Tracking
• Aave V3 Position Tracking
• DeFi Lending Position Tracking
• Staking Rewards Accounting
• DeFi Position Reconciliation
• Crypto Cost Basis Methods 2026

Sources

• Rebasing model: balance changes with no transfer to reflect yield (stETH daily rebase; Aave aToken interest-in-the-balance)
• Non-rebasing wrapper model: fixed balance; value via an increasing exchange rate / index (wstETH-style share system)
• A rebase is not a discrete transfer (read derived balance/index); rebase tax treatment jurisdiction-specific; cost-basis method unchanged