Renesis Insights

Renesis Team

Shadow NAV for Crypto Funds: How Managers Check the Administrator’s Number

Shadow NAV for crypto funds: why managers recompute the administrator’s NAV, where the two numbers break apart, and how to reconcile them daily.

A shadow NAV is the net asset value a fund manager calculates independently, from its own books and data, to check the official NAV produced by the fund administrator. The administrator’s number is the one investors deal at. The shadow NAV is how the manager knows that number is right before it goes out.

Traditional hedge funds have run shadow books for decades: in-house, through a second administrator, or through an outsourced provider, as AIMA describes. In crypto the practice matters more, because the inputs to NAV are less standardized. Markets never close, the same token trades at different prices on different venues, and part of the portfolio lives in smart contracts that an administrator’s system may not read natively.

This guide covers how the two numbers differ, why they drift apart in crypto, how a reconciliation runs, and the breaks that show up most often.

Official NAV vs shadow NAV: the fund administrator strikes the binding NAV at each dealing date; the manager’s shadow NAV runs daily from independent data under the same valuation policy

Official NAV vs shadow NAV

The two numbers answer different questions. The official NAV answers what a share is worth for dealing purposes, and it is binding: subscriptions, redemptions, management fees and performance fees are all calculated from it. The administrator strikes it at each dealing date, which for most liquid crypto funds means monthly, sometimes weekly.

The shadow NAV answers whether the manager agrees with that number, and if not, why. It is produced by the manager, or by a second provider on the manager’s behalf, using the fund’s valuation policy and independent position and price data. It is not sent to investors as a dealing price. Its job is to catch errors before the official NAV is final.

Two points are easy to miss:

  • Responsibility stays with the manager. The administrator calculates NAV under the fund’s valuation policy, but the manager owns that policy and answers to investors if the number is wrong. Gresham makes the same point: the fund stays accountable to its investors even when the administrator runs the calculation.

  • A shadow NAV only works if it is independent. If it is rebuilt from the administrator’s own position file, it reproduces the administrator’s errors. The inputs have to come from the exchanges, wallets and protocols directly.

The administrator’s NAV is the official number. The shadow NAV is how you know it is right.

Why crypto makes the gap bigger

In a long/short equity fund, the administrator and the manager usually see the same closing prices from the same exchange at the same time. Crypto removes each of those anchors.

  • Cut-off time. There is no market close, so a fund has to pick a valuation time and apply it everywhere. Many crypto funds use 00:00 UTC and read on-chain positions at the block nearest that timestamp, as Cobo notes. If the administrator snapshots at 4 p.m. New York time and the manager at midnight UTC, the two NAVs differ by whatever the market did in between. Regulated products show how much the choice matters: CF Benchmarks published research on which time of day is best for striking NAV on crypto ETFs.

  • Price source. The same token trades at slightly different prices on each venue. Unless the valuation policy names the source for each asset, such as a principal market, a composite or a benchmark rate, two careful people will pick different prices.

  • DeFi positions. LP tokens, lending deposits, vault shares, Pendle PT and YT, and looped positions have no exchange price. They are valued through their underlying assets and protocol state. An administrator that prices an LP token from an aggregator quote and a manager that values it through pool reserves will disagree. See how to calculate NAV for a DeFi-native fund and how funds value Pendle positions.

  • Perp funding and accruals. Perpetual futures pay or charge funding every one to eight hours. If funding is booked only when a statement arrives, the NAV misses accrued amounts. The same applies to lending interest that accrues every block.

  • Staking rewards and airdrops. Rewards that have accrued but not been claimed, and tokens that have been airdropped but are not yet liquid, need a recognition rule. Without one, each side applies its own.

How a shadow NAV reconciliation runs

Shadow NAV reconciliation in four steps: snapshot at the policy time, price by the valuation policy, compare with the administrator total first then by position, explain and log every break

The process has four steps, and the order matters.

  1. Snapshot at the policy time. Pull balances, positions and open orders from every exchange account, wallet and protocol at the valuation timestamp. For on-chain positions, read state at the block nearest that time.

  2. Price by the policy. Apply the same price sources, fallbacks and methods the administrator is supposed to use. This is a test of the administrator’s work, not a second opinion on valuation.

  3. Compare, top down. Start with total NAV. If the difference is above the tolerance in the valuation policy, compare by account, then by position, until every dollar of difference sits on a line item.

  4. Explain every break. Record each difference in a break log with its cause, who fixes it and by when. Some breaks are administrator errors. Others are gaps in the valuation policy, and the fix is to amend the policy so the question does not come up again.

Daily matters in crypto. A monthly-only reconciliation finds a month of breaks at once, under a deadline. Running the shadow NAV daily means most breaks are found the day they appear, and the monthly sign-off becomes a formality.

Common breaks and how to resolve them

Break

Usual cause

How to resolve it

Price source

Different venue or reference rate for the same asset

Name the source for each asset in the valuation policy

Cut-off time

Snapshots taken at different times

One fund-wide valuation time; nearest block for on-chain positions

Perp funding

Accrued funding not yet booked

Book funding per settlement from exchange data

DeFi and LP positions

LP token priced at a market quote instead of through its underlying

Value through underlying assets and protocol state

Staking rewards

Accrued, unclaimed rewards treated differently

Set a recognition point in the policy

Fees

Management or performance fee accrued on a different basis

Accrue daily with the formula in the fund documents

A worked example

Take a fund whose shadow NAV at month end is $40,212,400 while the administrator reports $40,156,400. The gap is $56,000, about 14 bps of NAV. The numbers are illustrative; this is how the gap breaks down:

  • Price source: 4,000 ETH priced at $1,812.40 by the administrator (one exchange’s close) and $1,815.10 by the manager (the composite rate the policy names). Difference: $10,800.

  • Perp funding: one day of funding received on a short BTC perp hedge, not yet booked by the administrator: $3,950.

  • LP position: a stablecoin/ETH LP token valued by the administrator at an aggregator quote and by the manager through pool reserves: $18,250.

  • Staking rewards: 12.5 ETH of accrued, unclaimed rewards that the policy recognizes and the administrator did not book: $22,688.75.

Those four items explain $55,688.75. The residual is $311.25, under a tolerance of 0.5 bps of NAV (about $2,000), so it can be signed off without further work.

The resolution differs by item. The funding and staking items are administrator errors against the policy, and the official NAV should be corrected before it is final. The price source item means the administrator did not use the source the policy names. The LP item may be a policy gap: if the policy does not say how LP tokens are valued, write it in. If the fund is above its high-water mark, a 20% performance fee on the $56,000 is $11,200 calculated on the wrong base.

Tools: spreadsheets, the administrator’s portal or a PMS

Most emerging managers start with a spreadsheet: exports from each exchange, wallet balances from explorers, prices pasted in at month end. It works for a handful of accounts and breaks down with DeFi positions, many wallets or a daily cadence, because every step is manual and nothing is reproducible.

The administrator’s investor portal is not a shadow NAV. It shows the administrator’s own numbers, so it cannot test them.

A portfolio management system that connects directly to exchanges, wallets and protocols produces an independent, position-level NAV every day, with the history needed to explain a break after the fact. That is the setup allocators’ operational due diligence teams increasingly expect; what LPs look for in a crypto fund’s reporting covers the rest of that checklist. For the administrator side, see our guide to crypto fund administration and how NAV attestation works for vaults and DeFi funds.

Where Renesis fits

A shadow NAV only works if it’s built from the same positions and prices as the administrator’s, every day, without someone rebuilding a spreadsheet. That’s the job Renesis does: one book of a fund’s positions on-chain and on exchanges, valued under the fund’s own policy, with NAV and investor reporting produced from it. See how the portfolio management system works, or how Enzyme vault managers use Renesis for reporting.

Frequently asked questions

What is a shadow NAV?

An independent calculation of a fund’s net asset value, produced by the manager or a second provider, to check the official NAV calculated by the fund administrator. It uses the same valuation policy but independent position and price data.

Is a shadow NAV required for a crypto fund?

Usually not as a legal requirement. It is how a manager meets its own responsibility for valuation, and allocators’ due diligence teams often ask how the manager checks the administrator. Very large managers sometimes appoint a second administrator just to keep the shadow books, as Carta notes.

How often should a crypto fund run a shadow NAV?

Daily, with a formal reconciliation at each official NAV date. Crypto markets trade around the clock and DeFi positions accrue continuously, so a monthly-only check leaves too long between a break and its discovery.

What tolerance should a shadow NAV reconciliation use?

Set it in the valuation policy: a basis-point threshold for total NAV and a dollar threshold per position. Anything above either is a break that needs a written explanation, even when the total nets out.

Still not sure if Renesis is right for you?

Ask ChatGPT, Claude or Perplexity what they have to talk about us. Click below to ask your favorite AI about us:

Built by builders.
For builders.

We're a DeFi-native team shipping fast. No enterprise sales cycles, no bloated pricing. Start free, talk to us when you're ready.

Renesis Insights

Renesis Team

Shadow NAV for Crypto Funds: How Managers Check the Administrator’s Number

Shadow NAV for crypto funds: why managers recompute the administrator’s NAV, where the two numbers break apart, and how to reconcile them daily.

A shadow NAV is the net asset value a fund manager calculates independently, from its own books and data, to check the official NAV produced by the fund administrator. The administrator’s number is the one investors deal at. The shadow NAV is how the manager knows that number is right before it goes out.

Traditional hedge funds have run shadow books for decades: in-house, through a second administrator, or through an outsourced provider, as AIMA describes. In crypto the practice matters more, because the inputs to NAV are less standardized. Markets never close, the same token trades at different prices on different venues, and part of the portfolio lives in smart contracts that an administrator’s system may not read natively.

This guide covers how the two numbers differ, why they drift apart in crypto, how a reconciliation runs, and the breaks that show up most often.

Official NAV vs shadow NAV: the fund administrator strikes the binding NAV at each dealing date; the manager’s shadow NAV runs daily from independent data under the same valuation policy

Official NAV vs shadow NAV

The two numbers answer different questions. The official NAV answers what a share is worth for dealing purposes, and it is binding: subscriptions, redemptions, management fees and performance fees are all calculated from it. The administrator strikes it at each dealing date, which for most liquid crypto funds means monthly, sometimes weekly.

The shadow NAV answers whether the manager agrees with that number, and if not, why. It is produced by the manager, or by a second provider on the manager’s behalf, using the fund’s valuation policy and independent position and price data. It is not sent to investors as a dealing price. Its job is to catch errors before the official NAV is final.

Two points are easy to miss:

  • Responsibility stays with the manager. The administrator calculates NAV under the fund’s valuation policy, but the manager owns that policy and answers to investors if the number is wrong. Gresham makes the same point: the fund stays accountable to its investors even when the administrator runs the calculation.

  • A shadow NAV only works if it is independent. If it is rebuilt from the administrator’s own position file, it reproduces the administrator’s errors. The inputs have to come from the exchanges, wallets and protocols directly.

The administrator’s NAV is the official number. The shadow NAV is how you know it is right.

Why crypto makes the gap bigger

In a long/short equity fund, the administrator and the manager usually see the same closing prices from the same exchange at the same time. Crypto removes each of those anchors.

  • Cut-off time. There is no market close, so a fund has to pick a valuation time and apply it everywhere. Many crypto funds use 00:00 UTC and read on-chain positions at the block nearest that timestamp, as Cobo notes. If the administrator snapshots at 4 p.m. New York time and the manager at midnight UTC, the two NAVs differ by whatever the market did in between. Regulated products show how much the choice matters: CF Benchmarks published research on which time of day is best for striking NAV on crypto ETFs.

  • Price source. The same token trades at slightly different prices on each venue. Unless the valuation policy names the source for each asset, such as a principal market, a composite or a benchmark rate, two careful people will pick different prices.

  • DeFi positions. LP tokens, lending deposits, vault shares, Pendle PT and YT, and looped positions have no exchange price. They are valued through their underlying assets and protocol state. An administrator that prices an LP token from an aggregator quote and a manager that values it through pool reserves will disagree. See how to calculate NAV for a DeFi-native fund and how funds value Pendle positions.

  • Perp funding and accruals. Perpetual futures pay or charge funding every one to eight hours. If funding is booked only when a statement arrives, the NAV misses accrued amounts. The same applies to lending interest that accrues every block.

  • Staking rewards and airdrops. Rewards that have accrued but not been claimed, and tokens that have been airdropped but are not yet liquid, need a recognition rule. Without one, each side applies its own.

How a shadow NAV reconciliation runs

Shadow NAV reconciliation in four steps: snapshot at the policy time, price by the valuation policy, compare with the administrator total first then by position, explain and log every break

The process has four steps, and the order matters.

  1. Snapshot at the policy time. Pull balances, positions and open orders from every exchange account, wallet and protocol at the valuation timestamp. For on-chain positions, read state at the block nearest that time.

  2. Price by the policy. Apply the same price sources, fallbacks and methods the administrator is supposed to use. This is a test of the administrator’s work, not a second opinion on valuation.

  3. Compare, top down. Start with total NAV. If the difference is above the tolerance in the valuation policy, compare by account, then by position, until every dollar of difference sits on a line item.

  4. Explain every break. Record each difference in a break log with its cause, who fixes it and by when. Some breaks are administrator errors. Others are gaps in the valuation policy, and the fix is to amend the policy so the question does not come up again.

Daily matters in crypto. A monthly-only reconciliation finds a month of breaks at once, under a deadline. Running the shadow NAV daily means most breaks are found the day they appear, and the monthly sign-off becomes a formality.

Common breaks and how to resolve them

Break

Usual cause

How to resolve it

Price source

Different venue or reference rate for the same asset

Name the source for each asset in the valuation policy

Cut-off time

Snapshots taken at different times

One fund-wide valuation time; nearest block for on-chain positions

Perp funding

Accrued funding not yet booked

Book funding per settlement from exchange data

DeFi and LP positions

LP token priced at a market quote instead of through its underlying

Value through underlying assets and protocol state

Staking rewards

Accrued, unclaimed rewards treated differently

Set a recognition point in the policy

Fees

Management or performance fee accrued on a different basis

Accrue daily with the formula in the fund documents

A worked example

Take a fund whose shadow NAV at month end is $40,212,400 while the administrator reports $40,156,400. The gap is $56,000, about 14 bps of NAV. The numbers are illustrative; this is how the gap breaks down:

  • Price source: 4,000 ETH priced at $1,812.40 by the administrator (one exchange’s close) and $1,815.10 by the manager (the composite rate the policy names). Difference: $10,800.

  • Perp funding: one day of funding received on a short BTC perp hedge, not yet booked by the administrator: $3,950.

  • LP position: a stablecoin/ETH LP token valued by the administrator at an aggregator quote and by the manager through pool reserves: $18,250.

  • Staking rewards: 12.5 ETH of accrued, unclaimed rewards that the policy recognizes and the administrator did not book: $22,688.75.

Those four items explain $55,688.75. The residual is $311.25, under a tolerance of 0.5 bps of NAV (about $2,000), so it can be signed off without further work.

The resolution differs by item. The funding and staking items are administrator errors against the policy, and the official NAV should be corrected before it is final. The price source item means the administrator did not use the source the policy names. The LP item may be a policy gap: if the policy does not say how LP tokens are valued, write it in. If the fund is above its high-water mark, a 20% performance fee on the $56,000 is $11,200 calculated on the wrong base.

Tools: spreadsheets, the administrator’s portal or a PMS

Most emerging managers start with a spreadsheet: exports from each exchange, wallet balances from explorers, prices pasted in at month end. It works for a handful of accounts and breaks down with DeFi positions, many wallets or a daily cadence, because every step is manual and nothing is reproducible.

The administrator’s investor portal is not a shadow NAV. It shows the administrator’s own numbers, so it cannot test them.

A portfolio management system that connects directly to exchanges, wallets and protocols produces an independent, position-level NAV every day, with the history needed to explain a break after the fact. That is the setup allocators’ operational due diligence teams increasingly expect; what LPs look for in a crypto fund’s reporting covers the rest of that checklist. For the administrator side, see our guide to crypto fund administration and how NAV attestation works for vaults and DeFi funds.

Where Renesis fits

A shadow NAV only works if it’s built from the same positions and prices as the administrator’s, every day, without someone rebuilding a spreadsheet. That’s the job Renesis does: one book of a fund’s positions on-chain and on exchanges, valued under the fund’s own policy, with NAV and investor reporting produced from it. See how the portfolio management system works, or how Enzyme vault managers use Renesis for reporting.

Frequently asked questions

What is a shadow NAV?

An independent calculation of a fund’s net asset value, produced by the manager or a second provider, to check the official NAV calculated by the fund administrator. It uses the same valuation policy but independent position and price data.

Is a shadow NAV required for a crypto fund?

Usually not as a legal requirement. It is how a manager meets its own responsibility for valuation, and allocators’ due diligence teams often ask how the manager checks the administrator. Very large managers sometimes appoint a second administrator just to keep the shadow books, as Carta notes.

How often should a crypto fund run a shadow NAV?

Daily, with a formal reconciliation at each official NAV date. Crypto markets trade around the clock and DeFi positions accrue continuously, so a monthly-only check leaves too long between a break and its discovery.

What tolerance should a shadow NAV reconciliation use?

Set it in the valuation policy: a basis-point threshold for total NAV and a dollar threshold per position. Anything above either is a break that needs a written explanation, even when the total nets out.

Renesis Insights

Renesis Team

Shadow NAV for Crypto Funds: How Managers Check the Administrator’s Number

Shadow NAV for crypto funds: why managers recompute the administrator’s NAV, where the two numbers break apart, and how to reconcile them daily.

A shadow NAV is the net asset value a fund manager calculates independently, from its own books and data, to check the official NAV produced by the fund administrator. The administrator’s number is the one investors deal at. The shadow NAV is how the manager knows that number is right before it goes out.

Traditional hedge funds have run shadow books for decades: in-house, through a second administrator, or through an outsourced provider, as AIMA describes. In crypto the practice matters more, because the inputs to NAV are less standardized. Markets never close, the same token trades at different prices on different venues, and part of the portfolio lives in smart contracts that an administrator’s system may not read natively.

This guide covers how the two numbers differ, why they drift apart in crypto, how a reconciliation runs, and the breaks that show up most often.

Official NAV vs shadow NAV: the fund administrator strikes the binding NAV at each dealing date; the manager’s shadow NAV runs daily from independent data under the same valuation policy

Official NAV vs shadow NAV

The two numbers answer different questions. The official NAV answers what a share is worth for dealing purposes, and it is binding: subscriptions, redemptions, management fees and performance fees are all calculated from it. The administrator strikes it at each dealing date, which for most liquid crypto funds means monthly, sometimes weekly.

The shadow NAV answers whether the manager agrees with that number, and if not, why. It is produced by the manager, or by a second provider on the manager’s behalf, using the fund’s valuation policy and independent position and price data. It is not sent to investors as a dealing price. Its job is to catch errors before the official NAV is final.

Two points are easy to miss:

  • Responsibility stays with the manager. The administrator calculates NAV under the fund’s valuation policy, but the manager owns that policy and answers to investors if the number is wrong. Gresham makes the same point: the fund stays accountable to its investors even when the administrator runs the calculation.

  • A shadow NAV only works if it is independent. If it is rebuilt from the administrator’s own position file, it reproduces the administrator’s errors. The inputs have to come from the exchanges, wallets and protocols directly.

The administrator’s NAV is the official number. The shadow NAV is how you know it is right.

Why crypto makes the gap bigger

In a long/short equity fund, the administrator and the manager usually see the same closing prices from the same exchange at the same time. Crypto removes each of those anchors.

  • Cut-off time. There is no market close, so a fund has to pick a valuation time and apply it everywhere. Many crypto funds use 00:00 UTC and read on-chain positions at the block nearest that timestamp, as Cobo notes. If the administrator snapshots at 4 p.m. New York time and the manager at midnight UTC, the two NAVs differ by whatever the market did in between. Regulated products show how much the choice matters: CF Benchmarks published research on which time of day is best for striking NAV on crypto ETFs.

  • Price source. The same token trades at slightly different prices on each venue. Unless the valuation policy names the source for each asset, such as a principal market, a composite or a benchmark rate, two careful people will pick different prices.

  • DeFi positions. LP tokens, lending deposits, vault shares, Pendle PT and YT, and looped positions have no exchange price. They are valued through their underlying assets and protocol state. An administrator that prices an LP token from an aggregator quote and a manager that values it through pool reserves will disagree. See how to calculate NAV for a DeFi-native fund and how funds value Pendle positions.

  • Perp funding and accruals. Perpetual futures pay or charge funding every one to eight hours. If funding is booked only when a statement arrives, the NAV misses accrued amounts. The same applies to lending interest that accrues every block.

  • Staking rewards and airdrops. Rewards that have accrued but not been claimed, and tokens that have been airdropped but are not yet liquid, need a recognition rule. Without one, each side applies its own.

How a shadow NAV reconciliation runs

Shadow NAV reconciliation in four steps: snapshot at the policy time, price by the valuation policy, compare with the administrator total first then by position, explain and log every break

The process has four steps, and the order matters.

  1. Snapshot at the policy time. Pull balances, positions and open orders from every exchange account, wallet and protocol at the valuation timestamp. For on-chain positions, read state at the block nearest that time.

  2. Price by the policy. Apply the same price sources, fallbacks and methods the administrator is supposed to use. This is a test of the administrator’s work, not a second opinion on valuation.

  3. Compare, top down. Start with total NAV. If the difference is above the tolerance in the valuation policy, compare by account, then by position, until every dollar of difference sits on a line item.

  4. Explain every break. Record each difference in a break log with its cause, who fixes it and by when. Some breaks are administrator errors. Others are gaps in the valuation policy, and the fix is to amend the policy so the question does not come up again.

Daily matters in crypto. A monthly-only reconciliation finds a month of breaks at once, under a deadline. Running the shadow NAV daily means most breaks are found the day they appear, and the monthly sign-off becomes a formality.

Common breaks and how to resolve them

Break

Usual cause

How to resolve it

Price source

Different venue or reference rate for the same asset

Name the source for each asset in the valuation policy

Cut-off time

Snapshots taken at different times

One fund-wide valuation time; nearest block for on-chain positions

Perp funding

Accrued funding not yet booked

Book funding per settlement from exchange data

DeFi and LP positions

LP token priced at a market quote instead of through its underlying

Value through underlying assets and protocol state

Staking rewards

Accrued, unclaimed rewards treated differently

Set a recognition point in the policy

Fees

Management or performance fee accrued on a different basis

Accrue daily with the formula in the fund documents

A worked example

Take a fund whose shadow NAV at month end is $40,212,400 while the administrator reports $40,156,400. The gap is $56,000, about 14 bps of NAV. The numbers are illustrative; this is how the gap breaks down:

  • Price source: 4,000 ETH priced at $1,812.40 by the administrator (one exchange’s close) and $1,815.10 by the manager (the composite rate the policy names). Difference: $10,800.

  • Perp funding: one day of funding received on a short BTC perp hedge, not yet booked by the administrator: $3,950.

  • LP position: a stablecoin/ETH LP token valued by the administrator at an aggregator quote and by the manager through pool reserves: $18,250.

  • Staking rewards: 12.5 ETH of accrued, unclaimed rewards that the policy recognizes and the administrator did not book: $22,688.75.

Those four items explain $55,688.75. The residual is $311.25, under a tolerance of 0.5 bps of NAV (about $2,000), so it can be signed off without further work.

The resolution differs by item. The funding and staking items are administrator errors against the policy, and the official NAV should be corrected before it is final. The price source item means the administrator did not use the source the policy names. The LP item may be a policy gap: if the policy does not say how LP tokens are valued, write it in. If the fund is above its high-water mark, a 20% performance fee on the $56,000 is $11,200 calculated on the wrong base.

Tools: spreadsheets, the administrator’s portal or a PMS

Most emerging managers start with a spreadsheet: exports from each exchange, wallet balances from explorers, prices pasted in at month end. It works for a handful of accounts and breaks down with DeFi positions, many wallets or a daily cadence, because every step is manual and nothing is reproducible.

The administrator’s investor portal is not a shadow NAV. It shows the administrator’s own numbers, so it cannot test them.

A portfolio management system that connects directly to exchanges, wallets and protocols produces an independent, position-level NAV every day, with the history needed to explain a break after the fact. That is the setup allocators’ operational due diligence teams increasingly expect; what LPs look for in a crypto fund’s reporting covers the rest of that checklist. For the administrator side, see our guide to crypto fund administration and how NAV attestation works for vaults and DeFi funds.

Where Renesis fits

A shadow NAV only works if it’s built from the same positions and prices as the administrator’s, every day, without someone rebuilding a spreadsheet. That’s the job Renesis does: one book of a fund’s positions on-chain and on exchanges, valued under the fund’s own policy, with NAV and investor reporting produced from it. See how the portfolio management system works, or how Enzyme vault managers use Renesis for reporting.

Frequently asked questions

What is a shadow NAV?

An independent calculation of a fund’s net asset value, produced by the manager or a second provider, to check the official NAV calculated by the fund administrator. It uses the same valuation policy but independent position and price data.

Is a shadow NAV required for a crypto fund?

Usually not as a legal requirement. It is how a manager meets its own responsibility for valuation, and allocators’ due diligence teams often ask how the manager checks the administrator. Very large managers sometimes appoint a second administrator just to keep the shadow books, as Carta notes.

How often should a crypto fund run a shadow NAV?

Daily, with a formal reconciliation at each official NAV date. Crypto markets trade around the clock and DeFi positions accrue continuously, so a monthly-only check leaves too long between a break and its discovery.

What tolerance should a shadow NAV reconciliation use?

Set it in the valuation policy: a basis-point threshold for total NAV and a dollar threshold per position. Anything above either is a break that needs a written explanation, even when the total nets out.