Introduction
The Cayman Islands has given tokenised funds a clear statutory home. On 24 March 2026, the Mutual Funds (Amendment) Act, 2026 and the Private Funds (Amendment) Act, 2026 came into force, accompanied by the Virtual Asset (Service Providers) (Amendment) Act, 2026. Before this framework, sponsors who wanted to represent fund interests as blockchain tokens had to work through how the existing funds laws and the separate virtual asset regime applied to their structure, often relying on legal opinion and regulator dialogue rather than express rules. The 2026 amendments replace that uncertainty with definitions, disclosure duties, record-keeping obligations, and named supervisory powers for the Cayman Islands Monetary Authority (CIMA). The headline principle is deliberately conservative: tokenisation does not change what a fund is or how it is regulated. A tokenised mutual fund remains a mutual fund, a tokenised private fund remains a private fund, and the tokens represent fund interests rather than free-standing virtual assets.
This article explains what the new regime requires of sponsors, operators, and administrators of tokenised vehicles, and what it means for managers weighing Cayman against other domiciles for a tokenised strategy. It covers the legal architecture and the three amendment Acts, the definitions of digital equity tokens and digital investment tokens, the offering-document disclosure standard, the annual record-keeping confirmation, the transfer-approval requirement, CIMA's inspection and restriction powers, and the carve-out from the virtual asset service provider rules. Fund sponsors, general counsel, compliance leads, administrators, and managers exploring tokenised share classes will find the specifics needed to scope a launch, brief a board, and decide where to incorporate.
The Legal Architecture: Three Amendment Acts
The framework is not a single new statute. It is built from amendments that slot tokenised funds into the laws Cayman already uses to regulate collective investment vehicles. Reading them together shows the design logic: extend the established regime rather than create a parallel one.
- The Mutual Funds (Amendment) Act, 2026 brings tokenised mutual funds expressly within the Mutual Funds Act. It introduces the concept of a tokenised mutual fund and the digital equity token, and sets the obligations that attach to them.
- The Private Funds (Amendment) Act, 2026 does the equivalent for the Private Funds Act, introducing the tokenised private fund and the digital investment token.
- The Virtual Asset (Service Providers) (Amendment) Act, 2026 clarifies the boundary with the virtual asset regime, confirming that issuing these fund tokens is excluded from the Virtual Asset Service Provider (VASP) rules.
All three commenced on 24 March 2026. The combined effect is that a tokenised fund is regulated as a fund, supervised by CIMA under the relevant funds law, and kept out of the separate VASP perimeter for the act of issuing its own tokens.
Tokenisation changes the wrapper, not the regime
The single most important point in the 2026 framework is that tokenising a fund interest does not reclassify the vehicle. A tokenised mutual fund stays under the Mutual Funds Act and a tokenised private fund stays under the Private Funds Act. The investor protection, anti-money laundering, and supervisory expectations that apply to traditional Cayman funds apply in full. Treat the token as a new way of representing an interest, not as a new kind of asset that escapes fund regulation.
How the Framework Defines Tokenised Funds
Definitions do the heavy lifting in this regime, because they determine which vehicles are caught and what a compliant token looks like. The amendments draw a clean line between the two fund regimes.
Tokenised Mutual Funds and Digital Equity Tokens
Under the Mutual Funds (Amendment) Act, 2026, a tokenised mutual fund is a mutual fund that has any of its equity interests represented by digital equity tokens. A digital equity token is a digital representation of the whole of an equity interest. The phrasing matters: the token stands for the whole interest, so the on-chain representation maps one-to-one onto the legal equity interest in the fund rather than to a fraction or a derivative of it.
Tokenised Private Funds and Digital Investment Tokens
The Private Funds (Amendment) Act, 2026 mirrors this for closed-ended vehicles. A tokenised private fund is a private fund that has any of its investment interests represented by digital investment tokens, and a digital investment token is a digital representation of the whole of an investment interest. The two regimes use parallel language so that the analysis is consistent across open-ended and closed-ended structures.
| Concept | Mutual funds | Private funds |
|---|---|---|
| Governing law | Mutual Funds Act (as amended 2026) | Private Funds Act (as amended 2026) |
| Vehicle term | Tokenised mutual fund | Tokenised private fund |
| Token term | Digital equity token | Digital investment token |
| What the token represents | The whole of an equity interest | The whole of an investment interest |
| Typical structure | Open-ended, redeemable | Closed-ended, committed capital |
Note: A fund is tokenised if any of its interests are represented by tokens. A vehicle does not need to be fully tokenised to fall within the framework, so a fund issuing a single tokenised share class should expect the regime to apply to that class.
The Offering Document: A Substantive Technology Risk Standard
The most visible new drafting obligation lands in the offering document. The framework requires that the risks specific to the digital token be identified and disclosed, and that the document explain how those risks are addressed or mitigated for investors. This is a two-part duty: disclose the risk, then describe the mitigation.
The amendments single out cybersecurity and transferability as areas that must be considered, but these are illustrative rather than exhaustive. Sponsors should map the full risk surface of their chosen technology and address each material item.
Risks to Identify and Mitigate
- Cybersecurity: Key management, smart-contract vulnerabilities, custody of private keys, and the consequences of a compromise. The document should explain controls, audits, and recovery arrangements.
- Transferability: How transfers are controlled, that operator approval is required, and what happens to a token that is moved without approval or to an ineligible holder.
- Technology and operational failure: Chain reorganisations, network outages, dependence on third-party infrastructure, and the fund's continuity plan if the underlying ledger or service fails.
- Legal and settlement finality: How the token relates to the register of interests, and which record prevails in the event of a discrepancy between the ledger and the fund's books.
Do not treat token risk disclosure as boilerplate
A generic paragraph stating that blockchain involves risk will not meet the standard. The framework asks for risks specific to your token and the mitigations you have put in place. A thin or copied disclosure invites questions from CIMA on application and weakens your position if an investor later complains. Draft this section against your actual architecture, with input from your technology and legal teams.
Record-Keeping and the Annual Operator Confirmation
The framework places real weight on records. Every record relating to the issuance, creation, sale, transfer, and ownership of the tokens representing fund interests must be properly kept, securely maintained, and available for inspection by CIMA. This applies whether the canonical record sits on a public chain, a permissioned ledger, or a combination of on-chain and off-chain systems.
The operator must provide CIMA with an annual confirmation that these records are maintained. The confirmation is not a one-time filing at launch; it is a recurring assurance that the record-keeping discipline holds throughout the life of the fund.
What the Confirmation Covers
- Issuance and creation: Complete records of every token minted and the interest it represents.
- Sale: Records of primary issuance to investors, tied to subscription and eligibility checks.
- Transfer: Records of every transfer, the approval that authorised it, and the parties involved.
- Ownership: A current and accurate picture of who holds each token at any time, reconcilable with the fund's register.
The Administrator's Role for Mutual Funds
For tokenised mutual funds, the licensed mutual fund administrator must be satisfied that record-keeping and compliance for the digital equity tokens meet the required standard. This pulls the administrator into the technology question directly. An administrator can no longer treat the token layer as something outside its remit; it must be comfortable that the systems generating and storing token records are sound enough to support the operator's confirmation.
Design the record architecture before you choose the chain
Decide early which system is the authoritative record of ownership and how the ledger reconciles to the fund's register of interests. Sponsors who pick a chain first and work out record-keeping later often find the two systems disagree at the worst moment. Agree the reconciliation model with your administrator and document which record prevails in a conflict.
Transfer Control: Operator Approval Is Required
A common assumption about tokenised assets is that they move freely peer to peer. The Cayman framework does not adopt that model for fund interests. Transfers of the tokens may only be made with the approval of the fund's operator in accordance with the offering document. Operator approval is the gating mechanism, and it must be reflected both in the legal documents and in the technology.
This has direct engineering consequences. A token that can be transferred to anyone, at any time, without a control point would not sit comfortably within the regime. Sponsors typically implement transfer restrictions through allowlists, eligibility checks, and approval workflows enforced at the smart-contract or platform level, so that an attempted transfer to an unapproved or ineligible party simply does not complete.
Practical Implications of the Approval Requirement
- Anti-money laundering and know-your-customer checks remain in force at the point of transfer, not just at initial subscription. The operator cannot approve a transfer to a holder it has not cleared.
- Investor eligibility for the relevant fund class must be confirmed before a transfer is approved, preserving any restrictions on who may hold an interest.
- Secondary liquidity is possible but controlled. Tokenisation can streamline transfers and settlement, yet it operates within the operator-approval framework rather than replacing it.
CIMA's Supervisory Powers
CIMA administers the regime and the amendments give it express tools to supervise tokenised funds. These powers reach further into the technology than the rules for a traditional fund, reflecting the new risk surface.
Inspection of Technology and Transactions
CIMA's supervisory powers extend to conducting inspections of both the underlying technology supporting tokenisation and the digital token transactions themselves. This is a notable expansion. CIMA can look at the infrastructure, not only the paperwork, and can examine the transaction record on the ledger. Sponsors should assume that the smart contracts, the custody arrangements, and the transaction history may all be subject to review.
Restrictions, Reporting, and Approval Conditions
| Power | What it means for sponsors |
|---|---|
| Restrict token characteristics | CIMA may impose specific restrictions on the features of a token, so design choices may need to satisfy the regulator. |
| Periodic reporting | Any periodic reporting requirement CIMA specifies must be complied with on an ongoing basis. |
| Request additional information | CIMA may require further information before approving a tokenised fund application. |
| Ongoing monitoring | CIMA monitors continuing compliance after registration, not only at the application stage. |
Build for inspection from day one
Because CIMA can inspect the underlying technology and the token transactions, your architecture should be inspectable. Maintain clear documentation of the smart contracts, an auditable transaction history, and a record-keeping system that a regulator can review without bespoke tooling. Designing for inspectability after launch is far harder than building it in.
The VASP Carve-Out: Funds Regime, Not Virtual Asset Regime
One of the most useful clarifications in the 2026 package concerns the boundary with the virtual asset rules. The Virtual Asset (Service Providers) (Amendment) Act, 2026 confirms that the issuance of digital equity tokens by tokenised mutual funds and digital investment tokens by tokenised private funds is excluded from the VASP regime.
This matters because, without the carve-out, a sponsor issuing fund tokens might have faced an argument that it was carrying on a virtual asset service and needed separate VASP registration. The amendment removes that ambiguity for the act of issuing the fund's own tokens. The vehicle is supervised as a fund, by CIMA, under the relevant funds law, and the issuance of its tokens does not pull it into the separate virtual asset perimeter.
That said, the carve-out is specific to the issuance of these fund tokens. Sponsors whose wider activities touch virtual assets in other ways should still analyse where the VASP regime applies to those other activities. The clarification narrows the question; it does not eliminate the need to think about it.
Considering a tokenised fund in the Cayman Islands?
AURNE helps sponsors structure and launch Cayman funds, including tokenised mutual and private fund vehicles, with the offering-document disclosure, record-keeping, and CIMA engagement the 2026 framework now requires. We align the structure with your strategy and your other jurisdictions.
Why Cayman, and How It Compares for Tokenised Strategies
The Cayman Islands moved early to give tokenised funds an express statutory framework rather than leaving them in a grey zone. For managers, that clarity is itself a feature. A named regime, defined token concepts, and known supervisory powers make it easier to obtain legal comfort, satisfy investors, and pass institutional due diligence. The framework was designed to preserve the investor protection and anti-money laundering standards that built Cayman's reputation as a funds domicile, which is why it extends the existing regime rather than carving out a lighter-touch alternative.
For Fund Sponsors and Managers
What the framework means in practice:
- Certainty at launch: You can structure a tokenised mutual or private fund knowing the rules that apply, rather than relying solely on opinion about how older laws map to new technology.
- Institutional credibility: A regulated tokenised vehicle in a recognised domicile is easier to present to allocators than an offshore structure with an uncertain regulatory status.
- Continuity with existing operations: If you already run Cayman funds, a tokenised share class fits within familiar governance, administration, and audit relationships.
For Administrators and Service Providers
The framework raises expectations on the service side:
- Administrators of tokenised mutual funds must be satisfied with token record-keeping and compliance, so they need the capability to assess it.
- Service providers should be ready for CIMA inspection of technology and transactions, with documentation that supports review.
- Reconciliation between the ledger and the fund register becomes a core operational control rather than an afterthought.
For managers comparing domiciles, it is worth weighing Cayman alongside other options where AURNE structures vehicles, including the British Virgin Islands and Mauritius, as well as onshore choices for the operating or management entity. The right answer depends on investor base, strategy, and where the manager and its other entities sit. AURNE advises on Cayman company and fund formation and on worldwide structuring so the fund domicile and the wider group are designed together rather than in isolation.
A Practical Launch Roadmap
Preparation is most effective when the legal, technology, and service-provider workstreams move in parallel rather than in sequence. The plan below assumes a new tokenised mutual or private fund, but the same sequence adapts to adding a tokenised class to an existing vehicle.
Step-by-Step
- Confirm the regime and structure: Decide whether the vehicle is a mutual fund or a private fund, and therefore whether you are issuing digital equity tokens or digital investment tokens. This determines which amended Act governs you.
- Design the token and transfer controls: Specify how the token represents the whole interest, and build operator-approval, eligibility, and anti-money laundering checks into transfers from the outset.
- Define the authoritative record and reconciliation: Agree which system is the record of ownership, how it reconciles to the register, and which record prevails in a conflict.
- Draft the offering-document disclosure: Identify the risks specific to your token, including cybersecurity and transferability, and set out the mitigations. Keep it specific to your architecture.
- Engage your administrator and providers: For a tokenised mutual fund, confirm the administrator is satisfied with token record-keeping and compliance. Brief all providers on inspection readiness.
- Prepare for CIMA: Anticipate requests for additional information, possible restrictions on token characteristics, and any periodic reporting CIMA may specify.
- Operate and confirm annually: Maintain complete records of issuance, sale, transfer, and ownership, and deliver the operator's annual confirmation to CIMA.
Readiness Checklist
- Vehicle classified as mutual or private fund, with the correct token concept selected.
- Token represents the whole interest and maps to the legal register.
- Transfer controls enforce operator approval, eligibility, and anti-money laundering checks.
- Authoritative record and reconciliation model documented and agreed with the administrator.
- Offering document discloses token-specific risks and mitigations, not generic blockchain language.
- Technology, custody, and transaction history documented for CIMA inspection.
- Annual operator confirmation process assigned and scheduled.
Common Pitfalls
- Pitfall one: Assuming tokenisation lightens the regulatory load. It does not; the full fund regime applies.
- Pitfall two: Generic risk disclosure. The framework expects token-specific risks and named mitigations.
- Pitfall three: Free transferability by design. Operator approval must gate transfers, so unrestricted peer-to-peer movement is incompatible with the regime.
- Pitfall four: Treating record-keeping as an engineering detail. The operator must confirm it annually and the administrator must be satisfied with it, so it is a governance obligation.
Key Takeaway
Cayman has made tokenised funds easy to regulate and hard to get wrong by treating tokens as fund interests inside the existing regime. The work for sponsors is in the detail: token-specific risk disclosure, operator-approved transfers, an inspectable record architecture, and an annual confirmation to CIMA that the records hold.
Conclusion
The Mutual Funds (Amendment) Act, 2026, the Private Funds (Amendment) Act, 2026, and the Virtual Asset (Service Providers) (Amendment) Act, 2026 came into force on 24 March 2026 and give tokenised funds a clear statutory framework. The guiding principle is conservative and deliberate: tokenisation changes how a fund interest is represented, not how the fund is regulated. Tokenised mutual funds stay under the Mutual Funds Act, tokenised private funds stay under the Private Funds Act, the tokens represent fund interests rather than separate virtual assets, and the issuance of those tokens is carved out of the VASP regime.
For sponsors, the obligations are concrete. Offering documents must disclose token-specific risks, including cybersecurity and transferability, and explain how they are mitigated. Operators must confirm to CIMA each year that records of issuance, sale, transfer, and ownership are properly kept, and transfers may proceed only with operator approval in line with the offering document. CIMA, as administrator of the regime, can inspect the underlying technology and the token transactions, restrict token characteristics, and require periodic reporting. The vehicles that launch cleanly will be the ones that design their token, transfer controls, and record architecture around these duties from the start.
Professional guidance adds the most value where the framework meets practical execution: choosing the right fund regime, drafting disclosure that is specific to your technology, aligning your administrator and providers with the record-keeping standard, and engaging CIMA with confidence. AURNE advises on Cayman fund and company formation and on structuring across jurisdictions, so the fund domicile, the management entity, and the wider group are designed to work together. Cayman has set a clear standard for tokenised funds; handled well, the framework is an opportunity to launch a tokenised strategy on credible, regulated footing.