The Tokenised Cayman Fund: The 2026 Statutory Framework

Cayman created two statutory categories of tokenised fund with effect from 24 March 2026. The Mutual Funds (Amendment) Act, 2026 inserted Part 3B, Tokenised Mutual Funds, comprising sections 22I and 22J. The Private Funds (Amendment) Act, 2026 inserted section 19A, headed "Requirements for tokenised private funds", and section 19B. A tokenised mutual fund is one that has any of its equity interests represented by digital equity tokens. Tokenisation is a layer on an existing regime, not a third regime.

The question managers should ask is not whether Cayman permits a tokenised fund, because since March it plainly does. It is whether they are willing for the whole fund to carry that characterisation, and whether the register, transfer restriction, anti-money laundering and audit questions are answered before the first token is minted. Those questions are answered before launch or they are not answered at all. David Lloyd, Chief Executive Officer at CV5 Capital

Executive Summary

The 2026 amendments give Cayman fund tokenisation a defined statutory home for the first time. They do not create a new regime, they do not relax any existing obligation, and the perimeter question they answer is narrower than most commentary suggests.

• The framework commenced on 24 March 2026, and material published before that date describes a position that has been superseded.
• The amendments were inserted into the Mutual Funds Act and the Private Funds Act, so a tokenised mutual fund remains a mutual fund for every other purpose of that Act. That includes the section 4(3) minimum aggregate equity interest of CI$80,000 and the annual CIMA fee of CI$4,125 or US$5,030.49 under the fee schedule updated 1 January 2026.
• Both definitions turn on the word "any", so one tokenised share class out of six brings the whole fund within the category, with no de minimis threshold and no materiality qualifier.
• The definitions say the interests are "represented by" tokens. A digital equity token is defined as a digital representation of the whole of an equity interest held by an investor, which has direct consequences for the register of members and for fractionalisation.
• The Virtual Asset (Service Providers) (Amendment) Act, 2026 confirms that issuance of these tokens by these funds is not a virtual asset issuance. It does not carry custody, exchange, transfer services or venue operation, and it does not carry activity by any other person.
• Tokenisation does not solve distribution, does not disapply the offering restrictions, does not create liquidity where there is no buyer, and does not alter the regulatory perimeter of the underlying strategy.

What changed on 24 March 2026, and what the position was before

Yes, you can tokenise a Cayman fund, and since 24 March 2026 you do so inside a defined statutory category rather than by structuring around the absence of one.

Three amending Acts took effect on that date. The Mutual Funds (Amendment) Act, 2026 inserted Part 3B into the Mutual Funds Act, headed "Tokenised Mutual Funds" and comprising sections 22I and 22J. The Private Funds (Amendment) Act, 2026 inserted section 19A, headed "Requirements for tokenised private funds", and section 19B into the Private Funds Act. The Virtual Asset (Service Providers) (Amendment) Act, 2026 dealt with the perimeter question, and section four below sets out precisely what it does and does not carry.

Before commencement, a Cayman fund could be tokenised, and some were. What did not exist was a statutory category. Tokenisation was a matter of the fund's constitutional documents, its offering document, its administration arrangements and a set of legal opinions, assembled bespoke each time. The recurring questions were the same on every deal. Whether the token was the interest or merely evidenced it. Whether the register or the ledger governed title. Whether issuing the token amounted to the issuance of a virtual asset, and how a regulator would characterise the structure if asked. Those questions were answered by analysis and by engagement, not by a provision you could cite.

The change is narrower and more useful than "Cayman has legislated for tokenised funds" suggests. The perimeter question has been answered. The category now has a name, a definition and a home in the statute book. What has not changed is the substance of fund regulation.

The practical consequence of the second row deserves emphasis. Cayman drew a deliberate distinction between the mutual fund token and the private fund token, and gave them different defined names. Anyone drafting a term sheet, an offering document or a token specification should use the term that matches the fund's regulatory category. Referring to "digital equity tokens" issued by a private fund is a drafting error that a regulator, an auditor or an allocator's counsel will notice.

The two new statutory categories, defined exactly

The definitions are the load-bearing element. A tokenised mutual fund is "a mutual fund that has any of its equity interests represented by digital equity tokens". A tokenised private fund is "a private fund that has any of its investment interests represented by digital investment tokens". A digital equity token is defined as a digital representation of the whole of an equity interest held by an investor in a mutual fund. A digital investment token is the equivalent for an investment interest in a private fund. Both fund definitions are constructed the same way: an existing regulated category, plus a representation layer, plus the word "any".

Four features of that drafting matter, and three of them are routinely missed.

First, the category is derivative. Each definition begins with an existing regulated category, "a mutual fund that", "a private fund that". If the vehicle is not a mutual fund within the Mutual Funds Act, or a private fund within the Private Funds Act, it cannot be a tokenised mutual fund or a tokenised private fund however it issues its interests. A vehicle that falls outside both Acts and issues tokens is not in this framework at all, and in particular does not get the benefit of the virtual asset issuance carve-out, which is expressed by reference to these defined categories.

Second, the object of the tokenisation is the fund's own interests, not its portfolio. Equity interests in the case of a mutual fund; investment interests in the case of a private fund. A fund that holds tokenised treasuries, tokenised credit or any other tokenised asset in its portfolio is not thereby a tokenised fund. The distinction between tokenising the wrapper and holding tokenised assets is the single most common conflation in this area, and the statute resolves it cleanly on the wrapper side.

Third, the word is "represented by", not "constituted by" or "evidenced by". The equity interest continues to exist as an equity interest. The token represents it, and the token definition is expressed by reference to the whole of that interest rather than a fraction of it. That is a deliberate and consequential choice, and section six below works through what it means for the register of members, for transfers and for redemptions.

Why "any" matters: partial tokenisation brings the whole fund into scope

The definitions do not say "substantially all of its equity interests", or "a material proportion", or "the class of equity interests that is tokenised". They say any. The consequence is that the statutory category attaches at the level of the fund, and a single tokenised interest is sufficient to attach it.

• A pilot is not ring-fenced. A manager operating a fund with five conventional share classes who tokenises a sixth class for a single digital-native allocator has, on the face of the definition, made the entire fund a tokenised mutual fund. What Part 3B requires applies to the fund, not to the sixth class.
• There is no threshold to fall below. Because the trigger is "any", there is no proportion of tokenised interests small enough to keep the fund outside the category. One token held by one investor is enough.
• Exit is not symmetrical with entry. Entering the category requires one tokenised interest. Leaving it requires that no interest is represented by a token, which means every token outstanding must be redeemed, converted or otherwise extinguished, and the fund must be able to demonstrate that. A structure that is easy to enter and difficult to leave should be entered deliberately.
• It is a governance decision, not a technology decision. Tokenising a single class is often presented internally as an experiment run by the operations team. On this drafting it is a change to the fund's regulatory characterisation and should go to the board as such, with the offering document, the administration agreement and the anti-money laundering procedures reviewed in the same paper.
• The segregated portfolio question is live. Where a segregated portfolio company is registered as a mutual fund, "the fund" for the purposes of the Act is ordinarily the company. Sub-fund increments are payable per segregated portfolio at CI$750 or US$914.63 under the fee schedule updated 1 January 2026. If the company is the fund, then tokenising the shares of one segregated portfolio raises the question whether the whole company becomes a tokenised mutual fund. That is precisely the kind of question the word "any" forces, and where the point is material it should be taken to Cayman counsel rather than assumed either way.

The commercially important point is the third one. Managers considering a limited pilot should understand that the pilot is not a limited commitment. The correct sequencing question is not "shall we tokenise one class and see", but "are we willing for this fund to be a tokenised fund, and if not, should the tokenised strategy sit in a separate vehicle". For managers running multiple share classes, that question should be answered before any token is minted.

What a tokenised fund must do that an untokenised fund need not

Section 19A of the Private Funds Act is headed "Requirements for tokenised private funds". Part 3B of the Mutual Funds Act performs the equivalent function for mutual funds across sections 22I and 22J. The obligations run along the same lines in both regimes.

• Annual confirmation on records. The operator must confirm annually to CIMA that records relating to the issuance, creation, sale, transfer and ownership of interests represented by tokens are properly kept and maintained in compliance with the Act.
• Operator approval of transfers. Interests represented by tokens are transferable only with the approval of the operator, given in accordance with the offering document. Free transferability is therefore not available within the statutory category.
• Token-specific risk disclosure. The offering document must identify the risks specific to the tokens, including cybersecurity and transferability risks, and must explain how those risks are addressed or mitigated for investors.
• Characteristics restrictions. CIMA may impose specific restrictions on the characteristics of a token, and the fund must comply with any restriction imposed.
• Periodic reporting and information. The fund must comply with any periodic reporting requirement specified by CIMA, and CIMA may request further information and monitor ongoing compliance.
• Administrator record-keeping. Records relating to token issuance, creation, sale, transfer and ownership must be securely maintained and made available to CIMA on request.
• Supervisory powers. Section 22J of the Mutual Funds Act and section 19B of the Private Funds Act give CIMA supervisory oversight of tokenised funds, extending to inspection of the underlying technology and of token transactions.

The requirements are additive. They sit on top of the fund's existing obligations, not in substitution for them. Nothing in the placement of these provisions relieves a tokenised fund of any obligation that applies to it as a mutual fund or a private fund. The two regimes are not identical, because the underlying regimes are not identical, and the table below sets out where they diverge.

Beyond the statute, tokenisation creates a set of workstreams that a conventional fund does not have. These are operational necessities rather than statutory assertions, and they are the items that in practice determine whether a tokenised launch is deliverable:

1. Offering document disclosure covering the token layer, the ledger, key management, transfer restrictions, and the consequences of a discrepancy between ledger and register.
2. A transfer restriction architecture that is enforceable at both the ledger layer and the constitutional-document layer, because enforcement at only one of them produces the mismatch described in section six.
3. An anti-money laundering and sanctions procedure that addresses secondary transfers, since every transferee is an incoming investor. CIMA's rule on an effective compliance programme for money laundering, terrorist financing and proliferation financing takes effect on 18 September 2026, as does its rule on compliance with financial sanctions and targeted financial sanctions. Both apply to the fund irrespective of tokenisation.
4. Administration and transfer agency arrangements with a provider whose systems can maintain the register as the record of title and reconcile it to the ledger on a defined cycle.
5. An audit approach agreed in advance with the auditor on existence and ownership assertions over interests represented by tokens.
6. Board reporting that covers key management, wallet governance and incident escalation, which is where allocator operational due diligence now concentrates.

Each of those workstreams carries an incremental cost over an untokenised equivalent, across technology, legal drafting, administration and audit. Those costs are commercial rather than statutory, they vary materially with the strategy, the ledger and the investor base, and they are quoted on enquiry rather than published. Statutory fees are unchanged by tokenisation.

The VASP interaction: what the 2026 amendment covers and what it does not

The Virtual Asset (Service Providers) (Amendment) Act, 2026 confirms that the issuance of digital equity tokens or digital investment tokens by a regulated tokenised fund is not a virtual asset issuance under the Virtual Asset (Service Providers) Act. It operates on the scope of virtual asset issuance rather than by granting the fund a licence or an exemption from anything else.

State the conditions in full, because the position is conditional and it is frequently quoted without them. On its terms it applies where all of the following hold:

1. the issuer is a tokenised mutual fund or a tokenised private fund, each as defined in the amended Mutual Funds Act and Private Funds Act respectively;
2. the instrument issued is a digital equity token for a mutual fund, or a digital investment token for a private fund, as those terms are defined; and
3. the activity in question is issuance.

What the amendment does not do is where the analysis actually lives. A tokenised fund that provides virtual asset services to third parties, such as exchange or custody services, remains fully subject to the Virtual Asset (Service Providers) Act.

The commercially useful way to state this: the amendment removes the fund itself from the virtual asset issuance perimeter in respect of one activity. It does not sterilise the structure. Where the tokenisation model contemplates custody, a venue or a secondary market, the perimeter question relocates to those participants rather than disappearing. This is examined further in the analysis of where the VASP licensing line falls for tokenised funds.

Tokenisation is a wrapper, not a third regime

The strongest evidence for this proposition is the drafting technique. Cayman did not enact a Tokenised Funds Act. It inserted Part 3B into the Mutual Funds Act and sections 19A and 19B into the Private Funds Act. A tokenised mutual fund is therefore a mutual fund for every purpose of the Mutual Funds Act, and a tokenised private fund is a private fund for every purpose of the Private Funds Act. Tokenisation adds; it does not displace.

The practical consequences follow mechanically:

• Registration category is unchanged. A tokenised mutual fund registers in whichever category applies to it. Tokenisation is not a registration category.
• Section 4(3) still applies. The minimum aggregate equity interest purchasable by a prospective investor of CI$80,000, commonly expressed as approximately US$100,000, applies to a tokenised mutual fund as it does to any other, unless the fund is a limited investor fund under section 4(4). Section 4(4) requires equity interests to be held by not more than fifteen investors, a majority of whom are capable of appointing or removing the operator of the fund. Both limbs are conditions and the audit requirement still applies. The token is defined as a representation of the whole of an interest, so fractionalising below the section 4(3) floor is not a way round it.
• The Private Funds Act timing rules still apply. Application within twenty-one days after acceptance of capital commitments under section 5(1)(a); no acceptance of capital contributions until registered under section 5(6). The twenty-one days runs from commitments; the prohibition bites on contributions. Tokenised subscription mechanics make it easier, not harder, to accept a contribution before registration by accident.
• Fees are unchanged. CI$4,125 or US$5,030.49 annually for a registered mutual fund and for a private fund under the fee schedule updated 1 January 2026, with sub-fund increments of CI$750 or US$914.63 and segregated portfolio increments of CI$525 or US$640.24 respectively. Annual fees are due on or before 15 January each year. The separate fund annual return filing fee of CI$300 or US$365.85 applies for financial years ending on or before 31 December 2025.
• Audit, anti-money laundering, directors' registration and economic substance are unchanged. The CIMA compliance programme rule and sanctions rule take effect on 18 September 2026 and apply on their own terms.
• Information reporting is unchanged in principle and more complex in fact. FATCA and CRS obligations attach to the fund as a financial institution. Amended CRS took effect on 1 January 2026 and expands the CRS perimeter to capture crypto-assets, principally where held indirectly. CARF came into force on 1 January 2026, with registration for pre-existing reporting crypto-asset service providers by 30 April 2026 and first reports due 30 June 2027 for calendar year 2026. Whether any participant in a tokenised fund structure is a reporting crypto-asset service provider is a separate analysis and should not be assumed either way.

The corollary is a useful test for any claim made about tokenisation. If a proposition would be false for the same fund without a token layer, it is almost certainly false with one. Tokenisation does not create capacity to do something the underlying Act prohibits.

Operational consequences: transfer agency, the register, NAV and redemptions

Return to the words "represented by". The equity interest exists; the token represents it. That framing has four operational consequences that determine how a tokenised fund is actually run.

The register remains the record of title

The 2026 amendments amend the Mutual Funds Act and the Private Funds Act. Those are regulatory statutes. They are not the source of law that determines legal title to shares in a Cayman exempted company or to partnership interests in an exempted limited partnership. That sits in the Companies Act and the Exempted Limited Partnership Act respectively, and in the fund's constitutional documents. Whether a distributed ledger record can stand as, or evidence, the statutory register is therefore a question of company and partnership law rather than one the tokenised fund provisions answer.

The design question is unavoidable and should be answered explicitly in the constitutional documents: is the register the record of title with the ledger as a mirror, or is the ledger intended to be determinative? A structure that leaves this ambiguous has a defect that will surface at the worst moment, which is a disputed transfer or a liquidation. How the official register works in a tokenised fund is not a technical footnote; it is the first question a serious counterparty asks.

Transfer restrictions have to bind in two places

The statutory requirement that transfers be made only with the approval of the operator, in accordance with the offering document, has to be given effect somewhere. A token that can move without a corresponding update to the register produces a holder on-chain who is not an investor of record, and an investor of record who no longer holds the token. Both positions are unsatisfactory. The architecture therefore has to enforce restrictions at the ledger layer, through allowlisting or an equivalent permissioning mechanism, and at the constitutional-document layer, through the discretion of the directors or the general partner to refuse registration of a transfer. Enforcement at one layer only is the most common structural weakness in tokenised fund designs, and it is a live topic in wallet and transfer restriction governance.

Secondary transfers are investor onboarding events

The commercial attraction of a token is transferability. The anti-money laundering regime treats each incoming holder as an investor requiring onboarding, and the CIMA compliance programme rule effective 18 September 2026 does not carve out on-chain transfers. Reconciling those two facts is why credible tokenised funds are permissioned rather than freely transferable, and why the design of anti-money laundering and know-your-client checks on secondary transfers is a gating item rather than a later refinement.

NAV, subscriptions and redemptions

Tokenisation does not change the valuation policy, the dealing calendar or the fund's obligations on redemption. A few consequences follow:

• A token that is transferable continuously against a NAV struck periodically creates a basis between the traded price and NAV. Somebody bears that basis. The offering document should say who, and should not imply that the token trades at NAV.
• Redemption obligations run to the holder of the interest as recorded, which returns to the register question above. Burning a token does not by itself discharge a redemption if the register has not been updated.
• Subscription in tokenised cash, where contemplated, engages the same acceptance-of-contributions timing analysis under Private Funds Act section 5(6) as any other subscription, and the settlement finality question is a matter for the administrator and the board, not the technology.
• Gates, suspensions, side pockets and compulsory redemption powers all need a mechanical expression at the token layer. If the constitutional documents permit suspension but the token cannot be frozen, the power is theoretical.

These points are developed further in the operational treatment of transfer agency and NAV in a tokenised fund.

What tokenisation solves, what it does not, and where it is still untested

The honest position is that tokenisation is a genuine improvement to a narrow set of problems and irrelevant to most of the problems that determine whether a fund succeeds.

Two of those rows are worth restating plainly, because they are where expectations most often break. Tokenisation does not create liquidity: a secondary market requires a buyer, a price and a venue, and a fund whose interests nobody wishes to buy is illiquid in token form exactly as it was in registered form. And tokenisation does not reduce the regulatory perimeter of the strategy: the analysis of what the fund does with its capital is untouched by how its interests are represented.

Where the framework is still untested

The framework commenced on 24 March 2026. As at August 2026 it has been in force for approximately five months. That is not long enough for a body of supervisory practice, market convention or judicial interpretation to have formed, and any source that presents settled answers to the questions below should be treated with caution.

1. Application to segregated portfolios. Whether tokenising the shares of one segregated portfolio of a company registered under the Mutual Funds Act brings only that portfolio or the whole company within the tokenised mutual fund category. The word "any" points one way; the practical result points the other. Where the point is material, take specific Cayman legal advice.
2. Ledger versus register. Whether and in what circumstances a distributed ledger entry can constitute or evidence the legal record of title, and what happens where the two diverge.
3. Transfers in breach of restrictions. The position of a transferee who acquires a token on-chain in breach of a transfer restriction, particularly one who acquires without notice. There is no Cayman authority on this point in a tokenised fund context.
4. Conflict of laws. Where a token representing an interest in a Cayman fund trades on a venue in another jurisdiction and is held through a foreign intermediary, which law governs title, and how that interacts with the fund's constitutional documents.
5. Insolvency and wind-down. How a liquidator treats holders identified only on-chain, how the ledger interacts with the statutory scheme of distribution, and what happens to interests whose keys are lost. The framework has not been tested in a Cayman liquidation.
6. Audit assertions. How Cayman-approved auditors will approach existence, ownership and completeness assertions over interests represented by tokens, and what evidence they will require over key management and ledger controls.
7. De-tokenisation. Whether, and on what evidence, a fund that has redeemed or converted all outstanding tokens ceases to be a tokenised fund, and what notification that requires.
8. Supervisory expectations. The powers to restrict token characteristics and to specify periodic reporting will be given practical content by CIMA's supervisory approach over time, and the market's understanding in August 2026 is necessarily provisional. Practitioner accounts such as how the CIMA tokenised fund questionnaire works in practice reflect experience to date, not settled doctrine.

Decision framework: should you tokenise

The question has a determinate structure. Work the steps in order and stop at the first one that returns a negative.

For managers evaluating where a tokenised structure sits within a broader platform decision, the tokenised funds and fund tokenisation pages set out the structural options, and the tokenised fund legal document suite covers the drafting workstream in detail.

Key Takeaways

• Take the decision to tokenise to the board as a change to the fund's regulatory characterisation, not to the operations team as a technology pilot.
• Decide in the constitutional documents, before any token is minted, whether the register or the ledger governs title, and how the two are reconciled.
• Build the operator approval requirement into both the ledger permissioning and the directors' or general partner's power to refuse a transfer, because one layer alone will not hold.
• Treat every secondary transferee as an incoming investor to be onboarded before settlement, and test the procedure against the CIMA rules taking effect on 18 September 2026.
• Agree the audit approach to existence and ownership over tokenised interests with the auditor before launch rather than at the first year end.
• Where a segregated portfolio, a secondary venue, a custodian or an overseas holder is involved, take specific Cayman legal advice rather than reading the framework by analogy.

Frequently Asked Questions

Can I tokenise a Cayman fund?

Yes. Since 24 March 2026 the Mutual Funds Act contains Part 3B, Tokenised Mutual Funds, at sections 22I and 22J, and the Private Funds Act contains sections 19A and 19B. A mutual fund with any of its equity interests represented by digital equity tokens is a tokenised mutual fund; a private fund with any of its investment interests represented by digital investment tokens is a tokenised private fund.

What are the new Cayman tokenised fund rules?

The operator must confirm annually to CIMA that records of token issuance, creation, sale, transfer and ownership are properly maintained. Transfers require the operator's approval in accordance with the offering document. The offering document must disclose token-specific risks, including cybersecurity and transferability risks, and explain how they are mitigated. CIMA may restrict token characteristics, specify periodic reporting, and inspect the underlying technology.

What is a digital equity token under Cayman law?

It is defined as a digital representation of the whole of an equity interest held by an investor in a mutual fund. The private fund equivalent is a digital investment token, representing the whole of an investment interest. The two terms are distinct and should be used according to the fund's regulatory category. Because the token represents a whole interest, it is not a route to fractional participation.

Does a tokenised Cayman fund need VASP registration?

Not for issuing its own tokens. The Virtual Asset (Service Providers) (Amendment) Act, 2026 confirms that issuance of digital equity tokens or digital investment tokens by a regulated tokenised fund is not a virtual asset issuance. Custody, exchange, transfer services and venue operation are not covered, and a fund providing virtual asset services to third parties remains fully subject to the VASP Act.

Is a tokenised fund a different regime from a mutual fund?

No. Part 3B was inserted into the Mutual Funds Act and sections 19A and 19B into the Private Funds Act, rather than enacted separately. A tokenised mutual fund remains a mutual fund for all purposes of that Act, including the section 4(3) minimum of CI$80,000, audit, and the annual CIMA fee of CI$4,125 or US$5,030.49 under the schedule updated 1 January 2026.

What happens if only some share classes are tokenised?

The whole fund falls within the category. The definitions turn on "any of its equity interests" and "any of its investment interests", with no de minimis threshold and no materiality qualifier. One tokenised class out of six, or a single token held by one investor, is sufficient. Partial tokenisation is therefore a decision about the fund's characterisation, not a contained pilot.

What does tokenising a fund actually achieve?

It improves transfer and settlement mechanics, automates the investor record, allows transfer restrictions to be enforced programmatically, and makes the fund holdable by allocators operating on-chain. It does not create liquidity, does not assist distribution, does not disapply the CI$80,000 minimum under section 4(3) of the Mutual Funds Act, and does not change the regulatory perimeter of the underlying strategy.