> For the complete documentation index, see [llms.txt](https://docs.rip.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rip.xyz/hypurr-vault/nav-calculation.md).

# How NAV is calculated

Net asset value, or NAV, estimates the value of the assets backing rHYPURR. NAV per share sets the price for vault deposits and redemptions. It is not a guaranteed price for selling NFTs or swapping shares on a market.

## The calculation

```
Total NAV = vault WHYPE - pending deposits
          + manager WHYPE + estimated NFT portfolio value

NAV per share = total NAV / outstanding rHYPURR shares
```

The oracle counts WHYPE balances held by the vault and manager. Native HYPE deposits wrap automatically before entering the queue. Unwrapped HYPE in the manager wallet is not counted. Pending deposits are excluded because their shares have not been minted yet.

Contracts calculate in atomic units with 18 decimal places. A deposit divides its net assets by NAV per share to calculate shares. A redemption multiplies shares by NAV per share, then deducts its fee.

## Estimating NFT value

The oracle uses a collection-level weighted sale estimate for Hypurr holdings. It selects the latest eligible sale for each of up to 100 distinct NFTs within the past 30 days. Eligible observations have a positive price, cover one NFT, and are not flagged as outliers. Repeated sales of the same NFT can replace its observation but cannot fill several sample positions. Newer observations receive more weight by sale order. This is not a time-weighted average or an appraisal of each NFT's rare traits.

Thin trading, related-wallet activity, and missing sale data can affect the estimate. Outlier filters reduce some unusual-price influence; they do not prove that every sale is independent or genuine. The manager may receive more or less than the estimate when selling an NFT.

The app's weighted-floor chart reconstructs this distinct-NFT estimate using only sales available at each historical cutoff. Reconstructed chart history does not replace the NAV stored for a finalized epoch.

## Confidence

Each report includes a confidence score in basis points. The score reflects the amount and age of the price data. Fewer observations or older sales reduce confidence.

A high score is not a guarantee that the valuation is correct. Read it alongside the report timestamp and underlying market activity.

## From estimate to onchain price

1. The oracle reads liquid balances, pending deposits, NFT holdings, and recorded sales.
2. It calculates NAV and checks the proposed report against configured limits.
3. An authorized oracle signs the report and submits it to the vault.
4. The contract checks the signature, expiry, version, and drift bounds. It saves the accepted NAV for the current epoch and advances the epoch counter.
5. The keeper uses that saved price to process the epoch's requests.

NAV publication targets a 15-minute interval in staging and production. The app shows the next scheduled report from the running oracle. That schedule is a target; signing, confirmation, retries, or a rejected report can extend the gap between accepted updates. Stale NAV blocks new deposit and redemption requests until valid data is available.

## What the checks establish

A valid signature identifies an authorized signer. Drift limits bound the change allowed per report. Expiry and staleness checks limit the use of old data. An `inputsCommit` hash commits to the report's inputs for later comparison.

These checks do not establish that the source data or NFT valuation is correct. A hash alone does not reveal the inputs or prove the NFTs can sell at the reported value.

[View NAV history in the app](https://www.rip.xyz/rhypurr/nav-history) or read the [request pricing rules](https://docs.rip.xyz/hypurr-vault/deposit-redemption.md).
