Digital Asset Funds
Fund Operations
NAV & Valuation
Cayman Regulation
Daily NAV for Crypto Funds: Is It Possible and Who Supports It?
Daily net asset value calculation is technically achievable for a Cayman-domiciled digital asset fund, but it is not a feature that can be switched on by drafting choice alone. It depends on a tightly coordinated stack of administrator capability, custodian data delivery, pricing source reliability, and portfolio liquidity. Understanding where that stack holds and where it fractures is essential before a manager commits to a daily NAV cycle.
"Daily NAV is achievable for the right strategy, but the constraint is almost never the regulatory framework. It is whether the fund's service provider stack can produce a complete, auditable NAV every business day without manual workarounds that introduce error and delay."
David Lloyd, Chief Executive Officer of CV5 Capital
Why NAV Frequency Is a Strategic Decision, Not a Default
The net asset value of a fund is the per-share or per-unit value of its portfolio at a defined point in time. For traditional hedge funds, weekly or monthly NAV cycles are standard because portfolio positions, including OTC derivatives and illiquid securities, require time-intensive pricing and reconciliation. For digital asset funds, crypto markets trade continuously across seven days of the week, and many managers assume that this constant price availability translates automatically into a capacity for daily NAV. It does not.
NAV frequency is a function of operational infrastructure, not market hours. A fund that strikes a NAV on every business day must be able to produce a complete, reconciled, auditable valuation of every position in the portfolio on that day, within a defined publication window, and distribute it to investors, counterparties, and the fund's own governance function in a timely manner. The ability to look up a Bitcoin price at any hour is a necessary condition. It is not a sufficient one.
The choice of NAV frequency is also a commercial and investor-relations decision. Institutional allocators conducting operational due diligence on a digital asset fund will assess whether the fund's stated NAV frequency is consistent with its portfolio composition, liquidity terms, and administrator capability. A fund that claims daily NAV while holding illiquid positions or relying on manual reconciliation processes presents a due diligence concern, not a competitive advantage.
The Operational Stack That Daily NAV Requires
Producing a daily NAV for a crypto fund is not a single process. It is the output of four interdependent workstreams that must all complete successfully within the same business day. A failure in any one of them delays or suspends the NAV for that date.
Custodian Data Delivery
The fund administrator cannot calculate NAV without a confirmed position report from the fund's custodian. For a digital asset fund, this means a complete snapshot of every asset held in custody, across every wallet address or exchange sub-account attributable to the fund, as of the close of the valuation day. The custodian must deliver this data to the administrator through an automated feed, an API connection, or a structured report, within a defined cut-off time that allows the administrator to complete its calculation before the NAV publication deadline.
Funds that rely on manually transmitted position reports from a custodian cannot consistently support daily NAV without accepting meaningful operational risk. A delayed report, a formatting error, or a reconciliation discrepancy pushes the entire NAV process past the daily window. The administrator then faces a choice between publishing a NAV that has not been fully reconciled or delaying publication and notifying investors. Neither outcome is acceptable as a recurring pattern.
Exchange and On-Chain Position Reconciliation
Many digital asset fund strategies hold positions across multiple venues simultaneously, including centralised exchanges, on-chain protocols, and OTC counterparties. For daily NAV purposes, the administrator must reconcile positions from all venues against the custody record before striking the NAV. Exchange positions are typically accessed via API and are relatively straightforward for major venues with institutional API infrastructure. On-chain positions, including staking balances, liquidity pool allocations, or protocol-level deployments, require wallet balance queries at the valuation timestamp, which can be technically complex depending on the protocols involved.
OTC positions present the most difficulty. Mark-to-market pricing for bespoke OTC contracts on a daily basis requires either a dealer quote or a defined model-based valuation. Most fund valuation policies specify that OTC positions are priced using the mid-market quote from the relevant counterparty, confirmed at the close of business. Obtaining and recording these quotes consistently, every business day, is an operational discipline that fund administrators with limited digital asset experience frequently underestimate.
Pricing Source Reliability and Hierarchy
Each asset in the portfolio must be assigned a reference price at the valuation point. The fund's valuation policy must document the primary pricing source for every asset class held, along with a defined fallback hierarchy if the primary source is unavailable or produces a price that falls outside a defined reasonableness range.
For liquid assets such as Bitcoin and Ether, composite reference rates derived from multiple regulated venues and calculated at a fixed time each business day are the institutional standard. For mid-cap tokens with thinner liquidity, the pricing source question becomes more complex, and the administrator must apply judgment within the bounds of the valuation policy. For derivative positions such as perpetual futures or options, daily mark-to-market requires end-of-day settlement prices from the relevant exchange, which must be captured and archived for audit purposes.
A well-structured valuation policy is not a theoretical document. It is a daily operational instruction set. Administrators processing a daily NAV rely on it to resolve pricing questions without escalating to the investment manager, which would compromise NAV independence. The CV5 Capital glossary provides a reference framework for the key valuation terms that should be defined in any digital asset fund's offering memorandum.
Pricing Infrastructure: Reference Rates and Fallback Policy
The quality of a daily NAV is only as good as the pricing data that underlies it. For a fund to credibly assert that its daily NAV is independently calculated and auditable, each price input must be sourced from a published, third-party data source that is not controlled by the investment manager.
Liquid Digital Assets
For Bitcoin, Ether, and major liquid tokens, the standard institutional approach is to use a volume-weighted composite price calculated over a defined window, typically the one-hour period ending at a fixed time on each business day, sourced from a regulated data provider that aggregates prices across multiple exchanges. This methodology reduces the influence of any single venue on the NAV and provides a consistent, replicable price for audit and investor reporting purposes. The specific provider and timestamp must be named in the offering memorandum.
Stablecoins and Cash Equivalents
USDC and USDT held within the fund portfolio are typically valued at par for NAV purposes. However, as discussed in the context of subscription mechanics, the valuation policy must address what happens when either asset trades away from its one-dollar peg at the valuation timestamp. The policy must specify whether the fund uses market price or par in such circumstances, and must assign authority to make that determination either to the administrator acting under policy or to the independent directors acting on a fair value basis.
Illiquid Tokens and Protocol Positions
This is the category where daily NAV becomes structurally difficult. Tokens with limited secondary market liquidity, positions locked in governance protocols, or allocations subject to vesting schedules cannot be priced reliably on a daily basis using market data alone. A fund holding material illiquid positions alongside liquid assets faces a valuation policy tension: if illiquid positions are priced daily using stale or model-based inputs, the resulting NAV may not accurately reflect the portfolio's fair value. If they are carved out into a side pocket and excluded from the main NAV, the liquidity terms and redemption mechanics of the fund must reflect that structure explicitly.
Most institutional administrators will advise managers that strategies with significant illiquid exposure are not compatible with a daily NAV cycle without side pocket provisions and corresponding disclosure in the offering memorandum. Managers who attempt to price illiquid positions on a daily basis without a robust fair value framework risk creating NAV disputes that are difficult and costly to resolve.
Administrator Capability: Who Actually Supports Daily NAV
The administrator is the operational constraint that most managers underestimate when targeting a daily NAV cycle. Fund administration for digital asset funds is a specialised capability, and not all administrators who accept digital asset mandates have the systems, data pipelines, or staffing models to support daily NAV at an institutional standard.
A manager evaluating whether an administrator can support daily NAV should ask the following questions during the selection process:
- Do you have automated data ingestion from institutional custodians and major exchange APIs, or do you rely on manually submitted position reports?
- What is your cut-off time for receiving position data, and what is your committed NAV publication time on each business day?
- How do you handle reconciliation breaks between your records and the custodian's report? What is the escalation and resolution process, and what is the typical resolution time?
- Which pricing data providers do you use for liquid digital assets, and how do you source prices for mid-cap tokens not covered by your primary provider?
- How do you price derivative positions, including perpetual futures and options, on a daily basis?
- What is your process for pricing OTC positions on days when a dealer quote is unavailable?
- Can you provide examples of funds you currently administer on a daily NAV cycle, and what is the asset composition of those funds?
Administrators with genuine daily NAV capability for digital asset funds typically have automated reconciliation workflows that ingest custodian and exchange data through structured API connections, apply pricing rules from a validated source hierarchy, flag exceptions for human review, and produce a draft NAV within a defined period after the valuation timestamp. Manual intervention should be the exception, not the standard process. Managers launching through the CV5 Digital Asset Fund Platform are connected to administrators whose digital asset workflows are evaluated as part of the platform's service provider due diligence process.
Liquidity Terms Must Be Consistent with NAV Frequency
A fund's NAV frequency and its liquidity terms are not independent variables. They must be aligned in the offering documents and in practice. A fund that strikes a daily NAV but only permits redemptions on the last business day of each month is offering price transparency rather than daily liquidity. This is a legitimate structure, but it must be presented accurately to investors and documented precisely in the offering memorandum.
Full daily dealing, meaning both subscriptions and redemptions on any business day, requires that the fund maintain sufficient liquidity at all times to meet redemption requests without distorting portfolio positioning or creating unfair treatment between redeeming and remaining investors. For strategies that are fully invested in liquid digital assets traded on major venues, this is achievable. For strategies with any illiquid exposure, OTC positions with settlement delays, or assets subject to exchange withdrawal limits, daily dealing creates a structural liquidity mismatch that must be managed through redemption gates, notice periods, side pocket provisions, or suspension rights.
CIMA-registered funds under the Private Funds Act (as amended) are required to maintain, and where necessary enforce, redemption provisions that are consistent with the fund's underlying liquidity. A fund that offers daily liquidity while holding structurally illiquid positions without appropriate safeguards faces both regulatory scrutiny and potential investor claims in a stressed redemption environment. These provisions, along with the fund's obligations under the FATCA/CRS compliance framework, must be addressed comprehensively in the offering memorandum and the fund's governance documentation.
Matching NAV Frequency to Strategy Type
The practical conclusion from the above analysis is that daily NAV is most appropriate for digital asset funds with a specific profile. The further a strategy departs from that profile, the stronger the operational and investor-relations case for a longer NAV cycle becomes.
Strategies well suited to daily NAV include those that hold exclusively liquid digital assets traded on major centralised exchanges, maintain no OTC positions or illiquid token exposure, use a single institutional custodian with automated daily data delivery, and target an investor base that values price transparency and daily subscription access.
Strategies better suited to weekly NAV include those that combine liquid exchange positions with on-chain deployments requiring daily wallet reconciliation, hold a small proportion of mid-cap tokens with limited pricing source coverage, or have an administrator whose digital asset workflows are partially automated but require daily human review of pricing exceptions.
Strategies where monthly NAV is the appropriate starting point include those with any material illiquid token exposure, OTC derivatives with bespoke settlement terms, or multi-venue architectures where reconciliation between exchange, custodian, and on-chain records cannot be completed reliably within a single business day. Managers considering fund manager formation through a structured Cayman platform should address NAV frequency as part of the initial structuring discussion, not as a secondary operational detail.
Key Takeaways
- Daily NAV for a crypto fund is technically achievable for liquid strategies, but it depends on automated custodian data delivery, validated pricing source infrastructure, and an administrator with proven digital asset daily NAV workflows.
- The binding constraint on daily NAV is almost always the service provider stack, specifically the custodian's data delivery SLA and the administrator's reconciliation automation, rather than the regulatory framework or the offering document drafting.
- Every asset class in the portfolio must have a defined primary pricing source and a documented fallback hierarchy within the valuation policy. Gaps in the pricing hierarchy make daily NAV operationally unsustainable.
- Illiquid positions, OTC derivatives, and on-chain protocol deployments require specific valuation treatment in the offering memorandum. Strategies with material illiquid exposure should use side pocket provisions or a longer NAV cycle rather than forcing illiquid assets into a daily valuation framework.
- Liquidity terms must be structurally consistent with NAV frequency. Daily dealing requires portfolio liquidity management disciplines, including gates, notice periods, and suspension provisions, that must be documented in the fund's constitutive documents.
- Managers should conduct detailed operational due diligence on any administrator's daily NAV capability before launch, including questions on data ingestion, reconciliation resolution timelines, and pricing source coverage for the specific assets in their strategy.
Build Your Fund on Infrastructure That Supports Daily Operations
CV5 Capital's CIMA-regulated platform connects digital asset fund managers with administrators and custodians whose workflows are evaluated for institutional-grade NAV capability. We help managers align NAV frequency, liquidity terms, and valuation policy from the outset, so operational infrastructure does not become a constraint after launch.
Speak with our team to explore how the CV5 Digital Asset Fund Platform is structured to support your strategy's specific operational requirements.
Speak with Our Team
This article is produced by CV5 Capital Limited for informational purposes only and does not constitute legal, regulatory, investment, tax, or financial advice. The content reflects general market commentary and the views of CV5 Capital and should not be relied upon as a basis for any investment, structuring, or service provider selection decision. References to valuation practices, administrator capabilities, and operational frameworks are illustrative of institutional practice and do not constitute a representation that any specific outcome will be achieved. Managers and investors should seek independent professional advice appropriate to their specific circumstances, strategy, and jurisdiction. CV5 Capital Limited is registered with the Cayman Islands Monetary Authority (CIMA Registration No. 1885380, LEI: 984500C44B2KFE900490).
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)