Who Keeps the Register for a Tokenised Luxembourg Fund?
Under the CSSF fund tokenisation FAQ of 2 October 2026, a tokenised Luxembourg fund still needs a UCI administrator to perform the registrar function; appointing a control agent under the Dematerialised Securities Law does not replace it. The control agent is a separate role that must notify the CSSF at least two months before starting and falls within DORA. Plan the register, the control agent and any smart-contract vendor as three distinct workstreams.
TL;DR — Key Takeaways
- ✓Registrar stays: The CSSF says a control agent does not remove the need for a UCI administrator performing the registrar tasks in points (19) and (20) of Circular CSSF 22/811.
- ✓Two roles, two files: The control agent notifies the CSSF at least two months ahead, counted from the CSSF confirming the file is complete. Outsourcing or ICT support adds a three-month notice.
- ✓DORA applies: Control agent entities are within DORA, and the CSSF considers the activity highly likely to be a critical or important function.
- ✓A smart-contract vendor can support the control agent but is an ICT third party, not the control agent or the registrar.

What does the CSSF tokenisation FAQ cover?
The CSSF FAQ on tokenisation, Version 1, was first published on 2 October 2026 and answers six questions in two sections: three on tokenising investment funds and three on the control agent role.
Question 1 confirms that a Luxembourg undertaking for collective investment (UCI) can issue native tokenised units or shares, provided the operating model complies with the framework for that UCI. The units can be registered or dematerialised. For registered units, any UCI administrator (UCIA) performing the registrar function may keep the unitholder register on a distributed ledger (DLT). The CSSF also reminds a UCIA that a substantial change to its operating model for DLT needs CSSF authorisation under point (5) of Circular CSSF 22/811.
“The use of DLT as the issuance and record-keeping infrastructure does not determine the legal form of underlying securities or vice-versa.”
CSSF, FAQ - Tokenisation, Version 1, Question 1
This guide is for fund managers, administrators and depositaries planning a Luxembourg UCI that issues units on DLT. It is not for non-Luxembourg funds, MiCA crypto-assets or secondary trading venues; the FAQ does not address them. The FAQ itself says it is not a complete guide and that the CSSF will update it progressively, so check the version number before relying on it.
Does a control agent replace the fund registrar?
No. Question 2 says the registrar tasks in points (19) and (20) of Circular CSSF 22/811 go beyond the control agent duties in Article 1(10a)(a) to (c) of the Dematerialised Securities Law, so a UCIA must still perform them.
The answer applies whatever the legal form. The CSSF names example entities that can take the registrar role: the investment fund manager (IFM), a registrar agent, or a credit institution authorised as UCIA. That entity performs all the residual registrar tasks the control agent does not cover. One firm may hold both roles only if it holds both permissions. The CSSF example is a credit institution authorised as UCIA that has also notified its intention to operate as control agent under Article 21a of the Dematerialised Securities Law.
“The tasks covered by the UCIA in its registrar function, which are listed in points (19) and (20) of Circular CSSF 22/811, go beyond what is required from a control agent under points (a) to (c) of Article 1(10a) of the Dematerialised Securities Law.”
CSSF, FAQ - Tokenisation, Version 1, Question 2
The US reaches a similar split by a different route: a registered transfer agent keeps the master securityholder file even when the file sits on a blockchain. In both systems the record can move on-chain while the regulated function stays with a named entity. Bermuda points the same way, with the BMA asking that fund documents identify the authoritative legal record for a tokenised fund register.
Can tokenised and traditional units use different registrars?
Yes. Question 3 allows several UCIAs to perform the registrar function for one UCI that issues both tokenised and traditional units, subject to five conditions set by the CSSF.
- No harmful fragmentation. The split must not make coordination and general supervision difficult or impossible, or add cost through unjustified duplication.
- Disclosure. The IFM must disclose the operating model and its risks to investors, and name every UCIA and its function in the offering documents, under point (41) of Circular CSSF 22/811.
- Consolidated view. The IFM or one UCIA must keep a consolidated view of all units issued, so tasks such as NAV per share and distribution or capital call calculations can run.
- Risk management. The IFM or the UCI must manage the extra risks from dividing the registrar function.
- Legal compliance. Where applicable, a register of all registered shares must still be kept at the UCI's registered office, with the content the 1915 Companies Law requires.
Our reading: the consolidated view is the operational test. The token contract records one subset of holders; the traditional register records another. Someone has to sum them every NAV cycle and resolve differences. That is the same reconciliation problem described in the analysis of on-chain golden records and fund register reconciliation, now with a named regulatory owner.
How long does the control agent notification take?
At least two months under Article 21a(2), counted only from the CSSF confirming the notification is complete. Outsourcing or ICT third-party notifications need at least three months, or one month for a Luxembourg support PFS.
Question 4 adds three practical points. The entity presents its operating model to the CSSF before notifying. The CSSF may prohibit the activity if the file lacks the information needed to check Article 21a(1); if it does not prohibit within the period, the entity may start. An entity from another EEA state must first inform its home authority, pass on any objection or comment, and show that the home authority will help the CSSF obtain information. The CSSF treats all of these as conditions for a complete notification.
| Role | Legal source | Permission | Lead time in the FAQ | Can be combined? |
|---|---|---|---|---|
| UCIA, registrar function | Circular CSSF 22/811, points (19) and (20) | UCIA authorisation (e.g. IFM, registrar agent, credit institution) | No period stated; substantial DLT changes need authorisation under point (5) | With control agent, if both permissions are held |
| Control agent | Dematerialised Securities Law, Art. 1(10a) and 21a | Notification to the CSSF | At least 2 months from completeness confirmation | With UCIA, if both permissions are held |
| Outsourcing or ICT third party | Circular CSSF 22/806; Circular CSSF 25/882 | Separate notification by the regulated entity | At least 3 months; 1 month to a Luxembourg support PFS | Supports a role; does not hold it |
| EEA control agent | Art. 21a; Art. 2(10) of the CSSF Law of 23 December 1998 | Home authority informed first | Completeness depends on it | Same rules as above |
An illustrative timeline, not a CSSF estimate: if the control agent file is confirmed complete on 1 February and a smart-contract support arrangement is notified the same day, the earliest control agent start is 1 April, but the ICT arrangement cannot begin before 1 May. The CSSF warns in its introduction that differences between legal delays may affect when to submit the control agent notification. Sequence the ICT notice first.
Does DORA apply to the control agent and its vendors?
Yes. Question 5 says control agent entities fall within DORA under Article 2(1)(a), (e) and (g), and Question 6 says the CSSF considers the activity “highly likely” to be a critical or important function under DORA Article 3(22).
The CSSF bases the DORA position on two Joint ESA Q&As, DORA 136-3193 and DORA 137-3195. The entity must show it has information processing systems, and control and security arrangements for them, suitable for the control agent duties, including by applying its DORA framework to those duties. Question 6 then permits a third party to provide technical support, naming smart contract development and administration as examples. Because the function is likely critical or important, the control agent must notify that ICT arrangement under Circular CSSF 25/882 using the CSSF form for ICT third-party arrangements supporting a critical or important function.
“The CSSF considers it highly likely that the control agent activity qualifies as a critical or important function (CIF) within the meaning of Article 3(22) of DORA.”
CSSF, FAQ - Tokenisation, Version 1, Question 6
An applicant that concludes the activity is not critical or important must tell the CSSF and give a robust rationale before any official notification, when it presents the operating model. The default assumption therefore runs against the applicant.
Which operating models does the FAQ not support?
In our reading, two common pitches do not match the FAQ: treating the token contract as the whole register with no UCIA, and treating the smart-contract vendor as the control agent without its own notification.
These are editorial conclusions from Questions 2 and 6, not CSSF statements about named products. First, a token contract can hold the unitholder record, but a UCIA still performs the registrar tasks and answers for them. Second, a vendor that writes or runs the contract supports the control agent as an ICT third party; the notified control agent stays accountable. Third, where tokenised and traditional units coexist, one entity must hold the consolidated view, so a token ledger cannot be the only source for NAV per share.
A compliance layer such as Blockmaze enforces transfer rules at the token level. It does not replace the UCIA or the control agent. Its job in this model is to keep the on-chain record and the consolidated registrar view reconcilable, with each blocked or approved transfer traceable to a rule. Map those evidence trails into the wider institutional custody and lifecycle compliance controls before the CSSF presentation, not after the notification clock starts.
Sources: CSSF, FAQ - Tokenisation, Version 1 (first publication 2 October 2026), Questions 1 to 6. Sources checked October 29, 2026. The timeline example and the operating-model conclusions are editorial analysis, not CSSF guidance or legal advice.
Frequently Asked Questions
Can a Luxembourg fund issue units only on a blockchain?
Yes. Question 1 of the CSSF tokenisation FAQ says Luxembourg UCIs can issue native units or shares using DLT, provided the operating model complies with the rules for that UCI. The units can be registered or dematerialised under the Law of 10 August 1915 on commercial companies. Using DLT does not decide the legal form, and the legal form does not require or exclude DLT.
Is the smart-contract developer the control agent?
Not by default. The control agent is the entity that notifies the CSSF under Article 21a of the Dematerialised Securities Law. Question 6 lets a control agent use a third party for technical support, such as smart contract development or administration. That provider supports the function; it does not hold it. The arrangement must be notified as ICT support for a critical or important function.
Can one firm act as both registrar and control agent?
Yes, if it holds every permission both roles need. The CSSF example is a credit institution authorised as a UCI administrator under Circular CSSF 22/811 that has also notified its intention to act as control agent under Article 21a. One permission does not cover the other, so each role still needs its own authorisation or notification.
When does the two-month control agent period start?
Only when the CSSF confirms that the notification is complete. Under Question 4, a complete file lets the CSSF check the Article 21a(1) requirements. An EEA entity must also have informed its home authority first and show that the CSSF can obtain information from it. If the CSSF does not prohibit the activity within the period, the entity may start.
Related Articles
Why Did BlackRock Keep the Register Off-Chain?
On 4 August 2026 BlackRock launched 12 tokenised share classes across six Institutional Cash Series money market funds holding $311bn, minted on public Ethereum with Kinexys by J.P. Morgan. The official shareholder register stayed off-chain.
What Is Ireland Asking About Tokenised Funds in DP12?
Central Bank of Ireland Discussion Paper 12 asks 16 questions across four DLT use cases, with investment funds, money market funds and ETFs at the centre. It is a preview of an authorisation checklist, not a tokenisation licence.