A manager assembling a tokenized private-credit fund discovers that the subscription mechanics, the servicing waterfall and the default documentation all diverge from the equity-fund playbook – yet the first pitch deck already shows a domicile and a feeder cascade chosen for the prior generation of funds. The legal question turns on whether the structure actually supports the credit economics, the on-chain settlement rails and the investor base you need to attract. Misalignment here surfaces as tax leakage, stranded capital in the feeder tier or an unworkable custody chain that stops distributions mid-cycle.
Tokenized private credit combines an illiquid underlying portfolio – loans to operating businesses, invoice finance, asset-backed receivables – with a digital-asset wrapper that promises faster settlement, fractional exposure and potentially secondary liquidity. The legal architecture must answer three pressures simultaneously: the originator's need to ring-fence risk and maintain servicing control, the investor's regulatory and tax constraints, and the on-chain infrastructure's custody, disclosure and redemption mechanics. The wrong fund domicile or feeder design creates irrecoverable tax drag, conflicts with the originator's credit agreements or locks out institutional allocators who cannot hold tokens directly. OBOLUS structures tokenized private-credit vehicles from the credit economics up, matching the fund domicile, the feeder cascade, the token terms and the custody stack to the business model you are building and the capital you intend to raise.
This page describes the structuring choices that define a tokenized private-credit fund, the originator and servicing arrangements that protect the credit portfolio, the feeder design that accommodates different investor classes, and the on-chain and legal documentation that governs distributions, defaults and redemptions.
What is tokenized private credit and why does it require different fund structuring?
Tokenized private credit is a fund or special-purpose vehicle that holds a portfolio of loans, receivables or other credit instruments and issues digital tokens representing fractional economic interests in that portfolio. The tokens settle on a public or permissioned blockchain, enabling faster subscription and distribution cycles, potential secondary trading and composability with decentralized-finance protocols. The credit assets themselves remain off-chain – loan agreements, security interests, promissory notes – but the fund's capital structure and the investor's economic rights are represented and transferred through the token layer.
This structure diverges from equity-focused crypto funds in three material ways. First, the underlying portfolio generates scheduled interest payments and principal amortization, not mark-to-market appreciation; the fund's distribution waterfall must route these cash flows to token holders in a manner that respects both the credit agreements and the token's on-chain settlement mechanics. Second, defaults and workouts introduce collection, foreclosure and recovery processes that do not map cleanly to the redemption-on-demand model common in liquid token funds. Third, credit underwriting, loan servicing and borrower confidentiality impose operational and disclosure constraints that many equity managers do not face.
The legal architecture must therefore separate credit risk from tokenization risk, protect the originator's ability to service and restructure loans without token-holder interference, and ensure that the token's on-chain terms accurately reflect the fund's off-chain economics. A structure designed for a venture-backed equity fund – unlimited redemptions, no preference stack, minimal disclosure – breaks when applied to a credit portfolio that requires covenant monitoring, scheduled amortization and workout authority reserved to a servicer.
In our cross-border practice we see managers choose tokenization for three operational advantages: faster capital calls and distributions through programmable settlement, fractional exposure that lowers the minimum check size, and the potential to list tokens on a secondary venue or integrate them into a lending protocol as collateral. Each of these advantages, however, depends on a fund structure that can execute the relevant on-chain action without triggering a default under the underlying credit agreements or violating the investor's regulatory constraints. Structuring tokenized private credit is the exercise of aligning those three layers – the credit portfolio, the fund vehicle and the digital wrapper – so that each reinforces rather than undermines the others.
How are the originator and servicer separated from the fund vehicle?
The typical structure interposes a bankruptcy-remote special-purpose vehicle between the originator (who sources and underwrites the loans) and the token-issuing fund (which holds the beneficial interest in those loans and issues tokens to investors). The SPV holds legal title to the loan portfolio under a sale or participation agreement with the originator; the fund holds the equity or beneficial interest in the SPV and issues tokens representing fractional claims on the SPV's cash flows. This separation achieves three objectives: it ring-fences the credit risk so that an originator bankruptcy does not drag the fund's assets into insolvency proceedings, it preserves the originator's ability to service the loans and manage workouts without requiring token-holder votes, and it creates a clean legal boundary for accounting and tax consolidation.
The servicing agreement governs how the originator continues to administer the portfolio after the loans are sold or assigned to the SPV. The servicer collects payments, monitors covenants, pursues delinquent borrowers and, critically, exercises discretion in workout and restructuring scenarios. The agreement must specify the servicer's authority to amend loan terms, accept partial payment in settlement or initiate foreclosure, and it must define the standard of care and the events that trigger servicer removal. For a tokenized fund these provisions interact with the token's on-chain governance: if token holders can vote to remove the servicer or override a restructuring decision, that vote must route through the fund's off-chain governance layer and comply with any quorum or consent thresholds in the SPV documents.
The servicing fee – typically a percentage of outstanding principal or collected interest – is deducted before distributions reach the token holders, creating a senior claim that reduces the fund's net yield. This fee must be disclosed in the token's offering materials and reflected in the on-chain distribution logic if distributions are automated through a smart contract. A common mistake is to program the contract to distribute 100 percent of received funds to token holders, forgetting that the servicer, the trustee and any backup servicer all take their fees first. The result is an under-reserved contract that cannot execute its own distribution waterfall without manual intervention.
For managers originating loans in-house rather than purchasing them from a third party, the separation is still necessary to avoid consolidation risk and to maintain the SPV's bankruptcy remoteness. The originator sells the loans to the SPV at a price that reflects the expected credit loss, and the servicing agreement runs between the originator (as servicer) and the SPV. Tax authorities in many jurisdictions will challenge the sale if the transfer price is not arm's length or if the originator retains excessive control; the documents must therefore include true-sale representations, non-consolidation opinions and servicing standards that demonstrate the SPV's independence.
The process above describes the standard separation model. Your facts – whether the originator is also the fund manager, whether the credit portfolio includes cross-border loans, whether secondary liquidity is planned – change the analysis and the documentation suite required. For a scoped assessment of your originator and servicing structure, contact OBOLUS at info@oboluslaw.com.
Which jurisdiction and vehicle type should host the fund?
The fund domicile determines the regulatory perimeter, the tax treatment of fund-level income and the ease with which different investor classes can subscribe. For tokenized private credit the domicile decision turns on three variables: whether the target investor base is US-taxable, non-US institutional or retail; whether the credit portfolio generates US-source income; and whether the manager needs a regulated-fund wrapper to satisfy institutional due diligence or to passport into other markets.
A Cayman exempted limited partnership or segregated portfolio company is the default for non-US institutional allocators investing in a globally diversified credit portfolio. The Cayman structure is tax-neutral, offers well-understood limited-partnership governance and imposes minimal ongoing disclosure beyond audited financials. The token issued by the fund represents the limited-partnership interest; transfers are subject to the partnership agreement's consent and anti-money-laundering provisions, but the blockchain ledger provides a transparent record of current ownership that simplifies NAV calculations and distributions. Cayman law does not prohibit tokenization, but the partnership agreement must specify that the token is the method of evidencing the partnership interest and that the on-chain record is the authoritative ownership register.
A Delaware limited partnership or Delaware statutory trust works for a fund targeting US-taxable investors or where the manager prefers US legal infrastructure. The Delaware structure allows pass-through taxation for US investors and supports the issuance of digital securities under US securities law, but it introduces state-law complexities around the legal characterization of the token and around voting and consent mechanics if the token is held through a custodian or DeFi protocol. If the credit portfolio generates US-source income, a Delaware vehicle also simplifies withholding and reporting.
For a fund seeking to market to retail investors in the European Union under a prospectus or to qualify as an alternative investment fund under the AIFMD, a Luxembourg or Irish vehicle provides the regulated wrapper and the passporting capability that institutional allocators increasingly require. The trade-off is higher setup cost, ongoing supervision fees and mandatory depositary arrangements that add friction to the custody and distribution cycle. A Luxembourg reserved alternative investment fund or Irish qualifying investor AIF can issue tokenized units, but the depositary must be satisfied that the custody chain – from the fund to the token platform to the investor's wallet – meets the safeguarding requirements under the applicable regime. This typically requires a tri-party arrangement among the fund, a licensed digital-asset custodian and the depositary, with clear contractual allocation of liability for key loss, hacking and operational failures.
In our practice a common error is choosing a domicile for its headline tax rate or incorporation speed without pressure-testing the investor-access and custody consequences. A BVI vehicle may be fast and cost-effective, but many institutional allocators will not invest in a BVI fund, and the digital-asset custody options available to a BVI entity are narrower than those available to a Cayman or Delaware fund. The result is a structure that launches quickly but cannot scale past the first friends-and-family round.
How are feeders designed to accommodate different investor tax and regulatory profiles?
A multi-feeder structure allows a single master fund (holding the credit portfolio) to accept capital from US-taxable, non-US tax-exempt and retail investor classes, each through a separate feeder vehicle tailored to that class's tax and regulatory constraints. The master fund issues tokens to each feeder, and each feeder in turn issues its own class of tokens to its investors. The master's distribution waterfall allocates income and principal collections pro rata across the feeders based on their token balances; each feeder then applies its own distribution and tax-reporting rules to its investor base.
The US feeder is typically a Delaware partnership that issues tokens qualifying as securities under US law. US investors receive pass-through tax treatment and K-1 reporting; the feeder withholds on any non-US investors who mistakenly subscribe through the US vehicle and remits withholding to the IRS. The token issued by the US feeder is a restricted security, meaning it cannot be freely traded without registration or an exemption, and the feeder's limited-partnership agreement includes standard transfer restrictions and right-of-first-refusal provisions that override any attempt by an investor to transfer the token on a secondary market without the manager's consent.
The offshore feeder is typically a Cayman exempted company or additional class within the same Cayman partnership structure as the master. It issues tokens to non-US investors, avoiding US tax on the feeder's income and eliminating K-1 reporting. The offshore feeder's token may be structured as a freely transferable bearer instrument or, more commonly for private credit, as a registered token subject to know-your-customer re-verification on transfer. If the offshore feeder markets to EU investors it may need an AIFM notification or a prospectus, depending on the offering size and investor type; if it markets to UK professional investors it must comply with the FCA's financial-promotion rules.
A retail or semi-liquid feeder may be added if the manager intends to offer daily or weekly redemptions and to lower the minimum subscription to a level accessible to high-net-worth individuals. This feeder sits in a jurisdiction that supports collective-investment-scheme registration – Luxembourg, Ireland, Malta transitioning under MiCA, or a US interval fund structure – and it provides limited liquidity by redeeming tokens at NAV on set dates, subject to a queue and a redemption gate if requests exceed a threshold. The retail feeder's expenses (custody, administration, depositary, audit, regulatory fees) are higher than the institutional feeders', creating a drag that must be disclosed and that typically results in a lower net return for retail token holders than for investors in the master or offshore feeder.
The critical design choice is whether distributions from the master to each feeder occur on-chain or off-chain. An on-chain distribution sends stablecoins or wrapped fiat directly to the feeder's wallet address, and the feeder's smart contract automatically forwards the funds to investor wallets based on token balances at the snapshot date. This is fast and transparent but requires that every step in the chain – master to feeder, feeder to investor – is programmed correctly and that the tax and servicing deductions occur before the distribution leaves the master. An off-chain distribution wires fiat to the feeder's bank account, and the feeder calculates each investor's share and either mints new tokens or credits the investor's account; this preserves flexibility but loses the settlement-speed advantage that motivated tokenization in the first place.
How are investor eligibility and the subscription process structured for a tokenized credit fund?
Investor eligibility turns on whether the token is offered as a security, as a collective-investment-scheme unit or as an unregulated fractional interest, and on whether the offering is public or private. For a US private placement under Regulation D or Regulation S, investors must be accredited (for a 506(b) offering) or qualified purchasers (for a 3(c)(7) fund), and the subscription documents must include the standard representations, questionnaires and anti-money-laundering certifications. The token itself is the certificated evidence of the partnership or LLC interest; the subscription agreement specifies that accepting the token into the investor's wallet constitutes acceptance of the fund's limited-partnership agreement or operating agreement and that any transfer of the token is subject to the manager's consent and to re-verification of the transferee's eligibility.
The on-chain eligibility layer enforces these restrictions through a whitelist or permissioned-token model. The fund's smart contract maintains a list of approved wallet addresses; only addresses on the whitelist can receive or hold the token, and any transfer to a non-whitelisted address fails. The manager or a delegated administrator adds addresses to the whitelist after completing know-your-customer, accredited-investor verification and sanctions screening. This architecture prevents an investor from selling the token on a decentralized exchange or transferring it to a non-qualified holder, but it introduces a centralization point – the whitelist controller – that must be disclosed and that investors may perceive as reducing the token's liquidity and composability.
For a fund marketing under a prospectus in the EU or under a registered offering in the US, the subscription process must comply with the additional disclosure and cooling-off requirements of the relevant regime. A MiCA-compliant tokenized fund issues a crypto-asset whitepaper if the token does not qualify as a security, or a prospectus if it does; the whitepaper must describe the credit portfolio's risk factors, the servicing and default procedures, the fee waterfall and the custody arrangements in the format prescribed by the MiCA regulatory technical standards. Investors receive the whitepaper at least 48 hours before subscription, and the fund operator must maintain a public website with updated portfolio information and distribution history.
A common structuring question is whether to allow subscriptions in cryptocurrency or to require fiat only. Accepting cryptocurrency – stablecoins, bitcoin, ether – simplifies the on-chain settlement and appeals to crypto-native allocators, but it requires the fund to convert the crypto to fiat if the underlying credit portfolio is denominated in dollars or euros, introducing conversion risk and additional custody steps. Many fund administrators will not accept cryptocurrency subscriptions because their bank accounts cannot receive crypto proceeds directly; the fund must either use a licensed digital-asset custodian as a conversion layer or require the investor to convert to fiat before subscribing. If the fund does accept crypto, the subscription agreement must specify the conversion rate, the timing of the conversion, and which party bears the slippage risk between subscription and conversion.
If a prior application stalled because the administrator or depositary could not accommodate tokenized subscriptions, a second read can surface the structural reason – often a mismatch between the custody model the documents assumed and the custody model the service providers actually support – and the route back to a workable stack. For a full stack assessment, write to info@oboluslaw.com.
What disclosure and reporting obligations apply to a tokenized private-credit fund?
The disclosure regime depends on whether the token is a security, the fund's domicile, the investor base and the secondary-market plans. For a US private fund relying on the 3(c)(1) or 3(c)(7) exemptions, the manager must deliver quarterly statements showing NAV, portfolio composition and fund-level expenses, and annual audited financials. If the fund has more than a threshold number of investors or assets under management, the manager must also file Form PF with the SEC, disclosing portfolio concentration, leverage and liquidity metrics. These obligations apply regardless of tokenization, but the on-chain transparency of the token's distribution history can simplify some reporting burdens and create others: investors see every distribution in real time, which reduces information asymmetry, but any discrepancy between the on-chain record and the audited financials must be explained.
For an offshore fund the disclosure baseline is the private-placement memorandum, the limited-partnership agreement and the audited financials. If the fund markets to EU professional investors under the AIFMD, the manager must also provide the disclosures required by the marketing passport, including detailed risk and liquidity profiles and the identity of the depositary. If the token will trade on a secondary market or digital-asset exchange, that venue may impose additional listing standards: continuous disclosure of material portfolio events, monthly or weekly NAV updates, and public reporting of defaults and restructurings in the underlying credit portfolio.
The credit portfolio itself introduces confidentiality constraints that do not apply to public-equity funds. Loan agreements typically include borrower confidentiality provisions that restrict the lender from disclosing financial information, covenant breaches or restructuring terms to third parties. A tokenized fund must structure its investor reporting to comply with these restrictions while still providing enough detail for investors to assess credit risk. The standard approach is to report at the portfolio level – total outstanding principal, weighted-average yield, percentage of loans in each rating category, aggregate delinquency and default rates – without disclosing individual borrower names or loan-level performance except for material defaults that have already become public.
The on-chain component of the fund – the token contract, the distribution logic, the whitelist controller – should be documented in a technical whitepaper separate from the legal offering memorandum. The technical whitepaper describes the contract's functions, the data it stores, the off-chain dependencies (price oracles, custodian APIs, servicer payment feeds), and the scenarios under which the contract might pause or fail. If the contract is upgradeable the whitepaper must disclose the governance process for upgrades and the addresses with upgrade authority. This document is not a substitute for a legal prospectus, but it provides the technical due diligence that sophisticated investors and their auditors require to understand custody and settlement risk.
How is custody arranged for a tokenized private-credit vehicle?
Custody for a tokenized private-credit fund operates at two levels: custody of the underlying credit assets (the loan agreements and security interests held by the SPV) and custody of the tokens that represent investor interests in the fund. The credit assets are held by a trustee or security agent under the SPV's governing documents; this is off-chain custody governed by traditional trust law and Uniform Commercial Code provisions. The tokens, by contrast, require digital-asset custody – secure storage of the private keys that control the fund's wallet addresses and the investor wallets holding the tokens.
For the fund's treasury wallet – the wallet that receives fiat-to-crypto conversions, holds reserves and sends distributions – the custody solution must be institutional-grade, ideally a licensed digital-asset custodian that provides insurance, multi-signature security, disaster recovery and regulatory oversight. The custodian issues the fund a wallet address, retains the private keys in cold storage or hardware-security modules and requires multiple authorized signatories to approve any outbound transaction. The fund administrator needs read-only access to the wallet to calculate NAV and verify distributions, but write access (the ability to transfer funds) is restricted to the custodian and the manager's designated officers.
For investor wallets the custody responsibility shifts to the investor, but the fund's documentation must specify the consequences of key loss. If an investor loses access to the wallet holding the token, the token is effectively frozen on-chain and the investor cannot receive distributions or transfer the interest. Some structures include a key-recovery mechanism: the investor proves identity through an off-chain process (notarized affidavit, court order) and the fund mints a replacement token to a new address and burns the old token. This requires the token contract to support a burn-and-reissue function and requires the fund's governance documents to authorize the manager to execute that function. The alternative is to include standard lost-certificate provisions in the limited-partnership agreement, treating a lost token like a lost stock certificate: the investor posts a bond or indemnity, the manager issues a replacement interest as a book entry and updates the off-chain register, and the old token remains on-chain but is marked as void.
If the fund uses a regulated depositary – required for a Luxembourg or Irish fund – the depositary must be satisfied that the custody chain meets the safeguarding requirements under the applicable regime. This typically requires a tri-party agreement among the fund, a licensed digital-asset custodian and the depositary, with the depositary exercising oversight but not holding the keys itself. The depositary verifies that the custodian is licensed, that the insurance coverage is adequate, that the disaster-recovery plan has been tested and that there is a clear contractual allocation of liability for different failure modes (key loss, hacking, insider theft, custodian insolvency).
How is the distribution waterfall structured and what happens on default?
The distribution waterfall defines the priority in which fund-level cash flows are allocated: first to expenses (servicing fees, trustee fees, audit, administration, custody), then to any senior or preferred token classes, then to common token holders and finally to the manager's performance fee or carried interest. This waterfall must be documented in the fund's governing documents and, if distributions are automated on-chain, encoded into the distribution smart contract. A mismatch between the legal waterfall and the on-chain logic is a hard failure: the contract may distribute funds to token holders before deducting fees, causing the fund to breach its service agreements, or it may withhold funds for fees that have already been paid off-chain, causing a shortfall to investors.
The most robust approach separates the waterfall into stages. Stage one occurs off-chain: the servicer collects payments from borrowers, deducts its fee and remits the net proceeds to the fund's bank account. The fund administrator then deducts fund-level expenses (audit, legal, custody, administration) and moves the remaining balance to the fund's distribution wallet. Stage two occurs on-chain: the distribution contract reads the wallet balance, calculates each token holder's pro-rata share and sends the funds to investor wallets. The performance fee is either deducted before the funds reach the distribution wallet or taken as a redemption of the manager's own tokens after the distribution, depending on the tax and accounting treatment the manager prefers.
Defaults introduce a separate path. When a borrower defaults the servicer initiates collection or foreclosure proceedings under the loan agreement; the credit portfolio's cash flows stop or become irregular as restructurings and settlements occur. The fund's governing documents must specify whether default recoveries are distributed immediately when received or reserved to cover future losses. A common credit-fund structure creates a reserve account: the first portion of recoveries goes into the reserve until it reaches a percentage of outstanding principal, and only recoveries above that threshold are distributed to token holders. This smooths distributions and protects against the risk that a subsequent default wipes out the prior recovery, but it means token holders do not see the full benefit of a successful collection until the reserve target is met.
The fund's default-disclosure policy must balance transparency with borrower confidentiality. Material defaults – typically defined as defaults exceeding a percentage of the portfolio or defaults that cause the fund's NAV to drop below a threshold – must be disclosed to investors promptly, but the disclosure should be generic ("a borrower representing X percent of the portfolio has entered default; collection proceedings are underway") rather than naming the borrower or disclosing the specific loan terms. If the on-chain token contract includes a transparency dashboard, that dashboard should display aggregate default statistics but not individual loan-level data.
For funds that allow redemptions – typically limited to quarterly or semi-annual gates – defaults complicate the redemption queue. If the credit portfolio is illiquid and the fund has insufficient cash to meet redemption requests, the fund must either sell loans at a discount to raise liquidity, borrow against the portfolio or suspend redemptions until cash is available. The limited-partnership agreement should include a redemption-gate provision (e.g., no more than 25 percent of outstanding tokens may be redeemed in any quarter) and a suspension clause allowing the manager to halt redemptions if the portfolio's liquidity drops below a threshold. These provisions must be disclosed in the offering memorandum and reflected in the token's terms, and investors must acknowledge them before subscribing.
Can token holders trade their interests on a secondary market and how does that affect fund governance?
Secondary liquidity is one of tokenization's most cited advantages: in theory, token holders can sell their interests on a digital-asset exchange or peer-to-peer without waiting for fund redemptions, and the market price provides a real-time valuation signal that complements the fund's NAV. In practice, secondary trading for a private-credit token is limited by regulatory, contractual and liquidity constraints, and managers must decide early whether to enable secondary trading and, if so, on what terms.
For a US private fund the token is a restricted security under Regulation D, meaning it cannot be traded on a public exchange or freely transferred without registration or an exemption. The most common exemption for secondary trades is Rule 144, which allows sales after a one-year holding period to qualified institutional buyers or, after additional restrictions, to accredited investors. The fund's limited-partnership agreement may also restrict transfers outright, requiring the manager's consent and imposing a right of first refusal that gives the fund or other investors the option to purchase the token before the holder can sell to a third party. These restrictions must be reflected in the token's smart contract: the contract includes a time-lock that prevents transfers until the one-year holding period expires, and a consent function that requires the manager's digital signature before any transfer executes.
For an offshore fund the regulatory barriers to secondary trading are lower, but the practical barriers remain. A Cayman exempted partnership's limited-partnership agreement typically includes a consent-to-transfer provision, meaning any transfer requires the general partner's consent. The general partner will grant consent only after the transferee has completed know-your-customer verification, accredited-investor or professional-investor qualification and sanctions screening. This re-verification process can take several days to several weeks, during which the token is effectively frozen. A peer-to-peer secondary market may solve the liquidity problem for the seller, but it creates an operational burden for the fund administrator, who must update the register and re-verify each new holder.
Listing the token on a licensed digital-asset exchange – a secondary venue regulated by the FCA, MAS, SFC or a comparable authority – provides greater liquidity but subjects the fund to the exchange's listing standards. These typically include continuous disclosure requirements, minimum free-float thresholds, market-making commitments and periodic NAV publication. The exchange may also require the fund to maintain a certain level of assets under management, to have been operating for a minimum period and to have a track record of timely distributions and accurate NAV reporting. For a new credit fund meeting these standards at launch is often impractical; the typical path is to launch as a private fund with restricted secondary trading and to pursue exchange listing once the fund has reached a threshold size and demonstrated performance.
The governance question is whether secondary trading should trigger any change in the fund's operations. If the token trades at a significant discount to NAV that may signal credit concerns or operational problems; the manager must decide whether to investigate and disclose the cause or to treat the secondary price as irrelevant noise. If the token holder base becomes fragmented – hundreds of small holders acquired through secondary trades – that complicates governance and increases the risk of activist investors accumulating a blocking stake through off-market purchases. The fund's governance documents should specify voting and consent thresholds that account for potential fragmentation, and they should reserve to the manager the authority to suspend secondary trading or to redeem small holdings compulsorily if fragmentation becomes unmanageable.
Related at OBOLUS
- Funds & Investment Vehicles for Digital-Asset Businesses – structuring, licensing and operational advice for crypto asset managers
- Staking Inside an Exchange-Traded Product: Structuring and Disclosure – custody and yield considerations for tokenized investment products
- Crypto Fund Formation in United States: Federal + State MTL – US regulatory perimeter for digital-asset fund managers
FAQ
Where should this fund be domiciled?
The domicile turns on your target investor base, the credit portfolio's income sources and whether you need a regulated wrapper. A Cayman vehicle works for non-US institutional allocators investing in a globally diversified portfolio; a Delaware structure suits US-taxable investors or where the manager prefers US legal infrastructure; a Luxembourg or Irish vehicle provides the regulated fund status and EU passporting capability that some institutions require. The decision affects tax treatment, custody options and the ease with which different investor classes can subscribe.
Does the manager need a licence?
That depends on the fund's domicile, the offering method and the manager's location. A manager operating a US private fund typically registers as an investment adviser with the SEC or relies on an exemption; a manager of an EU alternative investment fund may need AIFM authorisation or registration; a manager in the Cayman Islands or BVI generally does not need a local licence but must comply with anti-money-laundering registration. If the fund's token is classified as a security the manager may also need a broker-dealer licence or must use a licensed placement agent for subscriptions. For advice on your licensing perimeter, contact info@oboluslaw.com.
How is custody arranged for this vehicle?
Custody operates at two levels: off-chain custody of the underlying credit assets by a trustee or security agent, and digital-asset custody of the tokens. The fund's treasury wallet should be held by a licensed institutional custodian offering insurance, multi-signature security and regulatory oversight. Investors hold their own tokens in self-custody wallets or through a qualified digital-asset custodian. If a regulated depositary is required – for a Luxembourg or Irish fund – a tri-party arrangement among the fund, a licensed crypto custodian and the depositary is standard, with clear contractual allocation of liability for different failure modes.
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across more than seventy jurisdictions, on disputes and on-chain asset recovery across more than twenty-five 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, structuring the fund cascade so that each layer reinforces rather than undermines the others. To discuss your tokenized credit vehicle, contact info@oboluslaw.com.
By Lydia Brennan, Tax & Structuring Analyst – Lydia specializes in cross-border fund structuring, tokenized investment vehicles and the tax treatment of digital-asset income across multiple jurisdictions.
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.