Fund Administrator-Supplied Tokenized Share Classes
A fund administrator that already keeps a fund's register can supply its asset-manager clients a tokenized share class as a servicing line - without moving legal title onto a ledger and without bringing the fund inside MiCA.
- Maturity
- Emerging
- Model
- ERC-3643 / T-REX
- Proven stack
- Tokeny (T-REX) · ONCHAINID · Fireblocks · Taurus
- Last verified
- August 2026
Reviewed by Andrei Yurkevich, Founding Member at Protofire
administrators or transfer agents in production for third-party managers, earliest live 21 Jan 2025.
Two headline figures reported at these launches are routinely misread: they are the combined assets of the underlying funds, not of the tokenized share classes. No size figure for the tokenized classes themselves was located - do not infer one.
01. The opportunity
An asset manager wanting a tokenized share class needs three things at once: a token only eligible investors can hold, an identity record that decides eligibility, and a register that still satisfies its depositary and regulator. Most cannot buy those separately, because the register is not theirs to move; it belongs to the transfer agent. This pattern turns that constraint into a servicing line: the administrator that already keeps the register issues the token against it, operates the eligibility rules, reconciles the two, and supplies it to the managers on its book. MiCA does not apply, because a fund unit is a MiFID financial instrument excluded by Art. 2(4)(a), and UCITS, AIFMD, national registrar licensing and DORA apply instead.
The conditions that make this current are recent and datable. The first named administrator-supplied tokenized fund for a third-party manager went live on 21 January 2025. ESMA's guidelines on the qualification of crypto-assets as financial instruments have applied since 17 July 2025 and state that tokenisation does not change classification; Luxembourg's fourth blockchain law of 20 December 2024 extended ledger issuance beyond debt to all securities and created the control-agent role; and the FCA's PS26/7 of April 2026 permits the on-chain record to be the primary books and records of an authorised fund. The legal groundwork now exists in several domiciles, and the servicing capability does not, in most administrators, which is the opening for an administrator that already runs the register.
02. The regulatory position
03. Who's already done this
Fasanara money market token on Polygon PoS using ERC-3643, with Apex as fund administrator and transfer agent and the token layer supplied by Tokeny. The cleanest instance of the pattern and the earliest located: an administrator supplying the whole capability to an external manager. Size is not published.
Tokenized share class of the Coinbase Bitcoin Yield Fund on Base using ERC-3643, Apex as transfer agent and administrator, non-US investors first. Shows the capability repeating on a second client and a second chain. Fund domicile and size are not disclosed.
Twelve tokenized share classes across six existing UCITS money market funds on public Ethereum, with minting confined to fund operating hours and the transfer agent keeping the official register. The largest instance, and the clearest statement of the architecture: the incumbent administrator added the token layer and the transfer agent of record did not change.
Sterling, euro and dollar liquidity funds on Calastone's tokenised distribution network, with token creation, order routing and reconciliation supplied by the network. The variant where the capability comes from a network rather than the administrator - and the transfer agent and administrator are not named in the announcement, which is itself informative about where accountability is being placed.
Apollo Diversified Credit Securitize Fund across six chains, with Securitize named as both digital transfer agent and fund administrator. The furthest version of the pattern: the manager outsourced the register itself rather than buying a token layer from its existing administrator. Useful as the boundary case a European administrator is competing against.
04. Does this fit you?
- Yes for a licensed fund administrator or transfer agent already running a transfer-agency system, KYC and NAV production for external managers, where either a client has asked for a tokenized share class or a competitor has announced one.
- Not for the asset manager rather than the administrator (a different blueprint fits), or where the ledger entry is meant to be the legal register itself rather than a mirror of it (a different, statute-dependent architecture).
05. The stack, layer by layer
Most of these layers can be rented from a named vendor, and usually should be. The part that matters is the one layer you have to own yourself.
The registrar licence and the register itself
The registrar licence or registration and the register itself, onboarding and customer due diligence with investor records, NAV production and the fund accounting chain, and the client relationships with the managers whose funds would be tokenized. The register is what makes this a product rather than a purchase - it is not the manager's to move.
Token contracts, identity and the eligibility engine
Audited token and identity contracts with the issuer and investor applications around them, deployment across the supported chains, and the eligibility engine with its rule modules. Explicitly not included: no register of record, no licence, no customer due diligence, no NAV, no depositary relationship and no key custody. ERC-3643 is open source, so the support attach is the revenue rather than the licence.
The register seam, dual control and two tested exits
The synchronisation to the transfer-agency system in both directions - the chain-facing half is supplied and the register-facing half is not; the daily reconciliation control with an escalation path agreed with the depositary; dual control of the token agent-role keys and the written policy governing their use; out-of-hours detection and response; and two exits tested separately - running the deployed contracts without the provider's applications, and migrating off the issuance chain.
06. Why this stack
- The register stays with the licensed transfer agent, and the token is a synchronised representation of it. That design keeps the fund outside MiCA, because Art. 2(4)(a) excludes financial instruments.
- ERC-3643 (T-REX) enforces eligible-wallet-only transfers by construction, so KYC and eligibility are guaranteed at the contract level.
- The servicing work is identical whether the token is added to an existing share class or issued natively.
Request the full blueprint
This is the short version. The full blueprint is a single document your counsel and board can read cold, and a third-party-risk function can lift wholesale. Leave your work email and your personal link arrives in your inbox.
- The regulatory position, stated article by article
- Proven options at each layer, with the vendors that hold up
- The risk table with a named owner for each risk
- The division of labour: what is rented, built, and operated
- The third-party-risk pack a DORA governance function can lift
- The delivery path, step by step, with the monitoring and incident model
FAQ
Can a fund administrator offer tokenised share classes without moving legal title on-chain or bringing the fund into MiCA?
Yes. In the Fund Administrator-Supplied Tokenized Share Classes pattern, an administrator that already keeps a fund's register supplies its manager clients a tokenised share class as a servicing line without moving legal title onto a ledger. MiCA does not apply, because the fund unit is a MiFID II financial instrument excluded by Art. 2(4)(a); UCITS or AIFMD delegation rules, depositary oversight and DORA apply instead. It uses ERC-3643 / T-REX, and because that standard is open source the support attach is the revenue rather than a licence.
Which administrators already supply tokenised share classes to external managers?
Apex Group supplied the earliest instance, the Fasanara money market token on Polygon PoS using ERC-3643, live 21 January 2025, acting as fund administrator and transfer agent with the token layer from Tokeny, and repeated it for Coinbase Asset Management on Base in March 2026. J.P. Morgan Administration Services (Ireland) tokenised twelve share classes across six UCITS money market funds for BlackRock on public Ethereum on 4 August 2026, the largest instance, with the transfer agent keeping the official register. SS&C Calastone and Securitize run further variants.
What does the administrator own versus rent in this servicing line?
The administrator owns the registrar licence and the register itself, onboarding and customer due diligence, NAV production, and the client relationships with the managers whose funds would be tokenised. It rents audited token and identity contracts, chain deployment and the eligibility engine from providers such as Tokeny (T-REX, ERC-3643), Allfunds Blockchain, J.P. Morgan Kinexys or SS&C Calastone. What it builds is the register-facing synchronisation, the daily reconciliation control agreed with the depositary, dual control of the token agent-role keys, and two separately tested exit paths.
Already evaluating this for your institution?
When you are ready, we scope a business case on your own numbers: the costed build, the controls, the SLA and the ROI your board needs to approve it. Or talk it through first.
Run this pattern in production, or tried to and stopped? .