Education Hub
Core Architecture

NAV oracles: how illiquid RWA collateral gets priced on-chain


A price oracle for ETH just reads deep, continuous market data. A price oracle for a private credit portfolio has no such data to read, because there's no live market quoting the value of a pool of loans second by second. Pricing illiquid real-world assets on-chain requires a fundamentally different kind of oracle, one built around periodic valuation rather than continuous market prices.

How it works

A NAV (net asset value) oracle brings a periodically calculated valuation of an illiquid asset on-chain, rather than a continuously observed market price. The valuation itself is produced off-chain through the same processes traditional finance uses for illiquid assets: an administrator or valuation agent assesses the portfolio's worth based on the performance of the underlying loans, expected cash flows, default and recovery experience, and applicable accounting standards. That produced NAV is then published on-chain through the oracle at defined intervals, daily, weekly, or per reporting period, depending on the asset.

The trust question is sharper here than for a market-price oracle, because the value isn't independently observable the way a DEX price is. Anyone can verify ETH's price against the market; almost nobody can independently verify a private credit portfolio's NAV without access to the underlying loan data. That makes the credibility of the valuation process, and the ability to verify it, the entire ballgame. A NAV oracle is only as trustworthy as the valuation methodology behind it and the proof that the reported number actually reflects the underlying assets.

This is why NAV oracles for institutional RWA lean heavily on independent valuation, defined and disclosed methodology, and verifiable attestation. The reported NAV needs to come from a credible, ideally independent source, follow a methodology that's stated in advance rather than improvised, and be backed by verifiable evidence about the underlying assets rather than a bare assertion of value.

Why it matters

The NAV oracle is the linchpin that makes illiquid RWA usable as on-chain collateral at all. A lending market, a vault, and a redemption mechanism all need to know what the collateral is worth; for illiquid assets, the NAV oracle is the only source of that number. If it's wrong, manipulated, or stale, every downstream calculation, LTV, redemption value, LP NAV, is wrong with it, which is why the integrity of this single input carries so much weight.

It's also where the "verification gap" in tokenized real-world assets is most visible. Tokenizing an asset puts a token on-chain, but the token is only as meaningful as the proof that it actually represents what it claims, held in the amount it claims, worth what the NAV says. A NAV oracle without credible, verifiable backing is just a number someone typed in, and the difference between that and a genuinely trustworthy valuation is the difference between real RWA infrastructure and tokenized wishful thinking.

Where this shows up in Rekord

Pricing illiquid RWA collateral through credible, verifiable NAV oracles is central to what Rekord's Trust Layer exists to make possible: reported values backed by proof about the underlying assets, not bare assertion. For the market-price counterpart used for liquid crypto collateral, see Price oracles for institutional lending: multi-source feeds, deviation checks, staleness protection.