Digital Asset Fund Operations: The Institutional Operating Layer

In digital asset fund management, operations are the product. Allocators can source return streams anywhere; what they underwrite is the control environment around them — who holds the keys, who can move assets, how the NAV is struck, and what happens when an exchange, a counterparty or a smart contract fails. This pillar collects CV5 Capital's guidance on the operating layer of a digital asset fund: custody and wallet authority, exchange and counterparty risk, NAV production, stablecoin and staking mechanics, and the operational failure modes an institutional fund must be designed against.

"A digital asset strategy is only as investable as its operations. The manager who can evidence who controls each wallet, how the NAV reconciles to the chain, and how withdrawals are governed has already answered the questions that stop most funds at the diligence stage."Jeffrey Shaul, Director at CV5 Capital

Custody and wallet authority

Custody is the first operational question and the one an allocator trusts least when it is loosely answered. Managers should start with the threshold question of whether a digital asset fund actually needs a custodian, then work through what institutional allocators expect from a custodian, the practical trade-off between cold storage, MPC and prime brokers, and the full custody due diligence framework fund managers should run. Custody is inseparable from authority: our analysis of wallet authority architecture and why authority architecture is the most important design decision in a crypto fund explains why the question is not where the keys sit but who can use them — the same principle that governs exchange account control.

Exchange and counterparty risk

Trading venues remain the largest hidden risk in most digital asset funds. The problems compound across venues, as set out in the hidden control problem of multi-exchange trading and in why exchange risk is still the biggest hidden risk in crypto funds. Getting onto venues is itself a governed process, covered in our guides to exchange onboarding for regulated funds and the KYB risk that onboarding surfaces. Beyond the venue sits the broader question of counterparty risk in digital asset funds and the credit and counterparty exposures that defined the last cycle's failures.

NAV production and administration

An institutional fund's operations are validated at the NAV. The path from wallet to NAV is where on-chain reality is reconciled to the books, and the operational reality of running daily NAV in digital assets is more demanding than most managers expect. Whether daily NAV is achievable, and who supports it, depends heavily on the administrator, which is why administrator due diligence is an operational decision, not a procurement one.

Stablecoins, staking and DeFi

Digital asset operations extend into flows that traditional funds never handled. Subscriptions and redemptions increasingly move in stablecoins, raising the questions covered in whether a fund can accept BTC, USDC and USDT subscriptions, how stablecoin subscriptions and redemptions work for institutional funds, and stablecoins as portfolio liquidity infrastructure. Yield introduces further operational and accounting complexity, from staking inside institutional funds to DeFi fund accounting for staking, yield farming and liquidity pools, the institutional DeFi yield framework within a Cayman SPC, and the governance that institutional DeFi access requires. Underneath all of it sits smart contract risk, which a fund must be able to identify and price.

Operational failure modes

Most digital asset fund failures are operational, not directional. It is worth studying the operational breakdowns that kill funds, the hidden cost of poor trade operations, and concrete incidents such as the TrustedVolumes exploit and the Drift protocol hack, both of which point to the infrastructure that would have contained them. The common answer is a properly assembled institutional digital asset fund stack.

How the CV5 platform model helps

Risks and caveats

No operating model removes risk from digital assets: custodians can fail, venues can restrict or collapse, stablecoins can de-peg, and smart contracts can be exploited. The right custody, wallet-authority and NAV arrangements are fact-specific and depend on the fund's strategy, venues and instruments, and should be confirmed with counsel, the administrator and the fund's directors. Regulatory treatment, including the Cayman VASP perimeter, continues to evolve. This pillar frames the operational questions; the answers are structure-specific.

Frequently asked questions

Does a digital asset fund need a third-party custodian?

It depends on the strategy, the assets and the investor base, and the honest answer is often a blend of institutional custody and governed self-custody rather than one or the other. The threshold analysis is set out in whether a digital asset fund needs a custodian, and the model comparison in cold storage vs MPC vs prime brokers.

Can a digital asset fund produce a daily NAV?

Often yes, but it depends on the administrator, the venues and the instruments. The operational reality, and who supports it, is covered in our guide to daily NAV for crypto funds.

Where does this pillar connect?

Operations sit alongside governance and structure. From here, managers commonly move to fund governance and ODD readiness, launching a digital asset fund, and tokenised funds.