How Institutional Allocators Evaluate DeFi Fund Infrastructure

The due diligence process for a DeFi fund is expanding beyond strategy and returns. Allocators now scrutinize the operations stack as closely as the investment process. Here is what they ask — and what the right answers look like.

Why Infrastructure Due Diligence Matters Now

Two years ago, an allocator’s due diligence on a DeFi fund focused on the investment thesis: what protocols the manager targets, how they identify yield opportunities, what their edge is against on-chain competitors. The operations were an afterthought.

That has changed. Several high-profile DeFi fund failures — not from bad strategy, but from operational failures — have prompted institutional allocators to treat infrastructure with the same rigor they apply to investment process. The questions are now specific, and the answers need to be documented.

This shift mirrors what happened in traditional hedge fund due diligence after 2008, when operational risk rose to the top of every ODD checklist. For DeFi funds, the catalyst was a series of events that demonstrated how exposure could be miscalculated, how NAV could be reported incorrectly for extended periods, and how the absence of proper accounting records made investor recovery difficult when things went wrong.

The First Question: Can You Show Me Your NAV History?

The most revealing early question an allocator can ask is: show me your fund’s NAV from inception, with supporting documentation.

A fund that can respond with a complete daily NAV series, each entry linked to the block height at which it was computed, with price sources documented per asset, is demonstrating operational maturity that most DeFi funds lack.

A fund that responds with a spreadsheet built from end-of-month balance screenshots, or a NAV series that starts from when the manager signed up for a portfolio tracker, is signaling an infrastructure gap that has compounded since inception.

The supporting documentation matters as much as the number. An allocator who receives a NAV figure but cannot verify its derivation has been given an assertion, not a financial record. The ability to trace any day’s NAV back to on-chain primary sources is the minimum for an auditable fund.

The Second Question: Who Produces Your NAV, and Are They Independent?

In traditional fund management, NAV is produced by an independent fund administrator — not by the investment manager. The separation exists to prevent the manager from reporting a NAV that serves their interest (maximizing AUM for fee purposes) rather than reflecting economic reality.

In DeFi, this separation is still developing. Many funds produce their own NAV using in-house tools or generic portfolio trackers. The question an allocator should ask is: what prevents the manager from adjusting the NAV figures?

For a fund using a deterministic, block-level NAV computation engine with a full audit trail of adjustments, the answer is strong: any adjustment is logged with who made it, when, and why. The base computation is always preserved and reproducible from public on-chain data. The manager can apply an override, but cannot hide that they did so.

For a fund using a spreadsheet or a tracker with no audit trail, the answer is weak: the manager controls the inputs and there is no independent verification path.

Allocators who understand this ask specifically about the NAV adjustment mechanism: can the manager change a historical NAV figure without leaving a trace? If yes, that is a significant governance gap.

The Third Question: How Are New Protocols Covered?

DeFi fund strategies evolve rapidly. A manager who was primarily a lending yield farmer in 2023 may have expanded to Pendle yield-stripping, Hyperliquid delta-neutral strategies, and EigenLayer restaking by 2025. Each of these requires new infrastructure coverage.

The question is not whether the fund currently uses exotic protocols — it is how quickly new protocols can be brought into the NAV computation correctly when the manager decides to use them.

A fund that answers “we enter a position and then figure out how to account for it” is describing a period of uncovered exposure between the trade and the infrastructure catch-up. During that window, the protocol’s positions are either missing from NAV (understated) or valued incorrectly (using a proxy that may not reflect the actual redemption value).

The alternative is a fund whose infrastructure provider has a documented protocol onboarding process: new protocols are covered before capital is deployed, the coverage is tested against known values, and the coverage documentation is available for auditor review.

The Fourth Question: What Is Your Reconciliation Process?

Reconciliation in a DeFi fund means verifying that what the NAV engine reports matches what is actually on-chain. At first glance this seems circular: the NAV engine computes from on-chain data, so it should always match. In practice, reconciliation catches several categories of error.

Protocol integration bugs: a new or recently updated protocol integration may have an error in the exchange rate computation that causes the reported position value to diverge from the actual on-chain state. Daily reconciliation between the computed position values and the on-chain state catches this.

Chain indexing gaps: RPC nodes sometimes miss events or return stale state during periods of high load. A NAV engine that relies entirely on a single RPC provider without cross-checking is vulnerable to silent data gaps.

Wallet registry drift: funds add and remove wallets over their life. A wallet removed from the registry but still holding assets will cause a gap between reported NAV and on-chain reality. Regular reconciliation between the fund’s wallet registry and on-chain balances catches this.

An allocator who asks about reconciliation and receives a vague answer (“our system tracks everything automatically”) should probe further: what specific checks run daily, what tolerances trigger alerts, and what is the escalation process when a discrepancy is found?

The Fifth Question: How Are LP Flows Handled?

Every subscription and redemption creates a sub-period boundary that must be captured precisely for accurate Time-Weighted Return computation. An LP who subscribes on a day when the fund is up 2% intra-day and the engine does not capture the NAV at the moment of subscription will see an incorrect performance attribution in their statement.

The question is: at what precision does the fund capture NAV at subscription and redemption? Block-level precision means the fund queries the portfolio’s NAV at the block immediately before the LP’s capital arrived on-chain, and again at the block immediately after. This requires the engine to monitor on-chain events in near-real-time.

Daily-close precision means the fund uses the end-of-day NAV as the entry or exit price, regardless of whether the subscription occurred at market open or close. This is far simpler but produces a systematically incorrect TWR whenever intra-day returns are non-zero — which, in volatile markets, is most of the time.

Institutional allocators who care about accurate performance attribution (and all of them do) should ask about LP flow handling explicitly. The correct answer is block-level or at minimum intra-day precision, with documented timestamps for every subscription and redemption.

The Red Lines: What Disqualifies a Fund

Based on the questions above, there are a small number of operational facts that should be disqualifying for any institutional allocator conducting genuine ODD.

No daily NAV history from inception: a fund that cannot produce a complete daily NAV series going back to launch cannot be evaluated on its stated track record. Any period that is missing, estimated, or reconstructed from incomplete data is a gap that cannot be closed retrospectively.

No audit trail for NAV adjustments: a fund where the manager can change historical NAV figures without a documented record is a governance failure regardless of the manager’s integrity. Systems and process design, not trust in individuals, are what institutional capital requires.

No independent verification path: if the NAV cannot be independently recomputed from public on-chain data by a party without access to the fund’s systems, the auditor is in the same position as an auditor presented with management accounts but no source documents.

Self-reported coverage with no protocol onboarding discipline: a fund that deploys capital into a protocol and then retrofits the accounting creates a period of hidden exposure. The NAV figures during that period are unauditable.

These are not standards designed to exclude small or early-stage funds. They are standards that define what institutional grade means — and they are achievable with the right infrastructure from day one.