- Europe already tokenizes fund registers. It does not yet put natively issued assets inside fund wrappers. Those two run in opposite directions and almost everyone calls them the same thing. Three things called tokenization →
- The hinge is Article 21(8) of the fund managers directive. A Canton-native instrument most likely lands in the other assets limb, which swaps custody and strict liability for ownership verification. That moves who carries the loss. The hinge →
- The retail fund wrapper is the harder no. On the European regulator's June 2025 advice, the direct list is not expanding, so the only door is a capped bucket. Not one wrapper, not one asset →
- Every Canton claim I have logged at announced tier moves the same way: a tokenized wrapper travelling as bilateral collateral between two consenting counterparties. Not one of them is a fund holding a native asset. The bar, demonstrated →
- My only first-hand European demand signal is negative, dated August 2026, from a service provider desk. The no →
- AIF
- Alternative Investment Fund. Any European collective fund that is not a retail UCITS. Hedge funds, private credit, real estate, most institutional vehicles.
- AIFM
- Alternative Investment Fund Manager. The licensed firm that runs an AIF.
- AIFMD
- The Alternative Investment Fund Managers Directive, 2011/61/EU. The European rulebook for those managers, including the depositary rules this piece turns on.
- UCITS
- Undertakings for Collective Investment in Transferable Securities. The European retail fund standard, sold across borders, with a tightly defined list of what it may hold.
- Depositary
- The independent bank or firm that safekeeps a fund's assets and checks the manager's work. Not a synonym for custodian: a depositary owes duties to the fund and its investors that a custodian does not.
- NAV
- Net Asset Value. The per-share price of a fund, struck by its administrator.
- MiFID II
- Markets in Financial Instruments Directive II, 2014/65/EU. The European rulebook that defines what counts as a financial instrument, and who may trade or safekeep one.
- MiCA
- Markets in Crypto-Assets Regulation, (EU) 2023/1114, also written MiCAR. Covers crypto-assets that are not already financial instruments.
- CASP
- Crypto-Asset Service Provider. The MiCA licence for firms that hold, trade or transfer crypto-assets.
- ESMA
- European Securities and Markets Authority. The EU securities regulator that writes technical advice for the European Commission.
- AMF
- Autorite des marches financiers, the French markets regulator.
- DLT
- Distributed Ledger Technology. The regulator's term for a blockchain.
- MMF
- Money Market Fund. A fund holding short-dated government and bank paper, used as a cash substitute.
- MMFR
- Money Market Fund Regulation, (EU) 2017/1131. The rulebook those funds sit under.
- Repo
- Repurchase agreement. A short-term secured loan: sell a bond now, buy it back shortly after at a set price.
- SICAV
- Societe d'investissement a capital variable. A common European open-ended fund company structure.
- ISDA
- International Swaps and Derivatives Association. Writes the standard contracts used for derivatives and collateral.
- Reg S
- Regulation S, a US securities rule that lets an offer be made outside the United States without SEC registration. It is a carve-out from US law, not a European permission.
- EEA
- European Economic Area. The EU plus Iceland, Liechtenstein and Norway.
- CSD
- Central Securities Depository. The institution where securities are centrally recorded and settled.
- CSDR
- Central Securities Depositories Regulation, (EU) 909/2014.
- Daml
- The smart contract language Canton runs on. A Daml contract decides who can see and hold a given asset.
- RWA
- Real-world asset. A claim on something off-chain, recorded on-chain.
The no
In August 2026 a Dutch fund manager's service provider told me they don't see investor appetite for tokenized investment flow into their funds. Not yet, was the phrasing. I'm not naming the firm.
That's one datapoint and it's the only first-hand European one I have. It's also the one that ends the conversation earliest. At that desk the depositary question never gets asked, because the investor question fails first.
I'm an investor who writes, based in Rotterdam. I'm not a lawyer, not a fund manager, not a depositary. This isn't legal advice, it isn't a rating, and it isn't a route onto this site. Coverage isn't for sale. It's a public position on one question, frozen on the day it publishes.
The useful reader here isn't the service provider. They already know their own chain. It's the issuer or the asset manager holding a Canton-native instrument who can't get a straight answer on depositary, valuation and custody. The service-provider chain shows up in this piece because fluency in it is how you tell a serious wrapper conversation from a pitch.
Why this matters if you hold any Canton exposure: the institutional adoption thesis eventually has to pass through a fund wrapper, because that's where most European capital actually sits. So it's worth knowing exactly where the wrapper stops, and whether the thing blocking it is European law, Canton's own architecture, or nobody asking.
On my read it's the third, then the second. Confirmed activity keeps arriving at the quay. Nothing has cleared customs.
Three things called tokenization
Three different operations get filed under one word, and the difference decides everything downstream.
One. A fund share with a ledger-based register
The fund is conventional. Its assets are conventional. What moved onto a ledger is the shareholder register. This is CONFIRMED and it has happened repeatedly in Europe. Spiko's euro and dollar money market funds are UCITS approved by the French regulator, with a fully tokenized registry, CACEIS as depositary bank and PwC as statutory auditor. In 2026 Spiko and Amundi launched SAFO, a tokenized sub-fund under a French UCITS SICAV, with the register on Ethereum and Stellar, CACEIS again as depositary and administrator, and Chainlink supplying on-chain NAV.
Two. A tokenized claim on a conventional asset
The instrument is a wrapper. Underneath sits something a custodian already holds. CONFIRMED on Canton, more than once, which I get to below.
Three. A natively issued instrument
The ledger entry is the asset. There's no certificate behind it in a vault, no registrar's book that the token mirrors. This is the object in the question.
Almost all European progress is in the first category, and it's real progress. The European Central Bank's April 2026 macroprudential bulletin put tokenized money market funds at roughly a sixth of tokenized financial and physical assets on public blockchains, against a total of about 41 billion euro as at 4 February 2026, and set that against 1.73 trillion euro in money market funds regulated under the MMFR.
Small, growing fast, and pointed the other way from this question. Because the direction is the other way. Spiko didn't get a UCITS to hold a native token. It got a UCITS holding treasury bills to keep its register on a chain. CACEIS still has conventional financial instruments in custody, and PwC still audits against the same evidence it always did. The ledger changed how shares move between investors. It didn't change what the fund owns.
That's the conflation to watch for, and it's in most decks I see. Tokenizing the wrapper is solved in Europe. Putting a native asset inside the wrapper isn't, and the first doesn't get you to the second.
Not one wrapper, not one asset
"European fund" isn't one object, and neither is "Canton-native asset." Both sides of the question are a set, and the pairings fail in different places.
The wrapper side
A UCITS works from a defined eligible-asset list. ESMA's technical advice to the European Commission on the Eligible Assets Directive, published 26 June 2025, is the live signal, and it doesn't expand direct exposures. It proposes a look-through approach for at least 90 percent of the portfolio and permits indirect exposure to alternative assets, crypto among them, inside a capped bucket. That's advice, not law, and the Commission isn't bound by it. But on current direction, a UCITS holding a Canton-native token directly isn't the thing being contemplated. Indirect exposure inside a cap is.
A licensed AIF is where the question actually lives. Wider asset scope, a single independent depositary, and the full Article 21 apparatus.
A registration-regime AIF in the Netherlands sits below the licensing threshold, and parts of that chain aren't required at all. That's not a shortcut for a Canton-native issuance. It's a reminder that anyone offering a single yes for "European fund" isn't offering analysis.
The asset side
MiCA and MiFID II are mutually exclusive over the same token. Article 2(4) of Regulation (EU) 2023/1114 is explicit that crypto-assets qualifying as financial instruments fall out of MiCA, and ESMA's December 2024 guidelines on when a crypto-asset qualifies as a financial instrument are the document national authorities work from. The DLT Pilot Regime, Regulation (EU) 2022/858, amended MiFID II so that instruments issued by means of distributed ledger technology are expressly in scope.
So a natively issued Canton bond is a financial instrument. Safekeeping it is a MiFID II ancillary service, and for an AIF the depositary regime is AIFMD. Not MiCA.
I had this wrong in my own working notes until this piece, and I'd guess a fair number of decks have it wrong too. The reflex is to reach for MiCA whenever a token is involved. For a security-type instrument MiCA steps back by design. An ecosystem token that isn't a financial instrument goes the other way: MiCA applies, custody needs a CASP licence, and for a UCITS the capped bucket is the ceiling.
This is the second conflation. "Canton-native asset" covers a security and a crypto-asset, and they don't fail the same test.
The hinge
Article 21(8) of AIFMD splits the depositary's job in two, and the split is the whole question.
Under limb (a), financial instruments that can be held in custody go into custody: registered in a financial instruments account in the depositary's own books, in segregated accounts in the name of the fund, or physically delivered. The Level 2 regulation narrows it further. A non-physically-deliverable instrument is held in custody where it's a transferable security, money market instrument or fund unit, and it's capable of being registered or held in an account directly or indirectly in the depositary's name.
Under limb (b), everything else is "other assets." There the depositary verifies ownership and maintains a record, based on documents the manager provides and external evidence where it's available.
The two limbs carry different liability. Loss of a financial instrument held in custody triggers near-strict liability with narrow escape. Other assets carry a negligence standard instead.
On Canton, holdings live on participant nodes under contracts that decide who sees what. Whether a depositary can hold a native instrument in its own name, in segregated form, at the ledger level is a question about that instrument's Daml contract. It isn't answered by the network.
If the answer is no, the instrument is other assets. The fund can potentially still hold it, the depositary's duty drops to ownership verification and record-keeping, and the investor loses the strict liability backstop they thought they were buying. That isn't a small print change. It's the reason the wrapper existed.
SPECULATED My read, labelled as read: for most natively issued instruments on a privacy-partitioned ledger, limb (b) is the likelier landing, and nobody has published a memo saying so either way. This section is written from the directive, the Level 2 text and regulator guidance, not from a completed call with a depositary. If a later view has to correct it, the correction will be dated.
What I will and will not recommend
Gates named. Thresholds never. I don't score a wrapper, and I don't recommend a conversation until named things have been published. If a condition below reads like a cutoff, that's a misread. It's a qualitative stop.
Depositary
I don't recommend a wrapper conversation before a depositary that already acts for European funds has published how it treats a natively issued instrument, and specifically which limb of Article 21(8) it lands in. "We're looking at DLT" isn't a published position. Neither is a pilot.
Administration and NAV
I don't recommend a wrapper conversation before the administrator can strike a NAV without the manager marking the book. A liquid instrument with an independent price feed is the easy case. The case that actually arrives has no feed. If the only price is the issuer's, the conversation is early.
Valuation
I don't recommend a wrapper conversation before the valuation function, external valuer or properly separated internal function, has a written method for that instrument that it would show a depositary. Tokenized money-market paper is the easy case. Ecosystem tokens aren't.
Audit
I don't recommend a wrapper conversation before an auditor has an evidence path that isn't a public block explorer. Canton partitions data by design, so there's no global ledger to scrape and no third-party confirmation route that looks like the one an auditor uses for a custody account. The plausible path is participant-node attestation or custodian reporting. I can't find a published audit-firm position accepting it. Untested isn't failed. It also isn't done.
Until those four are published for the specific instrument, I won't recommend that an issuer spend a fund lawyer's time on a wrapper. The conversation worth having instead is the one that produces those publications.
The bar, demonstrated
A view that says "here's my bar" is an assertion. A view that says "here's my bar, here are the claims I published at announced tier, and here's what happened by their review date" is a demonstration. That part is a dated register, not a take.
The register opened on 25 August 2026, so review dates haven't matured and I won't invent outcomes. Three announced entries are open. Open on the review date is itself an outcome: it's the method refusing to promote a press cycle into a confirmed holding.
Vanguard and Wellington, tokenized money market fund shares as collateral on Canton via Nasdaq Calypso
Nasdaq's Roland Chai described tokens representing a direct, legally enforceable interest in the underlying fund shares, with margin calls generated in Calypso and collateral moving on-chain.
The detail worth having is the legal one. The parties amended their bilateral agreements to make tokenized fund shares eligible collateral, following the approach ISDA recommends. That's a contractual fix between two consenting counterparties. A depositary can't take a bilateral fix, because it answers to a supervisor and to every investor in the fund. Also, these are US money market funds, and what got tokenized is the fund share. Category one, moving as category two.
Alpend integrated with Temple's order book
Review date elevated because the source post was never opened directly. An execution venue for collateral management, if it confirms, is infrastructure. It isn't a depositary letter.
Virtu, Tradeweb and M1X, first fully on-chain sovereign-bond repo on Canton
Closest of the three to this question, because USDM1 is natively issued rather than a wrapper, and the counterparties are regulated. The full repo and repurchase cycle settled on Canton in under ten minutes.
Then read the small print, which is where it gets interesting for a European reader. USDM1 is a Marshall Islands sovereign obligation documented under New York law. M1X's own disclosures place it outside the United States under Reg S. Institutional custody is Anchorage Digital, BitGo and tZERO.
Article 21(3) wants a credit institution, a MiFID investment firm with the right permissions and capital, or a grandfathered UCITS-eligible entity. None of those three custodians qualifies. The nearest thing on Canton to the wrapper question is further from a European fund than the headline suggests.
Three announced claims, three open, none of them a regulated European fund holding a Canton-native asset. If that sentence turns up in somebody's round-up, it didn't come from here.
For method rather than for this thesis: Cantex withdrew its Phase 2 limit order book in public and the claim was retained rather than deleted. Musubi moved from announced to confirmed when a primary SBI document appeared. A CertiK guide moved the same way on a primary URL and an approved improvement proposal. That's how the register behaves when the world moves.
Where the EU actually put the door
There's one more piece of evidence a reader deciding whether to take Canton seriously should weigh, and it isn't about Canton.
The EU built a regime specifically for this. The DLT Pilot Regime has applied since 23 March 2023, giving market infrastructures targeted exemptions from MiFID II and CSDR so they can trade and settle DLT financial instruments. ESMA's Article 14 report, published 25 June 2025, found three authorized DLT market infrastructures in the regime's first two years.
ESMA named the bottlenecks as poor interoperability with existing infrastructure, limited access to central bank money, and uncertainty over whether the regime survives at all. It proposed recalibrating thresholds and making the regime permanent.
Three authorizations in two years is the number to sit with. If natively issued instruments were close to arriving inside European regulated structures at scale, this is the venue where it would be visible first, and it's quiet. That cuts both ways, and I'll say so plainly: it's evidence the door is narrow, and it's also evidence the door was built badly, which is roughly what ESMA concluded.
Confirmed and announced don't argue here. They point the same way. The infrastructure question is ahead of the wrapper question, the wrapper question is ahead of the demand question, and the demand question is the one a Dutch desk answered no to in August.
What would have to change
Start from the no, then name what would make the next conversation worth having.
- Demand. Somebody other than the issuer has to want the exposure inside a European wrapper. A service provider seeing no appetite is present tense, not permanent law. When it changes it'll show up as a named manager putting a written question to a depositary, not as a conference panel.
- Depositary. A published memo, from a depositary already acting for European funds, on where a natively issued instrument sits in Article 21(8). Until that exists, an issuer is asking counsel to speculate at counsel's hourly rate.
- Valuation. A price feed, or a written valuation policy for that instrument that doesn't collapse into the manager's own mark.
- Audit. One named audit firm that will take participant-node attestation or custodian reporting as evidence for a Canton holding, publicly, not in a closed pitch.
- Regime. A European Commission decision on whether the DLT Pilot Regime becomes permanent, and on recalibrated thresholds. ESMA has asked. The answer is pending.
None of that is a score. All of it is a publication. When those publications exist, this piece will be wrong in a way I can date, which is the entire reason for freezing it.
Who this is for
If you're a depositary, an administrator, a funds lawyer or a manager platform, this page is a leave-behind, not an invoice. You already live inside the chain above. If a sentence is wrong on your desk, send me the source. Corrections ride the next issue, with your name on them if you want it there.
If you issue or manage a Canton-native asset
The product is a fixed-scope RWA go-to-market memo: this four-gate chain applied to your instrument, evidence-tiered, gaps stated, and what I will and won't recommend. It isn't an open-ended strategy sprint, it isn't a listing, and it isn't legal advice. I'll tell you when you need counsel.
Price isn't on this page. Email hello@cantoncatalyst.xyz with the instrument and the entity, and I'll say within two working days whether I can take it. Conflict with coverage is the usual no. I don't sell research to parties I cover.
Here's what I keep turning over. Every gate above is a document somebody has to sign their name to, and signing is slower than building. So when a depositary finally publishes the custody line, will the constraint still be the depositary, or will it have moved back to the investor who didn't want the flow in the first place?
Sources
- ESMA, Report on the functioning and review of the DLT Pilot Regime, Article 14 of Regulation (EU) 2022/858, 25 June 2025 (esma.europa.eu)
- ESMA, Final Report on Technical Advice on the review of the UCITS Eligible Assets Directive, 26 June 2025 (esma.europa.eu)
- European Banking Authority Single Rulebook Q&A 2021_5864, reproducing AIFMD Article 21(8)(a) and (b) (eba.europa.eu)
- European Central Bank, Macroprudential Bulletin, tokenized money market funds, April 2026 (ecb.europa.eu)
- Spiko, launch of the first tokenized money market funds in the EU (spiko.io); Spiko and Amundi, SAFO (spiko.io)
- Ledger Insights, Vanguard and Wellington test tokenized MMF collateral on Canton via Nasdaq Calypso (ledgerinsights.com); Finadium on Nasdaq's Roland Chai (finadium.com)
- Finadium, Tradeweb and Virtu execute first repo with on-chain sovereign collateral (finadium.com); Regulation S and custody detail (crypto.news)
- Regulation (EU) 2023/1114 (MiCA), Article 2(4); ESMA guidelines on the conditions and criteria for the qualification of crypto-assets as financial instruments, December 2024