Key points
- A blockchain ledger only adds entries. A mistake is fixed with a new entry, and both entries stay on the list.
- The main change: the correction trail lives on the shared record of shares, next to the fix. The reason and the approver still come from your own file notes.
- Your administrator still keeps the official books and calculates NAV.
- Setups differ. In some, each share is represented on a blockchain and also tracked off chain in a registry. Which record controls is a question for counsel.
- A shared record does not create instant liquidity. Redemption terms and fund assets still decide when investors are paid.
- The five questions to ask first come as a sample file note.
It is a few weeks before the annual audit. The auditor asks why one investor's balance changed last spring. The share register shows only the current number, because someone typed over the old one. Nobody remembers the details or who signed off.
A blockchain ledger changes only part of that picture.
What a ledger is
On a blockchain ledger, entries are only added. Past entries are never edited or erased. For a fund, the entries show which account holds how many shares and when that changed.
This rule matters most when an entry is wrong. The real question is what stays on the record after the fix.
Example: fixing a wrong entry
This is a hypothetical example with round numbers.
Account A receives 1,000 shares on March 3. That is Entry 1. On March 5, a redemption is recorded as 100 shares. That is Entry 2, and the balance shows 900. On March 9, before any cash is paid, the team finds the request was for 10 shares, not 100.
In a register that allows overwrites, someone changes 900 to 990. Any history lives in that system's own audit log, if it keeps one. On a ledger, someone adds Entry 3 for plus 90 shares. Entry 2 stays on the shared list itself.
The entries add up: 1,000 minus 100 plus 90 is 990. That matches the true balance of 1,000 minus 10.
Now the record holds the wrong entry, the correcting entry and the date of each. The wrong entry is not hidden. It sits next to the fix. A reviewer can see what happened without asking anyone to remember it.
- Entry 1 Mar 3 Shares issued Plus 1,000
- Entry 2 Mar 5 Redemption recorded as 100, should be 10 Wrong entry (kept) Minus 100
- Entry 3 Mar 9 Correction (added) Plus 90
- Balance now
- 990 shares
What it changes
The example points to three practical gains.
What you can show an auditor. An auditor wants the full story of each correction. That means four things:
- The original entry: Entry 2, minus 100 shares on March 5.
- The correction: Entry 3, plus 90 shares on March 9.
- The reason: the request was for 10 shares, not 100.
- Who approved the correction, and when.
The ledger holds the first two. The reason and the approver come from your own file notes, so they belong in the file when you make the fix, not when the auditor asks.
What you can tell an investor who asks. The same file answers investors. Say the holder of Account A asks why the balance moved from 900 to 990. The manager can pull the same four items and send them. The investor needs no ledger access and gets the auditor's answer.
One list to reconcile to. Managers and administrators often keep their own versions of the same share counts. A shared record of shares can give both sides one list to check against. The administrator's books still sit alongside it.
What it does not change
The gains are narrow. Four things stay where they were.
The legal record. If the on-chain and off-chain records ever differ, which one controls? That is a question for your counsel, and the answer belongs in writing.
The official books. Your administrator keeps the official books of the fund and calculates NAV. A ledger of shares is not a set of accounts. It does not replace fund accounting, tax work or audit.
The rules. A fund share on a ledger is still a fund share. How securities law applies to your setup is a question for counsel.
Redemption timing. The record can update fast. The assets behind an evergreen fund, such as loans or property, cannot always be turned into cash fast. Fund terms and available cash still decide when investors are paid.
What it adds up to
For a small fund, the gain is mainly a cleaner share record with a visible correction trail. It does not bring in buyers or cash, so the useful work happens before you choose a setup.
Questions to ask first
The sample file note below turns this article into five questions, ready to copy, with a column to date each answer.
| Question | Who answers | Keep on file | Answer and date |
|---|---|---|---|
| Which record is the legal record, and who maintains it? | Your counsel | A written answer | |
| Who can add an entry, and how is each addition approved? | The ledger provider and the manager | Named roles and approvers | |
| How is a mistake corrected, and how is the correction shown? | The ledger provider | A sample correction, like Entry 3 above, with its reason and approver | |
| How often is the ledger reconciled to the administrator's register, and who signs off? | The administrator and the manager | The schedule and the sign-off name | |
| Who explains the record to your auditor, before the audit? | You, the administrator and the ledger provider | A name and contact in the audit file |
Back to the auditor. With a ledger and a filled-in file note, the answer is in the file: the wrong entry and the fix on the ledger, the reason and the approver in your note. Nobody has to rely on memory.
Where Tahoe fits
The auditor in the opening scene asked about the share record, not the fund's books. Tahoe is fund operations infrastructure for tokenized funds that works alongside your administrator, not in place of it.
We are building Tahoe on the two-record setup described above, with each share represented on a blockchain and also tracked off chain in a registry. Which one controls stays a question for your counsel. In that design, investors see the fund's own records in a portal in your fund's brand, not ledger entries. Your administrator keeps the books.