EST · MMXXVI
Home/Services/Funds & Investment Vehicles/Tokenized Fund Share Classes: Structuring and Transfer Restrictions
Funds & Investment Vehicles

Tokenized Fund Share Classes: Structuring and Transfer Restrictions

Tokenized Fund Share Classes: Structuring and Transfer Restrictions. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-f

A fund manager decides to offer institutional allocators a token-denominated share class alongside traditional units – the allocator can settle in stablecoins, the fund's net asset value rolls up on-chain, and secondary liquidity opens for a narrow circle of qualified buyers. On paper, the efficiency gain is clear. In practice, the register of members, the transfer-restriction mechanism and the administrator's custody arrangements sit across three legal systems, and a misstep in any one of them jeopardises the entire vehicle's exemption from securities registration or its fund classification for tax. Tokenized fund share classes demand a simultaneous solution to corporate law, transfer control, investor-eligibility enforcement and administrator interoperability – not a blockchain proof-of-concept bolted onto an existing fund deed.

Under the applicable fund-vehicle frameworks – whether a Cayman exempted limited partnership, a Luxembourg SICAV or a BVI segregated-portfolio company – the governing instrument controls who may hold units, how transfers are recorded and what happens when a holder attempts an impermissible sale. A token representing beneficial ownership of a share class must enforce those same restrictions programmatically if the administrator is to recognise the on-chain record as the authoritative register. This page sets out the structural choices, the points of friction between on-chain mechanics and administrator workflows, and the drafting that bridges them. It is written for fund managers, allocators and administrators assessing whether to add a tokenized class to an existing vehicle or to launch a new vehicle with tokenization built in from inception.

Why tokenize a share class

A tokenized share class is a class of units in a pooled investment vehicle for which beneficial ownership is recorded on a distributed ledger and represented by a digital token, rather than recorded solely in the administrator's internal ledger. The token typically sits on a permissioned or public blockchain; the fund's constitutional documents – the limited-partnership agreement, articles of association or fund prospectus – are amended to recognise the on-chain record as the authoritative register for that class, subject to the administrator's overriding reconciliation obligation.

The business case turns on three capabilities. First, settlement efficiency: an allocator subscribing with stablecoins (USDC or USDT) delivers cash-equivalent value in minutes, avoiding the multi-day correspondent-banking delay that marks traditional fund subscriptions. Second, transparent net-asset-value distribution: the fund's NAV per token is calculated by the administrator and published on-chain at each valuation date, allowing holders and prospective secondary buyers to verify the price without an intermediary. Third, controlled secondary liquidity: the token smart contract can enforce investor-eligibility criteria (accreditation, AML clearance, jurisdiction whitelist) at the moment of transfer, so the manager permits secondary trading within a defined group without sacrificing the vehicle's private-placement or qualified-investor status.

In our cross-border practice, managers pursuing this structure typically fall into one of three profiles. Profile A is a digital-asset hedge fund or venture fund with a predominantly crypto-native investor base; the allocators expect to subscribe in stablecoins and value the transparency of an on-chain register. Profile B is a traditional fund adding a tokenized class to accommodate one or two large allocators who operate treasury on-chain and prefer not to convert back to fiat for each subscription. Profile C is a real-world-asset vehicle (a real-estate fund, a private-credit fund) issuing tokens to retail-accredited investors in a jurisdiction that permits fractionalised fund units; the token enables a secondary market among the eligible cohort while the fund itself remains closed-ended.

The cross-border reality is that the vehicle's domicile (the jurisdiction whose corporate and fund law governs the entity), the manager's base (and its regulatory licence), the blockchain on which the token lives, the administrator's location and the investors' tax residences will rarely align. A Cayman fund managed by a Malta MFSA-licensed AIFM, issuing tokens on Ethereum to US and EU investors, and administered by a Jersey trust company, creates five distinct legal touchpoints, each with its own register-of-members concept, its own securities-law private-placement rules and its own tax characterisation of the token. The structure succeeds only if every touchpoint is mapped and each delegation of authority – manager to administrator, administrator to smart contract, smart contract back to the manager for override – is documented in the governing instrument and operationalised in the workflows.

Where ownership lives: register of members and the administrator's role

The foundational question is which record is authoritative. Under Cayman, BVI, Jersey, Luxembourg and Maltese company law, the fund vehicle must maintain a register of members – a formal ledger identifying every holder, their holding and the date of acquisition. The administrator, acting as the fund's service provider, maintains that register and reconciles subscriptions, redemptions and transfers to it. When a share class is tokenized, the constitutional documents must state whether the on-chain record is the register of members or whether the administrator's internal ledger remains the register and the token is merely evidence of beneficial interest.

The cleanest approach is to designate the on-chain record as the authoritative register, provided the administrator retains an override right to correct errors and to freeze transfers in the event of a dispute. The fund's articles or limited-partnership agreement include a clause along these lines: "For Class T units, the register of members shall be the record of token holders maintained on [named blockchain or ledger identifier]. The Administrator may amend the on-chain record to reflect a court order, to correct a manifest error or to enforce a transfer restriction under this Agreement; any such amendment shall be effected by instructing the token smart contract or, if technical intervention is required, by deploying a registry update through the contract's administrative function." This drafting satisfies the corporate-law requirement (a defined register exists) and preserves the administrator's liability firewall (it can intervene if the on-chain record diverges from legal reality).

The administrator's operational checklist includes four elements. First, the administrator must be able to read the on-chain record in real time; this typically requires an API connection to a blockchain node or to a registry service that indexes the token contract. Second, the administrator reconciles the on-chain holding to its internal NAV calculation at each valuation date and flags any discrepancy. Third, the administrator issues a formal confirmation to each new subscriber once the token is minted to that subscriber's wallet address; this confirmation serves as the investor's evidence of holding for tax and audit purposes. Fourth, the administrator maintains a parallel off-chain register mapping wallet addresses to verified investor identities (the KYC record), because the blockchain address alone does not satisfy AML or tax-reporting obligations.

A common mistake is to treat the token as a side-channel notification system while leaving the administrator's ledger as the true register. This creates two registers and introduces a reconciliation failure mode: if an investor transfers the token on-chain but the administrator does not update its ledger, who is the member? The investor cannot vote, cannot redeem and may not receive distributions, because the administrator's systems do not recognise the new holder. The structure fails. The governing documents must be explicit: one register, with the administrator's role confined to NAV calculation, reconciliation and override authority for legal or compliance reasons.

Transfer restrictions and eligibility enforcement

A private fund's entire regulatory position – its exemption from public-offer rules, its qualification as an alternative investment fund or a private fund under the applicable regime, and its investors' ability to claim treaty benefits or capital-gains treatment – rests on investor eligibility. The constitutional documents state who may hold units (e.g. only qualified purchasers under US law, only professional investors under Hong Kong law, only EU professional investors under MiCA) and require the manager or administrator to verify eligibility before admitting a subscriber. When units are tokenized, these restrictions must be encoded in the token smart contract, or the on-chain transfer will bypass the gatekeeper and destroy the vehicle's exemption status.

The technical mechanism is a whitelist or eligibility registry maintained on-chain. Before a token may be transferred from wallet A to wallet B, the smart contract queries the registry: is B on the approved list? If yes, the transfer executes; if no, the transaction reverts. The registry itself is updated by the administrator or by a designated compliance officer whenever a new investor completes KYC and satisfies the eligibility criteria. The key drafting point is that the transfer restriction in the constitutional documents must explicitly incorporate the on-chain mechanism: "No Class T unit may be transferred to any person unless (a) the Administrator has verified that the transferee satisfies the eligibility criteria in Schedule X, and (b) the transferee's wallet address has been added to the on-chain eligibility registry maintained at [contract address]. Any purported transfer in breach of this restriction is void."

Operators we advise routinely implement a two-tier whitelist: a primary list of verified investors (managed by the administrator) and a secondary list of pre-approved transferees for emergency liquidity (a narrow circle of market-makers or other funds willing to acquire distressed positions). The secondary list allows a holder to exit on short notice without the administrator having to complete a full onboarding for the buyer, but it is capped (e.g. no more than 10 per cent of the class may be held by secondary-list entities at any time) to preserve the fund's private character.

The lock-up question is whether a time-based restriction (a one-year or two-year lock-up before any redemption or transfer is permitted) should be enforced on-chain or off-chain. An on-chain lock-up is technically straightforward – the token contract checks the holder's acquisition timestamp and reverts any transfer before the lock-up expires – but it creates an operational headache for the administrator if the manager wishes to grant an early-redemption exception (for example, in the event of investor hardship or to accommodate a fund restructuring). The administrator would need to call an administrative function on the smart contract to release the lock for that specific token holder, adding a manual step and a gas cost. The alternative is to enforce the lock-up through the administrator's redemption workflow: the token itself is freely transferable among whitelisted addresses, but the administrator will not process a redemption request until the lock-up has run. This shifts the control point from the blockchain to the administrator's systems and is the approach we see in most structures targeting institutional allocators.

Custody of the token and administrator interoperability

A tokenized share class introduces a custody question that does not exist for traditional fund units: who holds the private key to the wallet in which the investor's tokens sit? If the investor controls the key, the investor has unilateral ability to transfer the token (subject to the whitelist), which aligns with the decentralised ethos but creates a nightmare for the administrator if the investor loses the key or if the token is transferred in breach of the governing documents. If the administrator or a third-party custodian controls the key, the token becomes a custodial record like any other asset in the fund's structure, and the blockchain adds transparency but no self-sovereignty.

The choice turns on the investor profile and the fund's liquidity terms. For a closed-ended fund with a narrow circle of sophisticated allocators and no interim redemptions, investor-controlled wallets (non-custodial) are workable: each investor completes KYC, receives a token to their nominated Ethereum or Polygon address, and holds that token until the fund's liquidation date, at which point the administrator calculates the final NAV and instructs the token contract to burn the tokens and distribute the proceeds (in stablecoins or fiat, as elected). The administrator never touches the private key. The fund's constitutional documents require each investor to maintain adequate operational security over their wallet and to indemnify the fund for any loss resulting from a compromised key.

For an open-ended fund with quarterly or monthly redemptions, custodial wallets managed by the administrator or by a licensed digital-asset custodian are more practical. The investor does not receive a private key; instead, the custodian mints the token to a wallet it controls and maintains an internal ledger mapping the investor's identity to the token balance. The investor sees the token balance via a web portal and can request a redemption through the same interface, but cannot move the token on-chain without instructing the custodian. This model mirrors the traditional fund-administration workflow and allows the administrator to integrate the tokenized class into its existing NAV, reconciliation and AML systems with minimal change. The downside is that the token no longer offers the investor any benefit over a traditional unit – it is still a custodial record – though it does allow the fund to accept stablecoin subscriptions and to publish NAV on-chain for transparency.

We regularly advise managers launching with a hybrid: the token is issued to investor-controlled wallets, but redemptions must be processed through the administrator's portal, and the investor agrees not to transfer the token to any address outside the whitelist without prior written consent. This preserves some self-custody benefit while giving the administrator a compliance checkpoint. The governing documents include a "lost-key" procedure: if an investor loses access to their wallet, the administrator may, upon receiving satisfactory proof of identity and a statutory declaration, mint replacement tokens to a new wallet and burn the old tokens, updating the on-chain register accordingly.

Domicile choice and the tax stack

The wrong domicile locks in tax leakage and limits which investors you can accept. A fund investing in digital assets – whether liquid tokens, staking rewards or DeFi protocol positions – generates income and gains that may be characterised as interest, dividends, trading profits or capital appreciation, depending on the strategy and the domicile's tax law. The vehicle must be structured so that the fund itself pays no entity-level tax (or minimal tax) and so that investors receive distributions in a form that qualifies for treaty relief or capital-gains treatment in their home jurisdictions.

The flagship domiciles for digital-asset funds are Cayman Islands (exempted companies and exempted limited partnerships), BVI (companies and limited partnerships under the VASP Act framework), Luxembourg (SICAV and specialised investment funds) and Malta (under the MFSA VFA framework, transitioning to MiCA). Each offers tax neutrality at the fund level: the vehicle pays no income tax, capital-gains tax or withholding tax on distributions to non-resident investors. The manager's choice among them turns on three factors: the regulatory treatment of the manager (whether the manager needs a fund-management licence and where it sits), the investor base (EU professional investors favour Luxembourg; US qualified purchasers favour Cayman), and the administrator's location (Jersey and Cayman administrators dominate the offshore market; Luxembourg administrators are required if the fund is a Luxembourg-domiciled AIFMD vehicle).

For a tokenized share class specifically, the domicile must recognise digital assets as property and must not impose stamp duty, transfer tax or securities-transaction tax on the issuance or transfer of the token. Cayman, BVI and Malta satisfy this. Luxembourg does not have specific tokenized-share-class precedent in its fund law, but a SICAV issuing dematerialised shares can characterise the token as evidence of the dematerialised share, avoiding a separate asset classification. A common mistake is to incorporate the vehicle in a low-tax jurisdiction without checking whether that jurisdiction's AML regime permits the administrator to onboard investors who subscribe in stablecoins; some offshore administrators will not accept crypto subscriptions unless the investor also maintains a fiat bank account in good standing, which defeats the structure's purpose.

The investor's tax position depends on whether the token is classified as a security, a unit in a collective-investment scheme, or something else in the investor's home jurisdiction. For a US taxable investor, a tokenized share in a Cayman fund is still a partnership interest or a share in a foreign corporation (depending on the vehicle type) and is taxed as such – the token is merely the evidence of ownership and does not change the character. For an EU professional investor in a Luxembourg SICAV, the token is an undertaking-for-collective-investment (UCI) unit, and gains on redemption are taxed as capital or as income depending on the investor's member-state rules. The fund's offering documents must include a tax disclosure for each major investor jurisdiction, and that disclosure must address the token specifically (whether its transfer triggers a taxable disposition, whether the blockchain record suffices for tax reporting, and whether the investor must report the wallet address on their foreign-asset returns).

Decision matrix: new vehicle vs. additional share class

A manager considering tokenization faces a structural choice: add a tokenized class to an existing fund, or launch a new vehicle with tokenization as the sole share class. The decision turns on the existing vehicle's constitutional documents, the administrator's willingness to support a hybrid structure, and the expected size of the tokenized-class investor base. Profile A: an existing Cayman fund with six traditional investors and one large crypto-native allocator willing to anchor a $20 million subscription. The path is to amend the fund's limited-partnership agreement to add Class T, designate the on-chain record as the register for that class only, and instruct the administrator to reconcile the token contract at each NAV date. Timeline: agreement amendment (two weeks for legal drafting and LP consent), token contract deployment (one week for development and audit), administrator onboarding (four weeks to integrate the API and update the NAV workflow). Key risk: if the amendment materially alters the fund's investment restrictions or redemption terms, the existing LPs may have a consent right, and one objection can stall the process.

Profile B: a manager launching a crypto-focused venture fund targeting 30 to 50 allocators, predominantly family offices and funds-of-funds already operating treasury on-chain. The path is to incorporate a new vehicle with tokenization as the sole structure from day one: the limited-partnership agreement designates the on-chain register as the authoritative ledger, every subscription is in USDC, and the administrator's systems are built around the token contract. Timeline: vehicle formation (Cayman LP, two weeks), regulatory pre-clearance if the manager is MiCA-licensed (four to six weeks), token contract deployment (two weeks including audit), administrator engagement (six to eight weeks to configure NAV, reconciliation and reporting for a tokenized-only vehicle). Key risk: fewer administrators have live experience with tokenized-only vehicles, and the manager may need to pay a higher fee or accept a longer setup period.

A middle path is a master-feeder structure: the master fund (Cayman) holds the assets and calculates a single NAV; two feeder funds (one traditional, one tokenized) invest 100 per cent into the master and issue their own units to investors. The traditional feeder operates like any Cayman feeder; the tokenized feeder issues tokens representing its units. This segregates the operational complexity – the master fund's administrator never touches the token contract – and allows the manager to pilot tokenization with a subset of investors without affecting the traditional investor base. The downside is the added layer of fees (two administrator engagements, two sets of audit and legal fees) and the dilution of the tokenized pool if it remains small.

Administrator and auditor selection

Not every fund administrator is equipped to handle a tokenized share class. The administrator must be able to query the blockchain in real time, to verify that the on-chain holder list matches its KYC records, and to issue redemption proceeds to a wallet or to a fiat account as the investor elects. A traditional Cayman administrator operating on legacy client-server software may lack the API infrastructure or the compliance appetite for this workflow. In our cross-border practice, managers launching tokenized classes typically engage one of a handful of administrators that have invested in blockchain-integration capabilities: these firms maintain Ethereum and Polygon nodes, have built reconciliation dashboards that pull on-chain data directly and employ developers who can troubleshoot smart-contract interactions.

The selection criteria include: proven experience with at least one tokenized fund (ask for a reference); a documented process for adding wallet addresses to the whitelist and for processing redemptions in stablecoins; and a willingness to sign off on the on-chain record as the authoritative register in the NAV report and in the audited financial statements. The administrator's fee for a tokenized class is typically 10 to 20 per cent higher than the standard rate, reflecting the additional technical and compliance work.

The auditor (Big Four or a specialist fund-auditor firm) must be satisfied that the on-chain record is auditable and that the controls around minting, burning and transfer restrictions are sufficient to prevent unauthorised dilution or withdrawal. This means the token smart contract must be open-source (or the auditor must receive the verified source code), the contract must have been audited by a reputable blockchain-security firm and the administrator must demonstrate that it has tested the reconciliation process against a test transaction set. Auditors increasingly expect to see the smart-contract audit report as part of the fund's control documentation, and some will engage their own blockchain specialist to verify the contract's logic before signing the financial statements.

Common mistakes include deploying an unaudited token contract (an automatic red flag for any institutional allocator), failing to document the administrator's override authority in both the constitutional documents and the smart contract (leaving no mechanism to correct an erroneous transfer) and neglecting to test the redemption flow with the stablecoin issuer (USDC redemptions require the fund to hold a Circle account; USDT redemptions require the administrator to have a relationship with Tether or to route through an exchange, which adds a settlement step and a timing risk). These are identified in a structured review before the first subscription, not after capital is committed.

Investor eligibility and KYC workflow

The subscription process for a tokenized share class runs in parallel with the traditional process until the moment of capital delivery. The investor completes the fund's subscription agreement, provides KYC documentation (proof of accreditation, source-of-funds declaration, beneficial-ownership certification) and satisfies any jurisdiction-specific requirements (for a US investor, the qualified-purchaser representation; for an EU professional investor, the MiFID opt-up documentation). The administrator reviews the documents, verifies the investor's identity against sanctions lists and adverse-media databases, and confirms that the investor meets the eligibility criteria in the fund's constitutional documents.

Once cleared, the administrator adds the investor's wallet address to the on-chain eligibility registry. The investor then initiates the subscription by transferring USDC or USDT to the fund's designated wallet address (a multi-signature wallet controlled by the administrator and the manager, or a single-signature wallet controlled by the administrator with the manager as a read-only observer). The administrator monitors the blockchain for the incoming transaction; upon confirmation (typically six blocks on Ethereum, faster on Polygon), the administrator mints the corresponding number of Class T tokens to the investor's wallet address and records the subscription in the fund's register. The investor receives an email confirmation with the transaction hash, the token contract address, the number of tokens minted and the NAV per token at the subscription date.

This workflow assumes the investor already operates a wallet and holds stablecoins. If the investor is new to on-chain operations, the administrator or the manager may offer a white-glove onboarding: the administrator provisions a custodial wallet, the investor wires fiat to the administrator's bank account, and the administrator purchases stablecoins on the investor's behalf and mints the tokens. This adds one to two business days and a conversion fee (typically 25 to 50 basis points), but it eliminates the investor's need to touch a private key. For a first-time tokenized subscription, this is the recommended path for a traditional family office or institutional allocator unfamiliar with wallet mechanics.

Redemption mechanics and liquidity windows

Redemption is the point of maximum operational friction in a tokenized structure. The investor submits a redemption request (typically via the administrator's portal or by email), the administrator calculates the redemption proceeds based on the NAV at the next valuation date, and the fund must deliver those proceeds either in stablecoins (to the investor's wallet) or in fiat (to the investor's bank account). If the investor elects stablecoins, the administrator burns the investor's tokens (calling the token contract's burn function) and transfers USDC from the fund's treasury wallet to the investor's wallet on the same day. If the investor elects fiat, the administrator burns the tokens, liquidates the corresponding NAV in stablecoins to fiat through an exchange or OTC desk, and initiates a wire transfer to the investor's account; this adds two to five business days depending on correspondent-banking routes.

The fund's constitutional documents must specify the default redemption currency and the notice period for electing the alternative. A typical clause: "Redemption proceeds shall be paid in USDC unless the redeeming investor notifies the Administrator in writing at least five business days before the redemption date that proceeds should be paid in USD via wire transfer. The Administrator shall burn the corresponding Class T tokens upon calculating the final redemption amount." This gives the administrator time to arrange the fiat conversion and to confirm the investor's bank details.

A liquidity mismatch arises if the fund's assets – venture positions, illiquid tokens, staking deposits – cannot be converted to stablecoins quickly enough to meet a large redemption. The standard protective mechanism is a gate: the fund's constitutional documents permit the manager to defer redemptions in excess of a threshold (e.g. 25 per cent of the class's NAV in any quarter) to the next valuation date, or to satisfy redemptions in kind by transferring a proportionate share of the fund's underlying assets to the redeeming investor. For a tokenized class, in-kind redemption means the administrator transfers the investor's pro-rata share of the fund's token holdings (Bitcoin, Ether, staked positions) to the investor's wallet and burns the Class T tokens. This preserves liquidity for the remaining holders but requires the investor to manage the custody and tax reporting of the distributed assets.

For a scoped assessment of your fund's domicile, administrator stack and tokenization readiness, contact OBOLUS at info@oboluslaw.com. We map the eligibility rules, the redemption mechanics and the custody flow before you commit capital to a structure that may not support the investor base you need.

When something goes wrong: dispute resolution and forced transfers

A tokenized share class introduces new failure modes: an investor's wallet is compromised and the tokens are transferred to an attacker; a token holder dies and the estate cannot locate the private key; a court issues a charging order against a limited partner and instructs the fund to transfer that partner's units to a judgment creditor. The traditional mechanisms – a register maintained by the administrator and a clause permitting the administrator to amend the register upon receiving a court order – still apply, but they must be operationalised on-chain.

The token smart contract should include an administrative override function that allows the administrator (or a designated contract administrator) to transfer tokens from one address to another without the holder's signature, and to burn tokens and mint replacement tokens if a wallet is lost. The fund's constitutional documents must explicitly grant this authority: "In the event of a court order, a manifest error, or upon receiving satisfactory evidence that a token holder has lost access to their wallet, the Administrator may instruct the token contract to transfer, burn or mint Class T tokens as necessary to reflect the legal position. Any person acquiring an interest in Class T tokens acknowledges that the token contract includes an administrative override function and agrees that the Administrator's exercise of that function in accordance with this Agreement is binding." This drafting ensures that the override is not a unilateral power but is tied to a legal or factual predicate.

A forced transfer triggered by a court order follows this process: the manager receives the court order (for example, an English-law worldwide freezing order instructing the fund to freeze and then transfer the defendant's units to the claimant upon judgment); the manager forwards the order to the administrator; the administrator verifies the order's authenticity and scope with its legal counsel; the administrator calls the smart contract's administrative transfer function, moving the tokens from the defendant's wallet address to the claimant's nominated address (which must be on the whitelist); and the administrator updates its internal register and notifies both parties. The blockchain transaction is public and timestamped, providing an auditable record of the forced transfer that satisfies the court's reporting requirements.

FAQ

Where should this fund be domiciled?

Domicile choice for a tokenized fund turns on the investor base, the regulatory status of the manager and the administrator's jurisdiction. Cayman Islands and BVI offer tax neutrality, no entity-level tax and established administrator infrastructure for digital-asset vehicles; they are the default for US and Asian allocators. Luxembourg SICAV or specialised investment funds suit EU professional investors and are required if the manager is MiCA-licensed or AIFMD-registered and passporting. Malta works for smaller vehicles targeting EU retail-qualified investors under MiCA's prospectus route. The domicile must recognise digital assets as property and must not impose stamp duty or transfer tax on token issuance. In every case, the governing documents must explicitly permit the on-chain register.

Does the manager need a licence?

Whether the manager of a tokenized fund requires a regulatory licence depends on the manager's location, the fund's classification and the investor base. A Cayman or BVI fund with exclusively non-local investors and managed from outside those jurisdictions typically does not require the manager to hold a fund-management licence in the fund's domicile, though the manager's home jurisdiction may require registration. An EU-based manager operating a MiCA CASP or an AIFMD firm managing a fund that markets to EU professional investors must hold the relevant authorisation. A US manager relying on private-fund exemptions under the Investment Advisers Act must still register as an RIA if assets under management exceed the threshold. The tokenization itself does not create a new licence requirement, but it may affect the characterisation of the vehicle or the offering as a securities product in certain jurisdictions.

How is custody arranged for this vehicle?

Custody in a tokenized fund structure has two layers: custody of the fund's assets (the portfolio holdings – tokens, staking positions, DeFi protocol claims) and custody of the investor's share tokens. The fund's assets are held by the fund itself in wallets controlled by the administrator or by a licensed digital-asset custodian engaged by the fund; the constitutional documents specify who holds the keys and under what signing authority. The investor's share token may be held in the investor's self-custody wallet (non-custodial) or in a wallet controlled by the administrator or a third-party custodian (custodial). Non-custodial is cleaner for closed-ended vehicles with sophisticated investors; custodial is more practical for open-ended vehicles with frequent redemptions. The choice is documented in the subscription agreement, and the administrator reconciles whichever model applies to the on-chain register at each NAV date.

About OBOLUS

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We match domicile to investor base, asset mix and redemption profile – not to a house view or a legacy client list. For fund vehicles, we draft the constitutional documents, map the administrator's workflow to the smart contract, and pressure-test the structure against the AML, tax and prospectus rules in every investor jurisdiction you target. To discuss your situation, contact info@oboluslaw.com.

By Lydia Brennan, Tax & Structuring Analyst – specialising in fund-vehicle structuring, cross-border tax optimisation and digital-asset holding structures across offshore and EU domiciles.

Related at OBOLUS

This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours