EST · MMXXVI
Home/Services/Funds & Investment Vehicles/Tokenized Treasury Products: Issuance and Fund Structuring
Funds & Investment Vehicles

Tokenized Treasury Products: Issuance and Fund Structuring

Tokenized Treasury Products: Issuance and Fund Structuring. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engage

A fund manager planning to launch a tokenized money-market product – shares redeemable on-chain, backed by short-duration government securities – discovers that the legal stack depends on three decisions made in sequence: where the vehicle sits, which investors it accepts, and how tokens move between wallets without breaking transfer restrictions. The regime governing issuance, the custody chain for the underlying securities, and the method by which net asset value is struck and published all turn on that first domicile choice. A mismatch between the fund's legal home and the profile of its investor base creates tax leakage, locks out entire categories of capital, and exposes the manager to parallel licensing in multiple markets.

This page sets out the legal framework for structuring a tokenized treasury product as an investment vehicle. It addresses vehicle choice, eligible-investor rules, transfer restrictions that survive on-chain movement, custody arrangements for the underlying government securities, and the mechanics by which tokens are issued, priced and redeemed. The analysis applies whether the product targets institutional allocators, family offices or, subject to local private-placement limits, qualified retail. Digital assets are the whole of our practice at OBOLUS, and we act only for businesses; we advise fund managers, token issuers and custodians on the licensing, tax and compliance stack across more than 70 jurisdictions.

What activity triggers a fund-manager licence

Issuing tokens backed by a pool of government securities is fund management in every flagship regime if the token confers a proportionate claim on the pool and the issuer exercises discretion over which securities to buy. The activity falls under the collective-investment-scheme rules in common-law markets, the UCITS/AIFMD perimeter in the EU, and equivalent fund-regulation frameworks in Singapore, Hong Kong, Switzerland and the UAE financial free zones. A pure custody arrangement – where the holder directs every purchase and the custodian executes without discretion – escapes fund regulation, but the moment the vehicle aggregates investor capital and the manager selects the securities, a licence or exemption is required.

The regime depends on where the manager sits, not where the vehicle is domiciled. A Cayman fund managed from London triggers FCA authorisation; a BVI fund managed from Abu Dhabi (ADGM) requires FSRA approval. Most managers structure around this by placing the vehicle in a fund-friendly domicile and either establishing the management company in a hub with a proportionate regime (the UAE free zones, Singapore, Switzerland) or relying on a private-placement exemption where one exists. The MiCA framework does not directly regulate investment funds, but an EU manager operating an alternative investment fund must comply with AIFMD; a non-EU manager marketing into the EU faces national private-placement rules until the fund qualifies under a registration pathway.

Tokenization does not create a separate regulatory category. The question remains: does the structure constitute collective investment, and is the manager conducting a regulated activity? If the answer is yes, the token element changes the compliance burden – transfer restrictions must be encoded or enforced at the wallet level, KYC must run before every secondary transfer, and the token contract itself becomes part of the offering documentation – but it does not remove the need for a fund-manager authorization or an applicable exemption.

Navigating the multi-jurisdiction fund stack – where the manager, the vehicle and the investors each sit in different markets – requires matching the domicile to the investor base and the redemption model before the token contract is written. To map the licensing, tax and compliance position for your product, contact OBOLUS at info@oboluslaw.com.

Vehicle choice and domicile

The vehicle must accommodate tokenized shares, permit daily or intra-day redemptions, and impose no withholding tax on distributions to non-resident investors. The leading structures are an exempted mutual fund or segregated-portfolio company (SPC) in Cayman or BVI, a corporate subfund within a Luxembourg or Irish ICAV, or a variable capital company (VCC) in Singapore. Each supports tokenization, but the mechanics differ. In Cayman and BVI, the register of members can be maintained on-chain or mirrored by a licensed administrator; in Luxembourg and Ireland, the transfer agent reconciles the token ledger to the statutory register daily; in Singapore, the VCC framework explicitly permits distributed-ledger share registers.

Domicile choice turns on three factors: the profile of the target investors, the manager's location, and the need for a regulatory label that institutional allocators recognize. A Cayman exempted fund is the default for a non-EU manager raising from family offices, endowments and sovereign wealth allocators across Asia, the Middle East and the Americas. A Luxembourg RAIF (reserved alternative investment fund) suits an EU-based manager that plans to scale into AIFMD compliance and wants the passport. A Singapore VCC works for a regional manager targeting institutional capital across APAC and seeking co-location with MAS-licensed service providers. BVI offers speed and lower setup cost, but fewer allocators hold BVI funds compared to Cayman or Luxembourg.

Tax neutrality is mandatory. The vehicle must not impose withholding on interest or dividend distributions and must not create a taxable presence in the investors' home markets. Cayman, BVI, Luxembourg (under the right structure) and Ireland (for qualifying funds) deliver this. A US-domiciled vehicle works only if every investor is US-taxable and comfortable with the resulting reporting; otherwise the offshore route is cleaner. The wrong domicile locks in tax leakage and limits which investors the fund can accept – re-domiciling a launched vehicle is expensive and often impractical.

Eligible investors and private-placement limits

Most tokenized treasury products are structured as private placements to avoid the cost and timeline of a public prospectus. The trade-off is a restriction on the number and type of investors the fund may accept. In Cayman, an exempted mutual fund may accept an unlimited number of investors but must file a prospectus with CIMA unless it restricts subscriptions to sophisticated investors under the exemption provisions. In BVI, a professional fund may accept only professional investors; an approved fund may accept up to 50 investors; an incubator fund has a short time window before it must upgrade. Luxembourg's RAIF may rely on AIFMD marketing exemptions if the manager is authorized, but every investor must meet the professional-client or equivalent threshold under MiFID.

Singapore's VCC framework permits retail investors only if the manager holds a capital-markets-services licence for retail collective-investment schemes; otherwise the fund is restricted to accredited and institutional investors. In the UAE financial free zones (ADGM and DIFC), a fund marketed to qualified investors does not require a public prospectus, but the definition of "qualified" is narrower than Cayman's sophisticated-investor concept. Crossing into a retail investor base – even a qualified-retail segment – multiplies the compliance burden: detailed disclosures, suitability assessments, ombudsman arrangements, and, in the EU, the entire UCITS or retail-AIFMD framework.

The token element creates a second layer. If tokens trade on a secondary market, the fund must either encode transfer restrictions in the smart contract (a whitelist controlled by the administrator) or maintain continuous KYC on every wallet holding the token. A fully open token that any address can hold converts the vehicle into a public offering in every market where holders reside, triggering prospectus and marketing rules the manager never intended to meet. In our cross-border practice, we see managers assume that blockchain-native distribution solves regulatory friction; in reality it multiplies the jurisdictional exposure unless transfer restrictions are designed into the contract from launch.

Transfer restrictions and on-chain compliance

A tokenized fund share must carry the same transfer restrictions as a traditional share in that vehicle. If the fund is limited to accredited investors, the token contract must prevent a transfer to a non-accredited wallet. The two mechanisms are a whitelist (only pre-approved addresses may hold the token) and a blacklist (flagged addresses are blocked). A whitelist is stronger and aligns with the regulatory expectation in every major regime: the administrator or transfer agent approves each wallet after KYC, and the contract reverts any transfer to an address not on the list. The administrator updates the whitelist as new investors subscribe and old investors redeem.

Blacklists work for sanctions screening and for blocking wallets flagged in a recovery or fraud matter, but they do not enforce the eligible-investor rule – they only prevent transfers to known-bad addresses. A blacklist alone does not stop an accredited investor from transferring to a non-accredited friend; a whitelist does. Some managers layer both: a whitelist for the base eligible-investor rule, and a sanctions-screening blacklist that blocks OFAC-designated addresses and addresses linked to mixers or sanctioned protocols. The compliance logic sits in the token contract, typically as a modifier on the transfer function that queries an on-chain or off-chain registry before allowing the transfer to execute.

The practical difficulty is maintaining the whitelist as investors change wallets. The administrator must support wallet updates without triggering a full re-subscription, and the contract must handle the case where an investor consolidates multiple wallets or rotates to a new address for operational security. Some structures use role-based tokens (the investor's KYC is tied to a controller key, and the token respects a delegation mechanism) rather than address-based whitelisting. The goal is the same: the token cannot move to a wallet that has not met the fund's investor-eligibility standard.

Custody chain for underlying securities

The fund holds government securities – short-duration Treasuries, sovereign bonds, or equivalent instruments – in custody at a bank or broker-dealer, and the tokenized shares represent a proportionate claim on that pool. The custody arrangement must segregate the fund's assets from the custodian's own assets, comply with the applicable safe-custody rules in the fund's domicile, and allow the administrator to verify holdings for NAV calculation. In Cayman, the custodian must meet the requirements of the Mutual Funds Act for a licensed or approved custodian; in Luxembourg, AIFMD mandates a depositary with specific oversight duties; in BVI, the custody rules vary by fund type but generally require a custodian regulated in a recognized jurisdiction.

The tokenization layer does not change the custody requirement for the underlying securities, but it adds a second custody question: who holds the private keys for the token contract, and who controls the admin functions (minting, burning, whitelist updates)? The safest model is a multi-signature or threshold-signature wallet controlled jointly by the manager, the administrator and an independent director or custodian. Single-key control by the manager creates operational and fraud risk; a compromised key can mint unlimited tokens or alter the whitelist. Some structures use a time-locked upgrade mechanism (the contract allows admin changes only after a notice period, giving investors a window to exit if they disagree with a proposed change). The custody arrangements for the fund assets and the custody of the contract admin keys are separate but equally critical to the structure's integrity.

In a recent structuring matter, a fund manager launching a tokenized short-duration bond fund initially planned to hold the contract admin key unilaterally. We mapped the risk: a single compromised laptop could destroy the vehicle's credibility. We restructured the admin control into a 2-of-3 multisig (manager, administrator, independent director) with a 48-hour time lock on whitelist and parameter changes. The manager retained operational flexibility; the investors gained a layer of protection institutional allocators expect.

Net asset value is calculated by the administrator at a frequency set in the offering documents – daily for most money-market products, intra-day for some institutional vehicles. The administrator values the underlying securities using a recognized pricing source (typically Bloomberg or a similar service for government bonds), subtracts liabilities (management fees, operational expenses), and divides by the number of shares outstanding. That per-share NAV is published and used for subscriptions and redemptions. For a tokenized vehicle, the NAV must also be made available on-chain or in a format that wallet interfaces and DeFi protocols can read, typically by publishing the NAV to an oracle or a public API that decentralized applications can query.

The token contract itself does not calculate NAV – it mints and burns tokens at the NAV the administrator publishes. The process is: investor subscribes → administrator completes KYC and approves the wallet → investor transfers cash (stablecoin or fiat wire) to the subscription account → administrator calculates the number of tokens due at the current NAV → the contract mints that quantity of tokens to the investor's whitelisted wallet. Redemptions reverse the flow: investor requests redemption → the contract burns the tokens → administrator transfers the redemption proceeds (NAV per token × quantity burned) to the investor's account. The administrator reconciles the on-chain token supply to the statutory register of members at least daily, and the register is the legal record.

Pricing lag is a risk. If NAV is calculated once daily but tokens are issued or redeemed intra-day, the investor may receive a price that is stale by several hours. Some products solve this with an intra-day NAV strike (the administrator calculates NAV every hour or on demand) or by batching subscriptions and redemptions at a single daily cutoff. The choice depends on the investor base: institutional allocators doing large subscriptions and redemptions care about the lag; smaller holders typically accept a daily NAV. A mid-sized tokenized treasury product we advised struck NAV four times daily (market open, midday, market close, end of business day in Asia) to accommodate allocators in multiple time zones; the complexity was manageable because the underlying portfolio was government securities with transparent real-time pricing.

Compliance and reporting

The fund must comply with AML obligations at the vehicle level (Cayman, BVI, Luxembourg all impose AML on fund administrators) and, if tokens are considered a virtual asset in the relevant jurisdiction, potentially at the token level as well. The administrator conducts KYC on every investor before adding the wallet to the whitelist, monitors transactions for suspicious activity, and files reports with the local financial intelligence unit if required. Transfer restrictions are part of the AML control: an investor cannot evade KYC by transferring the token to a different wallet, because the recipient wallet must also be whitelisted after KYC.

Reporting to investors follows the fund's standard cycle – quarterly or annual audited financials, periodic NAV statements – plus any on-chain transparency the manager chooses to provide. Some structures publish anonymized portfolio composition on-chain (the percentage allocation to each maturity bucket or issuer category) so that holders can verify the fund is performing as described; others keep portfolio detail private and rely on the audited financials. Tax reporting is the same as for a traditional fund: K-1s for US investors, local tax certificates for others, and any jurisdiction-specific information returns the fund is required to file.

The compliance burden for a tokenized fund is the fund's base compliance plus the on-chain enforcement layer. A common assumption is that on-chain operation reduces the administrator's workload. In reality, the administrator must reconcile two ledgers (the statutory register and the token contract), monitor for unauthorized transfers that slip past the whitelist (a contract bug or a compromised admin key), and maintain the whitelist as investors rotate wallets. If the fund accepts stablecoin subscriptions, the administrator must also track stablecoin receipts, convert them to fiat for deployment into the underlying securities, and handle the reverse on redemptions. Every added feature – intra-day NAV, stablecoin denomination, cross-chain bridging – compounds the operational and compliance load. The structure works, but the cost and the administrator's capability must match the complexity.

Common structuring mistakes

Three mistakes recur in tokenized-fund launches. The first is choosing a domicile based on incorporation speed without mapping investor eligibility. A BVI professional fund is fast and cheap to set up, but it cannot accept non-professional investors; if the manager later wants to expand into a broader qualified-retail base, the vehicle must be re-domiciled or a parallel fund established. The second mistake is launching with no transfer restrictions and discovering mid-cycle that tokens have moved to wallets the fund never KYC'd, creating an inadvertent public offering. The third is underestimating the administrator's role: the manager assumes a blockchain-native fund needs minimal administration, but the reconciliation, NAV-publishing, and whitelist-management workload is higher than for a traditional vehicle. The administrator's fee reflects this, and not every administrator has the systems to support on-chain reconciliation at scale.

Two structural traps appear in the custody stack. One is commingling the fund's fiat or stablecoin subscription proceeds with the manager's own operational accounts before deployment into securities; this pierces segregation and exposes the fund's assets to the manager's creditors. Subscription proceeds must flow directly to an account in the fund's name at a regulated custodian, and only the administrator or an independent director should have signatory authority. The other trap is holding the private key to the token contract's admin functions in a single non-custodial wallet without a recovery mechanism. If the manager loses that key, the whitelist cannot be updated, new tokens cannot be minted, and the vehicle is effectively frozen. Multi-signature control and a documented key-recovery protocol are not optional.

Structuring pathways by manager profile

A licensed EU fund manager targeting institutional allocators across Europe typically structures a Luxembourg RAIF or Irish QIF with on-chain share tokens, relies on the AIFMD passport for cross-border marketing, appoints a depositary and an EU-based administrator, and encodes KYC transfer restrictions in the token contract. Indicative setup time is typically a matter of months, and the ongoing compliance is the full AIFMD reporting and risk-management stack. This route delivers the regulatory label large allocators require and supports scaling into a UCITS-compliant retail vehicle if the manager later pivots to a broader investor base.

A non-EU manager raising from family offices and UHNW investors across Asia, the Middle East and North America typically structures a Cayman exempted mutual fund under the sophisticated-investor exemption, appoints a Cayman-licensed administrator and a custodian in a recognized jurisdiction (often a US or Singapore bank), and uses a whitelist-enforced token with wallet-level KYC. The vehicle avoids AIFMD compliance, files a light regulatory notice with CIMA, and accepts an unlimited number of investors provided they meet the sophistication standard. Indicative setup is a matter of weeks after engagement, and ongoing compliance is administrator-managed annual filings and audited financials.

A regional manager in Singapore licensed under MAS for accredited-investor funds typically structures a VCC, which permits distributed-ledger share registers under Singapore's VCC framework, appoints a Singapore fund administrator and custodian, and markets to accredited and institutional investors across APAC. The VCC can later upgrade into a retail-licensed structure if the manager obtains the additional CMS licence. This route offers MAS-supervised credibility and co-location with the region's digital-asset infrastructure.

A manager without a fund-management licence piloting a product typically structures a private fund in Cayman or BVI under a tight investor cap (under 15 in Cayman if relying on certain exemptions, or under 50 in BVI under the approved-fund route), manages the vehicle as general partner or investment manager under an advisory exemption, and runs the pilot for a fixed term (typically six to twelve months). If the pilot succeeds and the manager wants to scale, the vehicle transitions to a licensed-manager structure or the manager applies for the relevant authorisation. This route defers the licensing cost but limits the investor base; it works for proof-of-concept with strategic allocators but not for an institutional roll-out.

When to engage counsel

Engage before the token contract is finalized. The offering documents, the token contract and the custody arrangements are interdependent: the contract must enforce the restrictions stated in the subscription agreement, the administrator must be able to update the whitelist as new investors are approved, and the custody chain for the underlying securities must meet the domicile's safe-custody rules. Finalizing the contract first and fitting the legal structure around it is backward and typically results in either a contract rewrite or a mismatch between what the documents say and what the code enforces.

The right sequence is: domicile and vehicle choice → offering-document draft → token-contract functional spec → parallel finalization of the legal documents and the contract (with the lawyer, the contract auditor and the administrator all reviewing together) → whitelist and admin-key custody setup → launch. A short initial strategy call under NDA surfaces whether the manager's planned structure will work for the target investor base and the redemption model, and whether the chosen administrator can support the on-chain reconciliation load. OBOLUS advises fund managers, token issuers and custodians on the full stack – licensing, domicile choice, tax structuring, the compliance build – across more than 70 jurisdictions. For a scoped assessment of the legal position for your tokenized treasury product, contact us at info@oboluslaw.com.

Related at OBOLUS

FAQ

Where should this fund be domiciled?

Domicile turns on the profile of your target investors and the manager's location. Cayman works for a non-EU manager raising from family offices and institutions across Asia, the Middle East and the Americas. Luxembourg or Ireland suits an EU-based manager planning AIFMD compliance and cross-border marketing under the passport. Singapore's VCC framework works for a regional manager targeting institutional capital across APAC. Each delivers tax neutrality and supports tokenized shares, but the investor-eligibility rules and the compliance burden differ. The wrong choice locks in tax leakage and restricts which allocators you can accept.

Does the manager need a licence?

Managing an investment vehicle triggers a fund-management licence or exemption in every major regime. The requirement depends on where the manager sits, not where the vehicle is domiciled. A Cayman fund managed from London requires FCA authorisation; a BVI fund managed from Singapore requires a capital-markets-services licence unless the manager relies on an exemption. Many managers structure around this by placing the vehicle in a fund-friendly domicile and either establishing the management company in a proportionate hub or relying on a private-placement exemption where available. Tokenization does not create a carve-out from fund regulation.

How is custody arranged for this vehicle?

The fund holds the underlying government securities in custody at a bank or broker-dealer regulated in a recognized jurisdiction, and the custodian must meet the safe-custody rules in the fund's domicile. The tokenized shares are a claim on that pool. The second custody question is who controls the admin functions on the token contract (minting, burning, whitelist updates). The safest structure is multi-signature control by the manager, the administrator and an independent director. Single-key control by the manager creates fraud risk; a compromised key can mint unlimited tokens or alter the whitelist without oversight.

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 fund domicile to investor base, asset mix and redemption profile, and we work with managers from the first engagement call through launch and into the operational cycle. To discuss your tokenized treasury product, contact info@oboluslaw.com.

By Lydia Brennan, Tax & Structuring Analyst – advising fund managers and token issuers on cross-border vehicle structuring, domicile choice and the tax interface for digital-asset products.

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