Tokenized Feeder Funds: Structure and Setup Guide
What Is a Tokenized Feeder Fund?
A tokenized feeder fund is a pooling vehicle whose interests are issued as digital securities on a blockchain-based register. The feeder invests into a master fund as a single limited partner or shareholder, so smaller-ticket investors gain exposure to an institutional fund without the master's documents, minimums, or investor register changing at all. The token represents a share or interest in the feeder — not in the master, and not in the master's portfolio companies. Everything novel lives at the feeder layer; the master fund operates exactly as before.
This guide covers the anatomy of the structure, jurisdiction choice for the feeder vehicle, the economics investors actually receive, operational mechanics, and the setup sequence for GPs and access platforms.
Why Feeders Are the Dominant PE Tokenization Pattern
Of all the ways to tokenize private equity exposure, the feeder is the pattern that has actually shipped at scale — for structural, not technological, reasons.
The master fund and its LPA stay untouched. Tokenizing an existing fund directly means amending the limited partnership agreement, re-papering side letters, and getting consent from an LP base with no appetite for novelty. A feeder avoids all of that: the master admits one new LP — the feeder entity — under its existing subscription documents. From the master's perspective, nothing has been tokenized.
The innovation is contained. Digital share issuance, on-chain transfer controls, stablecoin subscription flows, and automated register maintenance all happen inside a vehicle the GP (or a third-party access platform) controls end to end. If the tokenization layer changes — a new chain, registrar, or compliance module — the master fund is unaffected.
It matches how access products already work. Wealth platforms have used traditional feeders for decades to aggregate smaller commitments into institutional funds. Tokenization upgrades the plumbing of a familiar structure rather than inventing a new one, which is why counsel can document it quickly and administrators can service it.
For the broader landscape — direct fund tokenization, continuation vehicles, and where feeders fit — see our private equity tokenization guide. This article stays on the feeder itself.
Anatomy of a Tokenized Feeder Structure
The structure has four layers:
- Master fund. The institutional fund — typically a Cayman or Delaware limited partnership — with its existing GP, LPA, and LP base. Not tokenized.
- Feeder entity. A newly formed vehicle that subscribes to the master as a single LP: a Cayman exempted company or segregated portfolio company (SPC), a BVI business company, a Luxembourg RAIF or SCSp, or a Delaware LP.
- Tokenized interests. The feeder's shares or partnership interests issued as digital securities; the on-chain register is (or mirrors) the legal register of members, with transfer restrictions enforced by smart contract.
- Investors. Qualified investors who pass KYC/AML and eligibility checks subscribe, receive tokens, and hold indirect exposure to the master's portfolio.
Choosing the Feeder Jurisdiction
The master fund's domicile is fixed; the feeder's is a design choice. The comparison below reflects the trade-offs GPs and access platforms weigh most often:
| Feeder vehicle | Typical use case | Tokenization compatibility | Key considerations |
|---|---|---|---|
| Cayman exempted company / SPC | Global institutional master funds; multi-fund access platforms (one SPC, many portfolios) | Strong — digital share registers recognized; securities fall under SIBL, not VASPA | Institutional familiarity; no direct taxation; CIMA registration analysis needed for fund-type feeders |
| BVI business company | Cost-sensitive single-fund feeders for non-US investors | Strong — flexible share classes, fast formation | Lighter fund brand than Cayman; incubator/approved fund regimes cap size |
| Luxembourg RAIF / SCSp | EU distribution to professional investors under AIFMD passport | Good — DLT-based securities recognized under Luxembourg blockchain laws | Requires an authorized AIFM; higher setup and running costs |
| Delaware LP | US-taxable investor base investing in a US or Cayman master | Good — LP interests tokenized as securities under Reg D | Keeps US investors in a familiar K-1 structure; state and federal securities analysis at feeder level |
A Cayman feeder deserves special mention because classification questions come up constantly: tokenized shares in a Cayman feeder are securities under Cayman law, so the relevant regime is SIBL rather than the VASP framework — a distinction we unpack in our Cayman Islands tokenization and VASP guide. The feeder is also, functionally, a special purpose vehicle; the general design questions — governance, bankruptcy remoteness, register architecture — are covered in our SPV structuring service overview.
Economics: Fee Stacking and Falling Minimums
The feeder's economics deserve honest treatment, because this is where poorly built access products lose trust.
Fee stacking
A feeder investor bears two layers of cost: the master fund's management fee and carried interest (typically 2%/20% or a variant), plus feeder-level costs — formation and administration expenses, platform or servicing fees, and sometimes an additional feeder-level management fee. Net returns to a feeder investor are therefore structurally below what a direct LP earns on the same gross performance.
Present this plainly: disclose each fee layer separately, show net-of-all-fees return scenarios, and never market master-fund track records as if feeder investors receive them undiluted. Allocators expect a feeder to cost something; what they penalize is discovering the stack after subscribing.
Minimums
The commercial reason feeders get tokenized at all is minimum reduction. The most cited example: Securitize's tokenized feeder into Hamilton Lane's Senior Credit Opportunities Fund (SCOPE), launched on Polygon in May 2023, cut the minimum from $2 million to $10,000 for qualified purchasers, per Securitize's announcement and reporting by The Block. Hamilton Lane later made its $5.6 billion Secondary Fund VI available through a Securitize-managed tokenized feeder as well, per the firms' 2024 announcement. The pattern is consistent: institutional funds with $1M–$5M direct minimums become accessible at $10K–$100K tickets through tokenized feeders — with eligibility gates intact.
Lower minimums change the operational math. A feeder admitting 500 investors at $20K instead of 5 at $2M only works if onboarding, the register, capital calls, and distributions are automated — which is precisely what the tokenization layer is for.
Operational Mechanics of a Tokenized Feeder
Capital calls
Most PE masters call capital over an investment period rather than taking it upfront. A tokenized feeder handles this one of two ways. In the committed-capital model, the feeder mirrors the master: investors sign commitments, the platform issues call notices with on-chain payment tracking (stablecoin or wire), and each holder's funded percentage updates automatically — defaults are handled under the feeder's own documents, insulating the master. In the fully funded model, the feeder collects the entire subscription upfront and holds uncalled amounts in reserve, simplifying investor experience at the cost of cash drag. Small-ticket access products usually go fully funded; institutional feeders usually mirror the master.
Distribution waterfalls
When the master distributes to the feeder, the feeder redistributes to token holders pro rata to funded interests, after feeder-level fees and reserves. Because the on-chain register is authoritative and current, waterfall calculations that administrators normally reconcile in spreadsheets execute programmatically — including mid-life scenarios where holders acquired tokens at different times through permitted transfers.
NAV updates and reporting
The feeder's NAV derives from the master's reported NAV (typically quarterly for PE), adjusted for feeder-level fees, expenses, and cash. The platform publishes per-token NAV on the same cadence; statements, capital account balances, and audit-ready ownership histories generate from the register rather than from reconciliation exercises.
Register maintenance
The register of members is the legal heart of the vehicle. The on-chain record either constitutes the register (where the feeder jurisdiction recognizes electronic/DLT registers) or is the operational system of record synchronized with the administrator's legal register. Transfers settle only between whitelisted, eligibility-verified wallets, and every change is timestamped for the auditor and regulator. Our DAO fund platform case study shows this register-and-governance architecture running for a pooled vehicle with distributed holders.
Eligibility and Distribution Rules: Who Can Be Offered What, Where
Tokenizing the feeder does not relax securities law — it enforces it in software. The offering analysis happens at the feeder level, because the feeder is the issuing entity:
- United States — Reg D. Feeder interests offered under Rule 506(b) or 506(c) are restricted securities limited to accredited investors — and, where the master requires it, qualified purchasers under the Investment Company Act (the Hamilton Lane feeders remained qualified-purchaser products). Transfer restrictions and holding periods are coded into the token.
- Offshore — Reg S. Non-US investors onboard under Regulation S with distribution compliance periods and no directed selling into the US; the platform segregates Reg D and Reg S tranches at the wallet level.
- EU/UK — professional investor regimes. A Luxembourg feeder distributes to professionals under the AIFMD passport; national private placement regimes cover other cases. Retail access generally requires an ELTIF 2.0 or equivalent wrapper — a different product, not a feeder variant to improvise.
- Middle East and Asia. ADGM, DIFC, Singapore, and Hong Kong each maintain professional/accredited investor definitions gating who may be onboarded there.
The practical consequence: a tokenized feeder is usually a multi-tranche offering with per-jurisdiction eligibility logic, enforced at transfer time by the compliance module rather than a PDF subscription booklet.
Setup Sequence: From GP Consent to First Onboarding
A tokenized feeder launch runs through four gates, in order:
- Fund selection and GP consent. The master's GP must approve the feeder's admission as an LP — and most LPAs restrict transfers and require GP consent for changes in beneficial ownership, which flows down to the feeder's token transfer rules. Negotiate capacity, reporting access, and fee treatment here; nothing downstream matters without it.
- Feeder formation with qualified counsel. Entity formation, offering documents, tranche structure (Reg D/Reg S/professional-investor), and tax analysis are legal work. Asset Haus coordinates this with qualified fund formation counsel as part of legal setup — we are infrastructure, not a law firm, and the offering documents are counsel's work product.
- Platform deployment. Token contracts with embedded transfer controls, the onboarding flow (KYC/AML, accreditation, sanctions), register configuration, and administrator integration — where the difference between a traditional and tokenized SPV stack becomes operational rather than theoretical.
- Onboarding and first close. Investors verify, sign, fund, and receive tokens; the register goes live as the system of record; capital call and distribution workflows are tested against the master's actual cadence.
Across 32 deals structured and $200M+ facilitated in 9+ jurisdictions, we run this on a 120-day launch model — a planning framework, with GP consent and counsel usually setting the critical path.
Pitfalls to Plan Around
- GP consent and transfer restrictions flow down. Whatever the master LPA restricts, the feeder must restrict at least as tightly. A token that trades more freely than the underlying LP interest permits is a structural defect, not a feature. Design secondary transfer windows around the master's consent mechanics — and see our private equity secondaries tokenization guide for how compliant secondary workflows actually run.
- Tax leakage by feeder jurisdiction. A badly placed feeder can turn a tax-efficient master into a leaky product — US withholding on effectively connected income or FDAP flows, treaty differences between Cayman, BVI, and Luxembourg, and PFIC/CFC consequences for US investors in offshore corporate feeders. This is analysis for tax counsel, done before formation, not after.
- ERISA and regulated-investor thresholds. US benefit plan investors can trigger plan asset treatment above the 25% threshold; some feeders exclude ERISA money entirely, others monitor the limit in the compliance module. Awareness-level note only — take it to ERISA counsel.
- Master-fund reporting dependency. The feeder can only report what the master provides. Confirm NAV cadence, K-1/PFIC statement timing, and audit access during the consent negotiation — token holders will expect faster reporting than a quarterly PE master naturally produces.
FAQ
What is a tokenized feeder fund?
A pooling vehicle — typically a Cayman exempted company, BVI company, Luxembourg RAIF/SCSp, or Delaware LP — whose shares or interests are issued as digital securities. The feeder invests in an institutional master fund as a single LP, giving smaller-ticket investors indirect exposure without any change to the master's documents.
Do feeder investors get the same returns as direct LPs?
No. Feeder investors receive the master's returns minus feeder-level costs: administration, platform or servicing fees, and any additional feeder management fee. On the same gross performance, a feeder investor's net return is below a direct LP's — which is why credible products disclose each fee layer separately.
Which jurisdiction is best for a tokenized feeder?
It depends on the investor base. Cayman exempted companies and SPCs suit global institutional distribution; BVI suits cost-sensitive non-US offerings; Luxembourg RAIF/SCSp suits EU professional-investor distribution under AIFMD; Delaware LPs suit US-taxable investors. Tax leakage and the master's domicile usually drive the final call, made with qualified counsel.
Does the master fund have to change anything to accept a tokenized feeder?
Structurally, no — the master admits the feeder as one new LP under its existing subscription documents. But the GP must consent, and in practice negotiates capacity limits, reporting terms, and assurances that the feeder's transfer controls are at least as strict as the master LPA's.
Can tokenized feeder interests be traded?
They can be transferred, subject to the securities rules of the offering (Reg D holding periods, Reg S compliance periods, professional-investor gates) and restrictions flowing down from the master LPA. Transfers settle between verified, whitelisted investors through controlled workflows — not a freely traded public market.
Planning a tokenized feeder for your fund or access platform? Start with a structured assessment.
Next step
Map the legal perimeter before launch.
Use the counsel-ready memo to separate issuer, platform, regulated partner, custody, transfer, and public-copy responsibilities.
Related Articles
Best Jurisdiction for Tokenized Asset Issuance (2026)
How to choose a jurisdiction for tokenized asset issuance: legal token recognition, flagship vehicles, and custody compared across leading hubs.
Platform & InfrastructureERC-3643 vs ERC-1400: Security Token Standards
ERC-3643 vs ERC-1400 compared: identity registries, partitions, transfer controls, and how each standard maps to US Reg D compliance.
Market CommentaryGCC Tokenization Market: 2026 Report
How big is the GCC tokenization market in 2026? Deal activity by country, flagship initiatives, demand drivers, and a 2026–2027 outlook.