What Is NAV Reporting for Crypto Funds?
How digital asset funds calculate Net Asset Value across wallets, chains and DeFi protocols — and why manual spreadsheet NAV breaks at scale.
Net Asset Value is the single number a fund's investors, auditors and administrators all agree to look at. For a traditional fund it is close to arithmetic. For a digital asset fund holding positions across fifteen chains and forty protocols, arriving at that number is the hard part.
What NAV means for a digital asset fund
NAV is total assets minus total liabilities, divided by units outstanding. The definition does not change because the assets are on-chain. What changes is the difficulty of enumerating the assets in the first place.
A crypto fund's balance sheet is spread across:
| Position type | Where it lives | Why it is easy to miss |
|---|---|---|
| Spot holdings | Wallets, exchanges, custodians | Multiple addresses per strategy |
| Lending positions | Aave, Morpho, Compound | Principal and accrued interest are separate |
| LP positions | Uniswap, Curve, Balancer | Value is a function of pool composition |
| Staked assets | Native staking, liquid staking | Rewards accrue continuously |
| Vesting or locked | Escrow, veTokens | Illiquid, but still an asset |
Why spreadsheet NAV breaks
Manual NAV works at ten positions. It fails at two hundred, for reasons that compound:
- Pricing is inconsistent. Two analysts pull a token price from two venues at two timestamps and produce two different NAVs.
- Protocol positions are opaque. A balance query returns an LP token, not the underlying assets it represents.
- Reconciliation is unbounded. Every new chain the fund touches multiplies the number of sources someone has to check by hand.
What an automated NAV process needs
Any system that produces an auditable NAV has to do four things:
- Discover every position the fund holds, without being told where to look.
- Value each position from a consistent, timestamped price source.
- Snapshot the result daily, immutably, so prior NAVs can be re-derived.
- Produce an export an auditor accepts without re-keying it.
Points three and four are where most in-house tooling stops. A number you cannot reproduce six months later is not a number an auditor can sign off on.
Further reading
Enumerating positions is the hard half of NAV, and it is its own subject: Tracking DeFi Positions Across Multiple Chains covers why lending, LP and staking positions resist a simple balance query.
If you would rather pull the underlying data yourself, see How to Pull Portfolio Data From a Crypto API.
Once the NAV exists, the movements behind it still have to be booked and evidenced: Crypto Transaction Reconciliation for Audits.
For how NAV fits the wider operating stack, see Crypto Portfolio Management for Funds.
Keep reading
NAV ReportingWhat SOC 2 Type 2 Means for Portfolio Data
Octav is SOC 2 Type 1 and Type 2 compliant. What the difference actually is, what auditors test, and why it matters when a vendor reads your fund's wallets.
2 min read
NAV ReportingSecurity Questions to Ask a Portfolio Vendor
What a fund's security review should cover before connecting wallets to a portfolio provider — key custody, read-only access, SOC 2 and data residency.
2 min read
NAV ReportingTransparency Dashboards for DeFi Treasuries
Public NAV and position pages let DAOs, vaults and treasuries prove holdings without granting access. What belongs on one and what to leave off.
2 min read