Operating a Tokenised Fund: Transfer Agency, On-Chain Registers and NAV Mechanics

The legal architecture of tokenised funds is now well documented: the Cayman Islands framework that commenced on 24 March 2026 settled how a regulated fund may issue tokenised interests, and 52% of institutions express interest in tokenisation according to the AIMA and PwC Global Crypto Hedge Fund Report. What almost nobody has written down is the operator's playbook, meaning who actually maintains the register, how a mint maps to a subscription, what happens to a token when an investor redeems, and how NAV is published for a share class that settles on-chain. Those mechanics, not the legal wrapper, are what an allocator's operational due diligence team will spend its time on.

"Tokenisation succeeds or fails in the back office. The question an allocator asks is never whether the token is elegant; it is whether the token supply, the share register and the administrator's books say the same thing at the same NAV point, every dealing day, with someone accountable when they do not."David Lloyd, Chief Executive Officer at CV5 Capital

Why This Matters for Funds and Managers

Since the Mutual Funds (Amendment) Act, the Private Funds (Amendment) Act and the VASP (Amendment) Act commenced on 24 March 2026, a CIMA-regulated Cayman fund has been able to issue tokenised interests within its existing registration, with token issuance by regulated funds excluded from the separate virtual asset licensing regime. The legal question of whether a fund may tokenise is therefore largely answered, and we cover it in the tokenised Cayman fund handbook and our analysis of what CIMA actually requires of tokenised funds. The operating question of how a tokenised fund runs day to day is the one that now separates credible launches from marketing exercises.

The distinction matters because allocators underwrite operations, not technology. When an institutional investor reviews a tokenised vehicle, the file it builds is about reconciliation controls, dealing mechanics and accountability, a process we described in how allocators underwrite tokenised Cayman funds. CIMA's own supervisory engagement follows the same pattern: its tokenised fund questionnaire probes register control, reconciliation frequency and the division of responsibility between service providers, as we set out in the CIMA tokenised fund questionnaire in practice.

The Common Misunderstanding

The misconception at the heart of most failed designs is that the blockchain replaces the transfer agent. It does not. In a properly structured tokenised fund, the on-chain token ledger is a representation layer, while the legal record of who owns the fund remains the share register maintained under Cayman law, in practice by the administrator or transfer agent. The token evidences the registered interest; it is not a bearer instrument that is itself the interest. That design choice is not conservatism for its own sake. It is what allows the fund to deal with lost wallet keys, erroneous transfers, court orders and sanctions events without the absurd result that whoever holds the token owns the fund.

The second misunderstanding is that on-chain settlement removes reconciliation work. In practice it adds a third record. A traditional fund reconciles the register against the administrator's books. A tokenised fund reconciles the register, the administrator's books and the token supply on the relevant chain, and the reconciliation must hold at every mint, burn and transfer. The operational integrity of that three-way tie-out is the core of the operating model, not an afterthought to it.

The Practical Reality: The Operating Cycle of a Tokenised Fund

Walked through end to end, the cycle looks familiar to anyone who has run a fund, with a token layer bolted to each dealing event. At subscription, the investor completes AML and eligibility checks exactly as in any regulated fund; the administrator accepts the subscription, issues shares or interests on the register, and only then is a corresponding quantity of tokens minted to the investor's whitelisted wallet. At redemption, the sequence reverses: the redemption request is processed against the register at the dealing NAV, the tokens are burned or swept from the investor's wallet, and proceeds are settled. Transfers between investors, where permitted at all, are constrained by the whitelist so a token cannot move to a wallet that has not been through onboarding. NAV is struck by the administrator on the underlying portfolio in the ordinary way, using the valuation governance described in our guide to the fund valuation policy, and is then published to token holders, typically off-chain through the usual investor channels and, where the design calls for it, pushed on-chain as a reference value. Corporate actions, such as equalisation adjustments, side pocket creation, compulsory redemptions or a share class restructuring, are executed on the register first and reflected in token supply through administrative mint and burn functions reserved to the issuer.

None of this happens by itself, which is why the division of labour must be written down before launch. The table below sets out the allocation that works in practice.

Key Considerations Before the First Mint

Managers coming to tokenisation from a trading background often underestimate how much of the work is procedural. The controls below are what CIMA and allocators alike will expect to see documented, and they echo the licensing perimeter analysis we set out in where the VASP licensing line falls for tokenised funds.

How the CV5 Platform Model Helps

CV5 does not make investment decisions for third-party strategies and is not a law firm, administrator, auditor or investment adviser. Managers retain their strategy, branding and investment discretion, supported by the regulated infrastructure described at the fund tokenisation service page.

Risks and Caveats

The operating model described here is a general template, not a specification for any particular fund. Designs differ on genuine questions, including whether tokens are issued for all share classes or one, whether secondary transfers are permitted at all, which chain and token standard are used, and how much NAV information is pushed on-chain. Smart contract functions such as freeze and forced transfer carry their own governance risks and should be reviewed by counsel and, where appropriate, independent technical auditors. The Cayman framework commenced on 24 March 2026 and supervisory practice under it is still developing; managers should confirm the current position with Cayman counsel before launch, and should not assume that operational choices acceptable in one structure will be acceptable in another.

Key Takeaways

• Since 24 March 2026 a CIMA-regulated Cayman fund can issue tokenised interests within its existing registration; the open question for managers is operational, not legal.
• The token is a representation layer; the legal record remains the share register, and the administrator's records are the golden source in any conflict.
• Mints map to subscriptions and burns to redemptions, always following the register entry rather than preceding it, with whitelisting enforced at the contract level.
• A tokenised fund reconciles three records, register, books and token supply, at every dealing day and NAV point, with a written escalation path for breaks.
• The division of labour between issuer, administrator, transfer agent and tokenisation platform must be documented before launch, because it is the first thing CIMA and allocators will ask to see.

Frequently Asked Questions

Who maintains the share register in a tokenised fund?

The administrator or transfer agent maintains the legal share register, exactly as in a conventional fund. The on-chain token ledger represents registered interests but does not replace the register, and well-drafted offering documents state that the register prevails in any conflict between the two records.

How do subscriptions and redemptions work with tokens?

Subscriptions follow the normal sequence, AML and eligibility onboarding, acceptance and register entry, and only then are tokens minted to the investor's whitelisted wallet. Redemptions reverse it: the request is processed at the dealing NAV, tokens are burned or swept, and proceeds are settled. The register event always drives the token event.

Is NAV calculated differently for a tokenised share class?

No. The administrator strikes NAV on the underlying portfolio under the fund's valuation policy in the ordinary way. What changes is publication and reconciliation: NAV is communicated to token holders on a defined protocol, and token supply is reconciled to the register and books at each NAV point.

What happens if an investor loses access to their wallet?

Because the register, not the token, is the legal record, the fund can generally verify the investor, freeze or invalidate the stranded tokens using reserved administrative functions and reissue tokens to a new whitelisted wallet. The procedure should be written into the fund's corporate action documentation before launch.