Crypto NAV vs Fund Administration
A fund administrator sells a bundle. A crypto NAV service sells one component of that bundle, and refreshes it far more often than the bundle ever will.
The speed is what causes trouble. An hourly number reads as more advanced than a monthly one, and a crypto NAV service starts to look like a fund administrator that got faster.
So: who does the DeFi part of your books, and how would you know if they were doing it badly?
Three things get called crypto NAV
Section titled “Three things get called crypto NAV”The snapshot. Poll the wallets, match what they hold against a list of known tokens, price it, add it up. Quick, cheap, and it runs as often as you like. Most of the market means this when it says crypto NAV, and on a simple book it answers the question honestly.
The administrator’s book. Full double-entry bookkeeping by people who do it for a living, with capital accounts, statements and an audit trail behind every figure. The hard part is handling the full complexity of the DeFi activity. The book has to be built from those before it can roll up into something you can check against onchain data.
Both, tied to each other. The administrator’s rigor applied to DeFi, where the ledger gets built transaction by transaction and then reconciled against the balance snapshot, so any difference shows up instead of disappearing into the total. We take reconciliation apart on its own page.
Run independently alongside an administrator, the third way is to use a provider for shadow NAV. It does not replace an administrator. It replaces the part of the administrator’s job that digital assets broke.
What a fund administrator covers
Section titled “What a fund administrator covers”A regulated fund uses a fund administrator. They deliver:
- The official NAV of record, the number your fund reports and your investors subscribe and redeem on.
- The books behind it: balance sheet, income statement, capital accounts.
- Investor services. The portal, the subscription and redemption workflow, the register.
- Onboarding and screening. KYC, KYB, and AML.
- The regulatory standing that lets them do all of it in your jurisdiction.
Most of that apparatus is commodity and inexpensive on an annualized basis. The books cost the most, and DeFi exposure is what causes difficulty.
Where a snapshot runs out
Section titled “Where a snapshot runs out”Nobody shopping for a fund administrator lands on a crypto NAV service by accident. Different buyers, different budgets, different reasons.
The trouble starts when a snapshot refreshing every hour gets treated as having caught up with an administrator reporting monthly. A snapshot wins on frequency and loses on two things.
It does not do the accounting. A balance is a position, not a book. No capital accounts, no journal behind each figure, no cost basis carried through a wrap or a bridge, and nothing to hand an auditor except the balance and your word for it.
It cannot tell you where the P&L came from. A total says the fund made money. It does not say which positions made it, and a position that loses money every period looks fine inside a positive total. Split one NAV move into a price effect and a yield effect per position and a reportable number becomes an actionable one. A snapshot has nothing to split.
Your LPs are asking the second one whenever they ask how the fund did, and no refresh rate answers it.
If you run a regulated fund
Section titled “If you run a regulated fund”You need an administrator. The question is who does the DeFi part of the books, and to what standard.
Ask your administrator how they price a Pendle PT, what they do with a bridge leg delivered to a router, and what reconciliation reports when the book and the chain disagree. The questions to ask work just as well on the administrator you already have as on one you are considering.
If you are not regulated
Section titled “If you are not regulated”A crypto-native fund, say a curator running strategies on a vault platform, has none of that apparatus and does not need it. No feeder to onboard, no redemption desk, no external NAV of record. Comparing yourself to the administrator model on compliance grounds answers a question nobody asked you.
Your depositors want transparency and timeliness, and the administrator model was never built to deliver either at that speed.
Administration runs on a periodic official NAV and an annual audit, so the detail behind the number reaches investors at audit. Yearly, and in crypto frequently later. That rhythm was built for investors who signed a subscription agreement and expect a quarterly letter.
Your depositors did not sign anything of the sort. They can see the vault balance every block and have no view whatsoever of the book underneath it, so they are reading a number without its accounting. Some of them now expect a feed rather than a letter, and a fund that waits until audit to show the composition of its book tends to learn this by watching deposits leave.
You are not buying compliance. You are buying the ability to show a correct, current, checkable book to people who can leave at any moment.
What frequency does not fix
Section titled “What frequency does not fix”Reporting more often does not make a fund safer. A NAV struck daily, computed correctly, from a reconciled book, can still sit on top of an arrangement a depositor was never shown. Correct and true are different properties, and failures sit in the gap between them. Liquidity that cannot be faked and an exploit absorbed across a book are both stories about accurate numbers sitting on top of a position that was not safe.
So frequency and correctness solve the reporting problem, and they do not solve the solvency problem. If somebody sells you the second while describing the first, ask another question.
Where PennyWorks fits
Section titled “Where PennyWorks fits”PennyWorks does shadow accounting. We build a fund’s DeFi books from read-only access, reconciled to the chain, with every figure tracing back to the transaction it came from. Numbers can be delivered as often as daily.
For a regulated fund the administrator strikes the official NAV, and we sit behind the administrator as the independent check on the DeFi part of the book. For a crypto-native fund with no administrator apparatus, it covers everything they need. PennyWorks is not a licensed fund administrator, holds no such license, and produces nobody’s official NAV of record.
If you already have an administrator and the digital asset part is what slips, the partner arrangement exists for exactly that. The rest of your setup stays where it is.
Related
Section titled “Related”- DeFi fund accounting, for what the job involves and why it lands on the portfolio manager.
- Shadow NAV, for the control an independent second computation gives you.
- How to evaluate a DeFi NAV provider, for the questions to put in front of whoever produces your books.
- Or talk to us.