The institutional allocator decision on tokenised funds is not a technology question and it is not a yield question. It is a fiduciary discipline question. The CIO of a US insurer, a sovereign wealth fund, a corporate treasury, or a fund-of-funds running an institutional mandate has to fit a tokenised product into an investment policy statement that was written for conventional fund wrappers, satisfy a board investment committee that the operational risk profile is at least as good as the conventional alternative, and demonstrate to internal compliance that the regulatory wrapper is recognisable. The reasons CIOs say no on tokenised funds are well-rehearsed (custody risk, T+0 mismatch with rebalancing windows, NAV transparency versus daily-pricing convention, regulatory wrapper unfamiliarity). The reasons they are starting to say yes are less rehearsed (collateral mobility, intraday liquidity, programmable cash management) and structurally more interesting because they reframe what the tokenised fund actually is: not a marginally better wrapper around an existing asset, but a different operating instrument with capabilities the conventional version does not have. This page maps both sides of the allocator-side decision, anchored by the Apollo / BlackRock / Franklin Templeton commentary that has driven the institutional conversation through 2024-2026.
Why CIOs say no
Four objections come up consistently in the allocator-side commentary, and each one has a substantive operating basis rather than just a familiarity bias.
Custody risk. The conventional institutional custody chain (a fund administrator at BNY or State Street, a sub-custodian at the relevant national CSD, holding via DTC in the US or Euroclear in the EU) has decades of operational track record and an explicit fiduciary regime layered on top. The on-chain custody alternative is structurally newer, with the operational discipline less time-tested. A CIO carrying a fiduciary obligation to act prudently has to defend a custody-arrangement choice against the conventional benchmark, and the on-chain alternative is harder to defend because the comparable track record does not exist yet.
The substantive read on the BUIDL stack illustrates the shape of the answer that has been emerging. BUIDL's underlying T-bill, repo, and cash sleeve sits in conventional custody at BNY. The on-chain wrapper is a representation layer on top of that custody arrangement. The custody risk on BUIDL is therefore not the on-chain piece (which is the SEC-registered transfer-agent function operated by Securitize) but the same custody arrangement a conventional MMF holder would have. The framing matters: the allocator is not trading conventional custody for on-chain custody, they are choosing whether to add an on-chain representation layer on top of the existing custody chain.
T+0 mismatch with rebalancing windows. Institutional rebalancing typically operates on T+1 or T+2 cycles to align with the underlying-asset settlement cadence and with internal investment-committee approval workflows. A T+0 (intraday or same-day) settlement primitive does not match the existing rebalancing cadence and may even create operational friction by requiring decisions to be made on a faster cadence than the institution is structurally set up to make.
The substantive read here is more nuanced. T+0 settlement on the tokenised side does not require the allocator to operate on a T+0 rebalancing cadence; it just makes T+0 available as a primitive when needed. An allocator using BUIDL or FOBXX as a tokenised cash holding inside a broader strategy can continue to rebalance the strategy on its conventional cadence while gaining the option to access the tokenised position intraday for collateral, redemption, or stablecoin-swap purposes. The T+0 capability is a tool the allocator can use on demand rather than an operating cadence the allocator has to adopt.
NAV transparency versus daily-pricing convention. Conventional MMFs publish a single end-of-day NAV; tokenised MMFs with on-chain rebase mechanics distribute yield through changing token balances. The two patterns deliver economically equivalent outcomes but are operationally different in a way that matters for fund-of-funds reporting, performance attribution, and conventional investment-policy-statement conformity. An allocator that has never had to handle a rebase token before has to update its accounting and reporting systems before it can hold one.
The substantive read is that the rebase mechanic is the issue rather than the underlying economics. Products like BUIDL that rebase daily require accounting accommodations; products like FOBXX with more conventional yield distribution mechanics do not have the same operational integration cost. Allocator preference between the two is partly driven by the operational discipline question rather than by any underlying-asset distinction.
Regulatory wrapper unfamiliarity. An institutional investment policy statement typically lists the wrapper categories the institution is permitted to hold (mutual funds, ETFs, separately managed accounts, hedge funds, private credit funds, money-market funds). A tokenised fund operates inside one of these wrappers (BUIDL inside the 3(c)(7) qualified-purchaser exclusion, FOBXX inside the 2a-7 government MMF perimeter), but the on-chain layer is not standardly addressed in the wrapper catalogue.
The substantive read is that the wrapper does not change just because there is an on-chain token attached to it. BUIDL is a 3(c)(7) Delaware LLC; that wrapper is recognisable to any institutional allocator that already holds qualified-purchaser-only fund interests. FOBXX is a 2a-7 government MMF; that wrapper is one of the most-held fund categories in the institutional space. The tokenisation layer adds capability without changing the underlying wrapper, and the institutional investment policy statement can usually accommodate the tokenised product through a clarification rather than a new wrapper category.
Why CIOs are starting to say yes
Three structural reasons for institutional-allocator interest in tokenised funds, anchored by the Apollo, BlackRock, and Franklin Templeton commentary that has driven the conversation through 2024-2026.
Collateral mobility. The conventional institutional collateral chain (Treasury collateral posted through the bilateral repo market or through CCP-cleared repo at FICC) operates on a settlement cadence that constrains how dynamically the collateral can be reallocated. A tokenised position (BUIDL on the JPMorgan TCN, JAAA on Aave Horizon, BUIDL on Binance as institutional collateral) can be posted, redeemed, or substituted on a faster cadence than the conventional alternative. For an allocator running a leveraged strategy or a treasury-management programme that uses collateral substitution as a yield-enhancement tool, the mobility differential is a substantive economic benefit.
Larry Fink's annual letters across 2024-2026 have positioned tokenisation as a structural rail for next-generation capital markets, with the collateral-mobility story as one of the more consequential pieces of the thesis. The Apollo positioning around ACRED in private credit has been similar, with the on-chain wrapper framed as enabling distribution and collateral use cases the conventional fund vehicle cannot support. The Franklin Templeton positioning around BENJI has emphasised the institutional and adjacent retail distribution flexibility that the tokenised wrapper enables.
Intraday liquidity. The on-chain liquidity primitive that BUIDL provides through the Circle USDC swap (during market hours, BUIDL holders can swap to USDC at par against the on-chain swap contract) is a structurally new capability for institutional MMF holders. The conventional MMF redemption cycle requires the holder to wait for the daily redemption window; the on-chain swap is intraday. For an allocator managing intraday cash needs (trading desk margin, settlement-window cash management, intraday liquidity covenant compliance), the on-chain liquidity layer is materially better than the conventional alternative.
The structural significance is that the tokenised MMF is not just a wrapper around an underlying fund, it is a different operating instrument with capabilities the underlying fund does not have. The Circle USDC swap is not part of the conventional FOBXX or BUIDL fund structure; it is a tokenisation-layer integration that delivers the intraday liquidity capability. Allocator demand for that capability is one of the underexplored drivers of the institutional tokenised-fund AUM growth.
Programmable cash management. The conventional corporate treasury cash-management stack runs through bank account structures with daily sweeps, conditional transfer rules, and operational controls implemented at the bank-software layer. The tokenised cash alternative (a tokenised MMF position used as a cash-equivalent treasury holding, with programmable conditional-payment logic on top) is the corporate-treasury analogue of the institutional collateral-mobility story.
The DBS Token Services and JPMorgan Kinexys positioning around tokenised deposits has emphasised the corporate-treasury programmability story explicitly. The question for the tokenised MMF side is whether the same programmable-cash-management story extends to fund interests. As of late April 2026, the early integrations (BUIDL on TCN, BUIDL as Binance collateral, JAAA on Aave Horizon) suggest the answer is yes for institutional-grade allocators, with the corporate-treasury extension still being built.
What the allocator decision actually requires
For a CIO actually allocating, four operating items have to be addressed before the allocation can clear.
Investment policy statement clarification. The IPS has to either explicitly accommodate the tokenised wrapper or be amended to do so. For a tokenised MMF wrapping a conventional 2a-7 or 3(c)(7) fund, the clarification is usually addressable without a substantive amendment. For a tokenised private-credit fund (ACRED) where the underlying wrapper is itself less common in the IPS, the amendment is more substantial.
Operational risk approval. The institutional operations team has to review the on-chain custody arrangement, the wallet-management approach, the cross-chain whitelist administration (where applicable), and the integration with the institution's existing custody platform. For most institutional allocators the operational risk review is the longest part of the approval process.
Regulatory wrapper validation. The investment compliance team has to validate that the tokenised product fits the institution's regulatory profile. For a US insurer regulated under state insurance law, a US public pension fund regulated under state public-fund law, a US private-fund holder regulated under ERISA, the analyses differ. The qualified-purchaser eligibility for BUIDL is a specific item that the compliance team has to check; the regulatory profile for FOBXX is different again.
Investment committee briefing. The allocation has to clear the investment committee with a substantive briefing on what the product is, why the allocation makes sense for the strategy, and what the operational considerations are. The briefing format is the same as for any new institutional position; the substantive content has to address the tokenisation-specific questions.
The four-step process is not faster for tokenised products than for conventional products, despite the technology layer being newer. The discipline is the same.
What the data suggests
The named institutional buyer base on BUIDL includes Ondo Finance (as the reserve asset behind OUSG), Ethena Labs, OKX, Standard Chartered, and the JPMorgan TCN integration that allows BUIDL to be posted as collateral against tokenised cash on the Kinexys rail (source). The composition of the broader holder distribution is whitelist-confidential.
The growth trajectory (USD 1 billion in March 2025, USD 2 billion plus USD 100 million cumulative dividends by December 2025, CoinDesk) is one of the cleanest data points on institutional-allocator uptake. The trajectory is faster than the FOBXX trajectory was at the same point in its lifecycle, but FOBXX launched in April 2021 in a materially different institutional adoption environment.
The qualitative read from the public commentary is that the institutional allocator conversation has shifted between 2023 and 2026 from "is this product a credible institutional position" (where the answer was usually no) to "what allocation size makes sense for the specific strategy" (where the answer is usually a small but meaningful share of the cash sleeve, with growing room for the collateral and intraday-liquidity use cases). The shift is partly the BUIDL anchor mandate driving credibility, partly the broader institutional-tokenisation infrastructure (Securitize as transfer agent, BNY as custodian, the multi-chain stack) reaching a maturity that allocators recognise.
Open questions
- The composition of the broader institutional buyer base on BUIDL beyond the publicly named participants. Coverage names a small set; the holder distribution is whitelist-confidential.
- APAC institutional uptake of US-issued tokenised MMFs (BUIDL through Standard Chartered, FOBXX through MAS-licensed channels). The regional positioning is explicit but the live distribution pipeline is not consistently disclosed.
- Whether Asian-issued tokenised MMFs (Progmat-issued wrappers in Japan, MAS-perimeter authorised funds in Singapore) achieve credible institutional-allocator uptake on a comparable trajectory to the US-issued products.
- The interaction between the November 2025 DeFi contagion (where curator vaults absorbed substantial losses on opaque-synthetic collateral selections, covered as a separate theme) and institutional-allocator willingness to push tokenised positions into curated-vault wrappers.
- Agentic-commerce posture from the allocator side. As AI-agent-controlled wallets become a credible holder category, whether institutional allocators are willing to permit agent-mediated holdings of tokenised fund interests is the structural extension of the existing allocator-decision discipline.