Valuing Receipt Tokens: Look-Through NAV for aUSDC, cUSDC, and Vault Shares

When you supply assets to a DeFi protocol, you receive a receipt token. Here is why pricing that receipt token at its market price gives you the wrong NAV — and what look-through valuation actually requires.

The Receipt Token Problem

Aave gives you aUSDC when you supply USDC. Compound gives you cUSDC. Yearn gives you yvUSDC. These receipt tokens represent your claim on the underlying asset, plus all accrued yield.

A naive portfolio tracker prices the receipt token by looking up its market price on a DEX or price feed. Sometimes this works — aUSDC trades very close to USDC at a 1:1 rate, adjusted for accrued interest. But for many protocol tokens, there is no liquid market. The yvUSDC price on a DEX reflects arbitrage activity, not the true redemption value of your vault shares.

More importantly, pricing receipt tokens at market gives you no insight into what you actually hold. The economic substance of your position is the underlying USDC plus accrued yield — not a claim on the secondary market price of a token.

Look-Through Valuation: The Correct Approach

Look-through valuation prices a position by unwrapping the receipt token to its underlying assets and pricing those instead.

For aUSDC: aUSDC_value = aUSDC_balance × aUSDC_exchange_rate × USDC_price

The exchange rate is stored on-chain in the Aave lending pool contract and increases monotonically as interest accrues. On any given block, the exchange rate precisely represents how many USDC each aUSDC can be redeemed for.

For more complex protocols, the unwrapping goes deeper. A Pendle PT is a zero-coupon claim on the underlying asset at maturity. A Uniswap V3 LP position is an NFT whose value is a function of both token prices and the current range boundaries — there is no simple exchange rate to look up.

Each protocol requires its own valuation logic. This is why DeFi NAV computation is a protocol coverage problem, not just a price-feed problem.

Accrued But Unclaimed Yield

Many DeFi protocols accrue yield continuously but only distribute it upon a claim transaction. Aave accrues interest directly in the aUSDC balance — the token rebases automatically. But Morpho Blue accrues interest in an internal accounting variable that only updates when a user interacts with the contract.

A NAV engine that only reads token balances misses accrued-but-unclaimed yield in protocols that do not rebase automatically. The fund’s true NAV includes this accrued yield — it is an asset of the fund, just not yet realized in a token transfer.

Correct look-through valuation reads the protocol’s internal accounting variables (not just the wallet’s token balance) and includes accrued yield in the position’s value.

Nested Protocols

The unwrapping problem gets harder when protocols are nested. A vault may hold yield-bearing LP tokens, which represent a liquidity position in a pool, which itself contains receipt tokens from a lending protocol.

At each layer, the engine must unwrap one step deeper and apply the correct exchange rate. Skipping any layer introduces error into the final USD valuation. Funds that use strategies like looping (borrowing and re-supplying repeatedly) or LP positions in pools containing yield-bearing assets will see significant NAV discrepancies if the protocol stack is not fully unwrapped.