Net Asset Value in Crypto: What a Defensible NAV Actually Requires
A traditional fund strikes its net asset value against a closing bell. Markets shut, an official closing price is published, and every asset is valued at that number. Nobody debates which price to use, because there is only one.
Crypto funds have no closing bell. Markets trade continuously across dozens of venues, each with its own price, and there is no official close to strike against. Every crypto fund that publishes a NAV has made a series of decisions, when to value, from which source, how to handle assets that barely trade, and most investors never see those decisions or know how much they matter.
This article explains what NAV is, why crypto makes it genuinely difficult, and what a NAV needs in order to survive an audit, an allocator's due diligence, or a dispute.
What net asset value is
Net asset value is the total value of a fund's assets minus its liabilities. Divided by the number of units or shares outstanding, it gives the NAV per unit: the price at which investors subscribe and redeem, the number performance is measured against, and the figure that appears in every report.
The arithmetic is simple. The difficulty lies entirely in the first term, the value of the assets. For a fund holding listed equities, that value is the closing price on the primary exchange, multiplied by the quantity held. For a fund holding crypto, "the closing price" does not exist and "the primary exchange" is a matter of judgement.
Why NAV is harder for crypto funds
Four features of crypto markets turn a mechanical calculation into a set of decisions.
There is no close. Crypto trades 24 hours a day, seven days a week, every day of the year. A fund has to decide what "end of day" means, 4 p.m. New York, midnight UTC, or some other convention, and then apply that consistently through weekends, public holidays and daylight-saving changes. Without a written policy, the valuation time tends to drift toward whatever was convenient on the day.
There is no single price. The same asset trades on dozens of exchanges simultaneously, at different prices. Which one is the fund's price? The largest venue? The one the fund trades on? An aggregate across several? Each answer is defensible; each produces a different NAV. We cover why prices diverge in Rethinking Crypto Data.
Much of the portfolio may barely trade. Bitcoin and Ether are easy. A fund that also holds a bridged token on a thin venue, a governance token with a vesting schedule, or a position in a protocol with three liquidity pools has assets for which no reliable market price exists. The fund administrator CV5 Capital puts it precisely: "Anyone can price bitcoin; the valuation policy exists for the bridged token on a thin venue with a vesting schedule, and that is the position an allocator will ask about first."
And continuous trading hides judgement instead of removing it. Because a price is always available on a screen, it is easy to assume valuation is automatic. CV5 Capital again: "Continuous trading does not eliminate fair-value judgment; it can conceal how much judgment the manager is already using." A fund that reads a live price off one exchange at an arbitrary moment has made a valuation decision, and has simply made it without documenting it.
The four decisions behind a crypto fund NAV
A defensible crypto NAV is one where each of these decisions has been made deliberately, written down, and applied consistently.
When: the valuation point
The fund's policy must specify a valuation time and time zone, and use the same one for NAV, performance reporting, subscriptions and redemptions. The time itself matters less than its consistency. A fund that values at 16:00 UTC every day is defensible; a fund that values "at close" without defining what close means is not.
The policy should also say what happens when the normal process fails: delayed data, an exchange outage, a network incident. These are not edge cases in crypto. They happen regularly, and the answer cannot be improvised at the moment.
The instrument built for this is a price struck at a fixed, repeatable timestamp. Blocksize's 30-minute VWAP is calculated at every half-hour on the clock from the trades in the preceding thirty minutes, and published five seconds after the interval closes. It exists so that "the price at 16:00 UTC" has one unambiguous answer, reproducible later. The regulated end of the market works the same way: US spot Bitcoin ETFs strike NAV against a reference rate calculated for 4 p.m. New York time, as we describe in Crypto Reference Rates and Benchmarks.
From where: the price source
For liquid assets, the question is which venue, or whether to aggregate across several. There are two defensible approaches and one that isn't.
The first is a single principal market, chosen and documented in advance, the approach fair-value accounting standards point to: the market with the greatest volume and activity for the asset that the fund can access. Simple to defend, simple to reproduce. Its weakness is that a single venue can diverge from the market, through an outage, thin liquidity at the valuation moment, or a regional premium, and the fund's NAV moves with it.
The second is an aggregated reference price across many venues, with a published methodology, more representative of the market and more resistant to single-venue anomalies. The consideration is that accounting standards treat it differently from a single-market quote, which we cover in Crypto Asset Valuation for Audit and Reporting. Many funds use an aggregate for NAV while classifying separately for financial statements.
The third, reading a live ticker from whatever exchange happened to be open in a browser, is not a methodology, and it will not survive the first serious question.
Whichever approach is chosen, the policy should set out a source hierarchy: the primary source, the fallback if it is unavailable, and the fallback to that. Fund administrators apply this hierarchy independently when striking NAV, which is why it has to be written down.
How: thinly traded assets
For assets that trade rarely or only on thin venues, a market price may exist but not be reliable. The last trade might be days old. A single small order might have set it. The quoted spread might be wide enough that the mid is meaningless.
The valuation policy needs a rule for when a market price stops being trusted, a maximum age, a minimum volume, a maximum spread, and what replaces it. Common approaches include using bid/ask data instead of the last trade, applying a time-weighted price across a longer window, falling back to a related liquid asset with an adjustment, or moving the asset to model-based valuation reviewed by a committee. Which price type fits which situation is covered in Crypto Prices Explained.
Two constraints from accounting standards shape this. Under ASC 820 and IFRS 13, blockage discounts, reducing a valuation because the fund holds more than the market could absorb, are not permitted. But a discount for lack of marketability can apply where the token itself carries a restriction, such as a lock-up or vesting schedule, that would transfer to a buyer.
Illiquid positions are also often revalued less frequently than liquid ones, monthly or quarterly instead of daily, with the policy stating the cadence and the triggers for an out-of-cycle review.
Who: governance
A methodology becomes a policy when someone owns it. Institutional crypto funds commonly operate a valuation committee that approves changes to price sources, rules on exceptions, reviews stale or overridden prices, and meets both on a fixed schedule and on trigger events: a delisting, a stablecoin depeg, a bridge exploit.
Regulators expect the same of fund valuation in general. In the US, SEC Rule 2a-5 requires a registered fund's board either to determine fair value itself or to designate a valuation designee and oversee it, with periodic testing of valuation methods and documented reporting. In the EU, Article 19 of the AIFMD requires alternative investment funds to have written valuation policies and procedures, applied consistently, and a valuation function that is either independent of portfolio management or subject to safeguards against conflicts of interest. Neither rule was written for crypto; both describe exactly the structure a crypto fund needs.
The committee's composition matters: it should include senior people who are not paid solely on fund performance, its decisions should be minuted, and it should keep an exceptions log that auditors and allocators can inspect. The fund's directors oversee the whole arrangement.
The administrator is the policy's operating arm, applying the hierarchy independently when it strikes NAV. That independence is the point, with one caveat the law firm Veritas Global Law states plainly: "Outsourcing the calculation does not outsource the judgment." The manager remains responsible for the policy the administrator applies.
Where crypto NAV calculations go wrong
The failure modes are predictable, and they cluster in the places where a decision was never made explicitly.
The timestamp drifts. Valuation runs "at close of business" for whoever is on shift, which is 16:00 on weekdays and whenever someone remembers on weekends. Two NAVs a week apart are not comparable.
The source changes silently. The primary exchange had an outage, someone pulled the price from a different one, and the substitution was never recorded. The NAV is right; the audit trail is not.
A thin asset is priced off a stale trade: a token last traded four days ago at a price that no longer bears any relationship to what it could be sold for. The NAV overstates the fund.
A single venue diverges. On 22 February 2021, Ether on Kraken fell to roughly $700 while trading above $1,400 on other exchanges. A fund striking NAV off that venue at that moment would have marked its Ether at less than half its market value. A fund with a multi-venue reference would not have noticed.
And the most common failure of all: nobody can explain the number. When an auditor or an allocator asks why a particular price was used, there is no documented answer.
What a defensible crypto NAV needs
Pulling the above together, a crypto NAV that holds up needs five things: a fixed valuation time, applied consistently, with written rules for holidays, weekends and failures; a documented price source hierarchy, with primary and fallback sources named in advance; a rule for thin assets, stating when a market price stops being trusted and what replaces it; a governance structure that owns the policy, records exceptions, and meets on triggers; and an audit trail that lets any published NAV be reconstructed later, down to which price, from which source, at which timestamp.
None of these makes the number more accurate on a good day. They make it explainable on a bad one.
Blocksize price data for NAV calculation
Blocksize supplies the price inputs a NAV process depends on, aggregated across more than 70 centralised and decentralised exchanges.
The 30-minute VWAP is the product built for NAV: a closing price struck at a fixed, repeatable time from executed trades across the market, published on the clock with a documented methodology. The 24-hour VWAP provides a stable daily mark for funds that value once a day. Consolidated bid/ask gives a market-wide quote for assets where trades are too sparse to price from, and AMM state prices cover DEX-native tokens directly from pool reserves.
Every product's methodology is published, and every published price carries a timestamp, so a NAV struck against a Blocksize price can be reproduced and evidenced after the fact. The same feeds are validated on-chain across decentralised oracle networks before they are accepted, an independent check that the reference reflects the market.
Blocksize is a data input to the NAV process. The valuation policy, the source hierarchy, the treatment of illiquid assets and the accounting classification remain the responsibility of the fund, its administrator and its auditors.
Frequently asked questions
How is NAV calculated for a crypto fund? Total assets minus liabilities, divided by units outstanding. The difficulty is valuing the assets: crypto has no official closing price, so the fund must decide on a valuation time, a price source and a method for thinly traded holdings, and apply them consistently.
When should a crypto fund strike its NAV? At a fixed time and time zone chosen by the fund and applied every day, including weekends and holidays. The specific time matters less than consistency. US spot Bitcoin ETFs, for example, use a reference rate struck at 4 p.m. New York time.
Should a crypto fund use one exchange or an aggregated price? Both are defensible if documented. A single principal market is simpler and aligns with fair-value accounting; an aggregated price is more representative and resistant to single-venue anomalies. Many funds use an aggregate for NAV and classify separately for financial statements.
How are illiquid tokens valued in a crypto fund? The valuation policy should set rules for when a market price is no longer trusted, by age, volume or spread, and what replaces it: bid/ask data, a longer-window average, a related-asset proxy, or a model reviewed by a valuation committee. Illiquid assets are often revalued less frequently than liquid ones.
What is a valuation committee? A governance body that owns the fund's valuation policy: approving source changes, ruling on exceptions, reviewing overridden prices, and meeting on a schedule and on trigger events. It should include senior people not paid solely on performance, and keep minutes and an exceptions log. SEC Rule 2a-5 in the US and AIFMD Article 19 in the EU describe the same structure for funds generally.
What is a 30-minute VWAP and why is it used for NAV? A volume-weighted average price calculated from trades in the thirty minutes before each half-hour mark, published on the clock. It provides a fixed, reproducible closing price in a market that never closes, which is what NAV calculation needs.