● Tokenized money market funds are the fastest-growing corner of institutional real-world asset tokenization. Ondo Finance reports its OUSG product has passed $770 million in total value locked, spread across Ethereum, Solana, Ripple, and Polygon.● Launching one comes down to five infrastructure decisions: which blockchain, which issuance partner or platform, how custody integrates, how KYC/AML and compliance workflows hold up under the SEC and MiCA, and which jurisdictions you cover.● Vendors are sorted into three categories. Productized issuance platforms like Securitize and Ondo, compliance-standard infrastructure like Tokeny's ERC-3643, and development partners like Restart Fintech for custom builds.● The deciding question is build versus buy, based on how standard or bespoke your fund structure is. The closing checklist walks through it.

Why tokenized money market funds are scaling faster than other RWA categories

Tokenized money market funds have pulled ahead of every other real-world asset category because the demand behind them comes from a regulatory mandate, not from speculation. Ondo Finance reports that its OUSG product has grown past $770 million in total value locked, a figure worth reading as a company claim rather than an independently verified number. The scale of the segment holds up against outside data. Callan and Everstake both estimate that on-chain tokenized real-world assets reached roughly $30 to $31 billion by mid-2026, with U.S. Treasuries and money market funds accounting for about half of that total.

The GENIUS Act, enacted in July 2025, explains why tokenized Treasuries dominate that half. The law permits payment stablecoin issuers to hold tokenized money market fund shares as reserve assets, and stablecoin issuers collectively back more than $300 billion in outstanding tokens. Each of those issuers now needs a compliant reserve vehicle that settles on the same chains their tokens live on. A tokenized fund holding short-dated Treasuries and overnight repos fits that requirement almost exactly, which turns every large stablecoin into a structural buyer of on-chain fund shares.

That demand pull shows up in who is launching. J.P. Morgan Asset Management built its JLTXX fund, announced in May 2026, specifically to serve stablecoin reserve holders under the GENIUS Act, investing only in Treasuries and fully collateralized repos. J.P. Morgan committed $100 million at launch, with Anchorage Digital participating alongside it. When a bank of that size stands up a public-Ethereum fund for a named regulatory use case, the market has moved past pilots.

For an asset manager, that shift raises the stakes on the infrastructure choices that follow. You are no longer deciding whether tokenized funds work. You are deciding how to build one that satisfies reserve buyers, custodians, and regulators at the same time, and the rest of this guide breaks those decisions down in order.

The five infrastructure decisions every launch requires

Launching a tokenized money market fund comes down to five decisions you make in sequence, and each one constrains the next. First, you pick a blockchain, or more often a set of them, since the largest 2026 funds issue across multiple chains from a single legal wrapper. Second, you choose how to issue, either through a productized platform or a custom build. Third, you integrate custody, which the EU treats as its own regulated activity under MiCA. Fourth, you design the KYC/AML and compliance workflows that gate who can hold your tokens and enforce transfer restrictions at the protocol level. Fifth, you map your jurisdictional coverage, because a token compliant under SEC rules may not qualify for distribution under MiCA.

The rest of this guide works through each decision in order, then places the vendors against them.

Choosing a blockchain: Ethereum, multi-chain, and permissioned alternatives

Ethereum still anchors the largest institutional launches, but the funds scaling fastest in 2026 no longer treat chain selection as a single choice. J.P. Morgan Asset Management launched JLTXX on public Ethereum in May 2026, following its earlier MONY private placement fund, also on Ethereum (JPMorgan press release). Franklin Templeton's BENJI shows where that starting point leads. It began on Stellar in 2021 and by 2026 had expanded across Polygon, Canton, Ethereum, Arbitrum, Base, Aptos, Avalanche, and Solana (Everstake).

Multi-chain issuance from one legal fund wrapper wins because it widens distribution without fragmenting the fund itself. Public-chain deployment lets fund administrators reach more channels, and it lets stablecoin issuers hold the tokens directly as GENIUS-compliant reserves (Everstake). Adding a chain extends where shares can circulate while the underlying fund and its share register stay singular.

Permissioned networks like Canton and Kinexys solve a narrower problem. They restrict access at the network level, which suits participants who want a closed settlement venue rather than open public distribution. In practice, both appear as secondary networks inside multi-chain deployments rather than as a fund's primary venue. Hashnote and Circle's USYC, for example, settles across Ethereum, Canton, and Solana. The tradeoff is real. A permissioned chain shrinks your potential holder base to whoever the operator admits, which undercuts the distribution logic driving public-chain launches.

Chain choice and compliance enforcement resolve as one decision, not two. On public chains, transfer restrictions live in the token contract itself. A transfer agent runs KYC and sanctions screening, then adds a cleared wallet to an on-chain allow list, and the smart contract enforces holder caps, jurisdiction filters, and freeze functions on every transfer (Everstake). ERC-3643 is the dominant standard for encoding that logic, with ERC-1400 as an alternative. Because those controls travel with the token, a fund can deploy the same compliant token across several chains without rebuilding its restrictions each time.

Going multi-chain adds one further requirement. Cross-chain settlement depends on institutional-grade validator infrastructure across Ethereum, Solana, and Polygon, and messaging protocols like CCIP, LayerZero, and Wormhole now count as core fund infrastructure rather than optional extras (Everstake). Decide your allow-list and bridging model at the same time you pick chains, because retrofitting either after launch means reissuing the token.

Custody integration and why it's not a bolt-on decision

Decide custody architecture at the same time you choose your chain and design your compliance logic, because all three constrain each other. A custodian has to hold the private keys that control your fund's tokens, and those keys live on whatever blockchain you selected. If your compliance model relies on allow-listed wallets and freeze functions, the custodian's wallet infrastructure has to support those controls natively. Bolt custody on last, and you discover the custodian cannot enforce the transfer restrictions your smart contracts assume.

MiCA sets the regulatory floor, and it is specific. It treats custody and administration of crypto-assets as a distinct regulated activity, and authorized custodians must keep client positions in a register and maintain legal and operational segregation of client crypto-assets from the custodian's own estate. A custodian can be held liable to your investors for loss of assets or loss of access when the loss is attributable to the custodian. That liability standard shapes which providers will even take your fund, so treat it as a gating question during vendor selection rather than a contract detail settled afterward.

Custody concentration is the diligence point most launch teams underweight. A large share of tokenized fund assets currently sits with a small number of qualified custodians and transfer agents, which creates outsized counterparty risk for any single fund relying on one of them. Map your custody exposure the way you would map any concentrated counterparty. Ask whether the custodian supports your target chains, whether their segregation model satisfies MiCA, and whether a failure at that one provider would freeze investor redemptions across your entire fund.

Building KYC/AML and compliance workflows that satisfy SEC and MiCA

The most durable compliance design for a tokenized fund puts eligibility checks inside the token itself rather than relying only on an off-chain gate. The ERC-3643 standard, stewarded by Tokeny, does this through ONCHAINID, a decentralized identity framework that links each investor to an on-chain identity carrying cryptographic claims such as verified KYC status. Before any transfer executes, the contract checks both sender and receiver against jurisdictional restrictions, accreditation, and sanctions screening. If an investor moves to a restricted jurisdiction, the issuer can revoke access through the identity registry in real time.

Regulators on both sides of the Atlantic effectively demand this enforcement, even if they don't name the mechanism. In the EU, MiCA requires full customer due diligence, continuous transaction monitoring with prompt suspicious-activity filing to the national Financial Intelligence Unit, and Travel Rule compliance under the Transfer of Funds Regulation. Since December 2024, every crypto-asset transfer must carry full originator and beneficiary data with no minimum threshold, so a fund's transfer logic has to capture and transmit that data on every movement. ESMA has also directed providers to restrict services involving non-compliant tokens, which maps directly onto the transfer-restriction and whitelisting logic a fund's smart contracts enforce.

The US picture centers on the SEC rather than a single crypto statute, and the sourcing here is thinner. Reg D and Reg S offerings turn on investor accreditation and geographic eligibility, which is exactly the kind of rule ONCHAINID claims can encode at the wallet level. The SEC's Custody Rule pushes fund assets toward a qualified custodian, a requirement you handle alongside on-chain controls rather than instead of them. Treat the US layer as an area needing counsel-specific validation, not something a protocol standard resolves on its own.

The July 1, 2026, MiCA transitional deadline turns this from a design preference into a hard schedule for any EU-facing launch. National transitional windows for existing crypto-asset service providers close entirely on that date, and any provider without MiCA authorization must stop operating in the EU regardless of where the firm is headquartered. Penalties reach up to 12.5% of global annual turnover for serious violations, with personal liability possible for executives. If you plan to distribute to EU investors, the custody, CDD, and transfer-restriction workflows have to be authorized and operating before that window shuts.

The vendor landscape: three categories, not one list

The vendors serving tokenized money market funds are split into three groups, and confusing them leads asset managers to buy the wrong thing. Productized issuance platforms package the full fund lifecycle into a template you configure. Compliance-standard infrastructure supplies the protocol layer that enforces investor eligibility inside the token itself. Development and implementation partners build custom infrastructure for funds for which no template fits. Each group solves a different part of the launch, and a single vendor rarely covers all three well.

Productized issuance platforms: Securitize and Ondo Finance

Securitize and Ondo Finance offer the fastest path to market when your fund structure fits a standard template. Securitize consolidates four regulated functions that fund distribution normally spreads across separate intermediaries. It operates as an SEC-registered transfer agent maintaining the official ownership record, a broker-dealer handling issuance and onboarding, an alternative trading system for secondary trading, and a fund administrator running NAV and reporting (Mercuryo). An asset manager plugging into that stack inherits the regulatory plumbing instead of assembling it.

BlackRock BUIDL shows what productized issuance delivers at scale. Launched in March 2024 on Securitize's infrastructure, the fund grew to roughly $2.3 billion in assets, and BlackRock has since filed with the SEC for a second tokenized fund on the same stack (Securitize). BUIDL now runs across Ethereum, Solana, Polygon, Avalanche, and several other chains, so the platform handles multi-chain deployment without the manager rebuilding compliance per network.

Ondo Finance takes a narrower position as the cash-management specialist. OUSG holds a diversified basket of institutional tokenized Treasury funds and aggregates their liquidity through Ondo Nexus, which extends 24/7 subscriptions and redemptions to third-party fund holders as well. Ondo reports OUSG surpassing $770 million in total value locked, a company-stated figure rather than an independently verified one (Ondo Finance). If your goal is a liquid, multi-chain cash-management product that interoperates with existing tokenized Treasury funds, Ondo's model is purpose-built for it.

Both platforms trade structural flexibility for speed. A template optimized for the common case handles standard investor classes, common jurisdictions, and conventional redemption mechanics cleanly, and it struggles when your fund departs from those defaults. An unusual feeder structure, a jurisdictional footprint the platform does not support, or investor eligibility rules that fall outside its onboarding logic will run into the limits of what a configurable product can bend to. That constraint is exactly where a custom build earns its place, which the Restart Fintech entry below covers.

Compliance-standard infrastructure: Tokeny and ERC-3643

Tokeny sells the compliance rail your fund runs on, not the platform that issues and operates the fund. The Luxembourg firm authored ERC-3643, the permissioned-token standard originally called T-REX and now the only tokenized-securities standard formally accepted as an Ethereum ERC. More than $32 billion in assets have been tokenized using it, which is why so many issuance platforms and issuers build on top of it rather than inventing their own compliance logic.

The mechanism that makes ERC-3643 useful for a regulated fund is ONCHAINID, its claims-based identity framework. Each investor holds an on-chain identity carrying cryptographic claims such as verified KYC status, issued by trusted parties. Before any transfer executes, the token checks both sender and receiver against jurisdictional restrictions, accreditation rules, and sanctions screening. Compliance lives inside the token itself, so if an investor moves to a restricted jurisdiction, Chainalysis notes the issuer can revoke or update access in real time through the identity registry. An ERC-20 token offers none of that. It was built for open, pseudonymous transfers, which is exactly what a securities regulator will not permit.

Here is the distinction that matters for your launch. Choosing Tokeny and ERC-3643 settles which compliance standard your token enforces. It does not settle who designs, builds, and runs the rest of the stack. The standard is deliberately modular and multi-chain, and Hedera integrated it into its Asset Tokenization Studio in November 2025 for cross-border, non-US issuance. A productized platform can adopt it, a custom build can adopt it, and both still owe you everything else. That means custody integration, NAV and redemption mechanics, and jurisdiction-specific workflows. Treat the standards decision and the build-and-operate decision as two separate line items, because a vendor that gives you one does not automatically give you the other.

Development and implementation partner: Restart Fintech

Restart Fintech builds the fund infrastructure that productized platforms and standards layers cannot, because your fund does not fit a template. Securitize and Ondo work best when your structure matches what their stack already supports. The moment your fund carries an unusual redemption schedule, a mixed investor base across three jurisdictions, or eligibility rules that a standard whitelist cannot express, you need infrastructure designed around your fund rather than a template you bend your fund to fit. Restart Fintech operates as your fractional CTO and custom-build partner, so you get the engineering depth of an in-house blockchain team without carrying that team on payroll.

The three infrastructure decisions this guide treats as hard problems are the ones Restart Fintech is built to handle. On custody, Restart Fintech designs the integration between your qualified custodians and your on-chain records so that MiCA's segregation and liability requirements hold at the protocol level, not just on paper. On KYC/AML, Restart Fintech architects the onboarding, transaction-monitoring, and allow-list workflows that feed your smart contracts, mapping full CDD, ongoing monitoring, and Travel Rule data capture into the wallet-eligibility logic your fund enforces on-chain. Each workflow is designed against the specific rulebooks your investor base triggers, not a generic compliance module.

Multi-jurisdiction coverage is where a bespoke build earns its cost. A token compliant under U.S. rules may not qualify for distribution in the EU under MiCA, which forces parallel legal opinions and parallel enforcement logic for a cross-border holder base. Restart Fintech builds infrastructure that carries MiCA obligations, Swiss DLT Act requirements, and SEC-related considerations such as qualified-custodian and Reg D/Reg S accreditation logic inside one coherent system, rather than stitching together separate tools per jurisdiction. For a fundraising from EU, Swiss, and U.S. investors under one legal wrapper, that unified design is the difference between a launch that survives regulatory scrutiny and one that fragments under it.

Choose Restart Fintech when your fund is bespoke enough that a standard platform would cost you more in workarounds than a custom build costs outright. If your structure, footprint, and eligibility rules match a template, the productized platforms are faster and cheaper. If they do not, a partner who designs your custody, compliance, and multi-chain architecture as one system for regulated institutional RWA infrastructure is the option that actually gets your fund to market.

Launch decision checklist: what to lock down before you build

Work through these five questions in order before you commit to a vendor, because each answer narrows the field, and the last one decides everything.

1. NAV and redemption mechanics. Decide how often you strike NAV and how redemptions settle. A fund that publishes intraday NAV and offers same-day redemption needs an issuance stack wired to a fund administrator and a settlement path that clears in hours, not days. Securitize handles this natively through its fund-administration layer. A bespoke redemption waterfall, tiered by investor class, usually does not fit that template.

2. Custody integration depth. Confirm whether your custodian plugs into the token contract directly or sits behind a manual reconciliation step. MiCA requires legal and operational segregation of client crypto-assets from the custodian's own estate, and it holds the custodian liable for losses attributable to it. Ask how the allow-list updates when the custodian adds or freezes a wallet, and whether that logic lives on-chain.

3. Jurisdictional regulatory coverage. Map your investor base to the rules that bind it. A token compliant under U.S. Reg D may not qualify for EU distribution under MiCA, which forces parallel legal opinions. If you sell into both the U.S. and the EU, you need onboarding that segments investors by jurisdiction and a compliance stack that enforces SEC accreditation logic and MiCA CDD side by side.

4. Blockchain and interoperability. Choose your legal wrapper first, then decide which chains it deploys to. The largest 2026 funds issue multi-chain from one wrapper, anchored on Ethereum, and treat bridging protocols like CCIP and LayerZero as core infrastructure. Lock down which chains you launch on and which you can add later without re-papering the fund.

5. Build versus buy. This question decides which of the three vendor categories applies. If your fund structure, redemption terms, and investor eligibility rules fit a standard template, a productized platform like Securitize or Ondo Finance gets you to market faster. If your structure, jurisdictional footprint, or eligibility rules break the template, you need custom infrastructure, and a development partner like Restart Fintech becomes the right fit. Answer this honestly first. The other four decisions follow from it.

FAQs