What Is Ireland Asking About Tokenised Funds in DP12?
Central Bank of Ireland Discussion Paper 12 is a consultation framework for DLT and tokenisation, not permission to launch a tokenised fund. Published on 5 March 2026, it sets out four use cases and 16 questions, with a particular focus on investment funds, money market funds and ETFs. Because Ireland is the European Union's largest fund domicile, the questions point to the evidence a manager will need on governance, custody, valuation, transfer agency, resilience, interoperability and investor protection before an Irish tokenised UCITS can reach the market.
TL;DR — Key Takeaways
- ✓The Paper: Central Bank of Ireland Discussion Paper 12, published 5 March 2026, on DLT and tokenisation in financial services.
- ✓The Scope: Four use cases and 16 questions across markets, investment funds, money and payments.
- ✓Fund Focus: Investment funds, including money market funds and ETFs, receive a dedicated part of the consultation.
- ✓The Deadline: Stakeholder responses were due 5 June 2026; the Bank intends to publish a feedback statement.
- ✓The Practical Read: DP12 is a preview of an authorisation checklist, not a tokenisation licence or a replacement for UCITS controls.

A Discussion Paper With a Product Perimeter
DP12 asks how tokenisation should fit inside Ireland's existing financial-services perimeter. It does not approve a tokenised fund, but its questions reveal what a manager will need to prove before asking for authorisation.
The Central Bank published the paper on 5 March 2026 and closed responses on 5 June 2026. It said a feedback statement would follow, covering some or all of the issues raised. That makes the consultation a live policy input, not a settled rulebook.
DLT and tokenisation can transform finance, but “technology, in and of itself, will not be sufficient.”
— Vasileios Madouros, Central Bank of Ireland, 5 March 2026
That sentence is the paper's centre of gravity. A tokenised UCITS still needs a legal owner, a depositary, a reliable NAV, an accountable transfer agent and investor protections. DLT is the mechanism to examine, not the answer to those obligations.
Sixteen Questions, Four Use Cases
The paper turns broad interest in tokenisation into four use cases and 16 questions. The structure matters because the Central Bank is asking for evidence across an operating model rather than evaluating a chain in isolation.
| Question group | What a manager must be ready to explain |
|---|---|
| Legal and regulatory | What the token is, which rules apply and who is accountable |
| Fund operations | NAV, register, transfer agency, depositary and reconciliation |
| Technology and resilience | Scalability, cyber risk, outages, upgrades, outsourcing and recovery |
| Market and investor outcomes | Liquidity, interoperability, costs, disclosures and suitability |
The fund use case sits beside markets and payments, so a submission that focuses only on token transfer misses the paper's cross-system questions. Ireland wants to know how a ledger interacts with the intermediaries already responsible for the product.
Why Ireland's Fund Domicile Changes the Weight of the Questions
Ireland's role as the European Union's largest fund domicile gives DP12 practical force beyond a normal discussion paper. A future Irish tokenised UCITS will be supervised in the same ecosystem that already approves fund managers, depositaries and transfer agents at scale.
That does not make the Central Bank a single EU tokenisation regulator. It does mean that its feedback will shape the route a manager, administrator and depositary must take in one of Europe's deepest fund markets. A manager building for Ireland is downstream of the consultation even if its investors sit elsewhere in the EU.
The commercial implication is sequencing: decide the fund jurisdiction and service-provider stack before choosing the ledger. The same architecture that works for a permissioned US fund may not satisfy Irish governance or depositary expectations.
The Fund Questions Are Really Register Questions
For a tokenised fund, the hardest questions are who owns the share, which record controls, who can correct an error and how a transfer agent reconciles wallets with the official register. DP12 puts those questions beside the technology rather than after it.
A ledger balance is easy to display. It is harder to make it legally authoritative while preserving investor identity, transfer restrictions, sanctions controls, valuation, corporate actions and a recoverable error path. The manager needs a written reconciliation policy and a clear answer for every disagreement between ledger, administrator and depositary.
The same boundary appears in BlackRock's European tokenised share classes, where the token is visible on-chain but the legal register remains an explicit operating choice.
Resilience and Interoperability Are Authorisation Issues
DP12 treats operational resilience, scalability and interoperability as enabling conditions, not engineering polish. A manager must show what happens when the network halts, a provider changes, a wallet is compromised or an investor needs to exit through a conventional channel.
Interoperability also has a legal side. A token that bridges to another chain can change who controls the record, where a restriction is enforced and which service provider is responsible for a failed transfer. A two-chain diagram is therefore a governance diagram as much as a technical one.
The Central Bank is examining “legal and regulatory clarity, operational resilience and scalability, and interoperability.”
— Central Bank of Ireland DP12 overview
This is why a manager should write recovery and portability requirements before selecting a vendor. If the fund cannot continue serving investors after a ledger outage, the ledger is not an acceptable production dependency.
Turn DP12 Into a Pre-Application Checklist
A manager can use DP12 as a pre-application checklist while waiting for the feedback statement. The objective is not to guess the final rule; it is to make every dependency visible and configurable.
- Define the token's legal nature and the official ownership record.
- Assign depositary, transfer-agent, administrator and key-control responsibilities.
- Document NAV, valuation, corporate-action and ledger-reconciliation controls.
- Set wallet eligibility, transfer restrictions and investor-disclosure rules.
- Test outages, upgrades, vendor replacement, bridge failure and conventional exit.
- Map how the structure works across UCITS, AML, DLT and data-protection requirements.
DP12 does not say which chain Ireland will prefer. It says, more usefully, that the chain will be only one part of the decision. The winning application will make the legal, operational and investor-protection story as precise as the token transfer.
Frequently Asked Questions
What is Discussion Paper 12?
Discussion Paper 12 is the Central Bank of Ireland's March 2026 paper on distributed ledger technology and tokenisation in financial services. It presents four use cases and 16 consultation questions covering markets, investment funds, money and payments. It is a policy discussion document, not an authorisation or a regulatory exemption for tokenised funds.
When did the Central Bank of Ireland publish DP12?
The Central Bank published DP12 on 5 March 2026 and invited responses by 5 June 2026. The Bank said it intends to publish a feedback statement covering some or all of the topics raised. As of 12 September 2026, the paper remains the key public statement of the questions Ireland wants answered.
Why does DP12 matter for tokenised UCITS?
Ireland is the European Union's largest fund domicile, so the Central Bank's supervisory expectations shape the practical route for an Irish tokenised UCITS. DP12 asks how DLT interacts with existing fund governance, custody, valuation, transfer agency, operational resilience and investor protection. A future application will need answers to those questions even if the final rules use different terminology.
How many use cases and questions does DP12 contain?
The paper examines four detailed use cases and asks 16 questions for stakeholders. The use cases span tokenisation in markets, investment funds including money market funds and ETFs, and money and payments. The questions are open-ended: the Central Bank is gathering evidence rather than prescribing one blockchain architecture.
Does DP12 permit a fund to issue tokens today?
No. DP12 does not approve tokenised fund shares, replace UCITS requirements or make a distributed ledger the official ownership record. It asks how existing legal and supervisory obligations would apply. A manager still needs the appropriate fund, depositary, transfer-agent, custody and investor-disclosure arrangements before launching a product.
What should a manager submit or prepare after DP12?
A manager should map the full operating model: the legal nature of the token, the official register, wallet eligibility, transfer restrictions, valuation and NAV controls, depositary oversight, cyber and outsourcing risks, business continuity, investor disclosures and cross-border distribution. The paper's questions can be used as a pre-application checklist while the feedback statement is pending.
Related Articles
Can an ETF Put Its Shares On-Chain Without New Relief?
A US filing that exposes the same register and custody questions.
Can a Tokenized MMF Legally Trade 24/7 at $1?
A US order focused on intraday pricing and dealer liquidity.
Why Did BlackRock Keep the Register Off-Chain?
A European fund structure that keeps the legal record explicit.
How Do Tokenized Funds Use ERC-7540 Async Vaults?
The settlement-standard question behind tokenized fund flows.