Tokenisation needs an exit-cost test, not just a faster transfer

On November 2, 2026, the Central Bank of Ireland published feedback on its distributed-ledger and tokenisation consultation, alongside its next work programme. This is a development from this week, not a new November 7 announcement. Official release

The important question is not how many more assets can be issued as tokens. It is whether a project removes friction across a business process's entire life. Open Market Notes argues that normal transactions, exception handling and eventual migration must be costed together. Making the first faster does not establish that the whole system is better. The mechanisms and hypothetical examples below are our analysis, not reported pilot results.

An engagement route is not an operating licence

The planned Tokenisation Access Point, or TAP, offers a route to discuss emerging models, implementation and the application of existing rules. Programme page

A single contact point could reduce the expense of explaining the same architecture to different teams. But discussion is not product approval or an endorsement of a chain or asset. A firm still needs questions precise enough to receive useful answers.

Consider a hypothetical fund recording units on a shared ledger. Its transfer mechanism is only the beginning. Which record governs if the ledger and fund register disagree? Who handles an erroneous transfer? How does an investor establish entitlement after losing a key? Who maintains records if the supplier exits? These are illustrative diligence questions, not allegations about a particular project.

If several institutions must reconcile everything off-chain afterwards, digitisation may improve the entrance without eliminating coordination later. Conversely, clearly assigned human exception handling can be safer than a superficially automatic process without accountable recovery. The presence of manual work does not itself negate a technology's benefits.

Settlement conditions define what speed means

In its November 5 speech, the ECB described Pontes as connecting market DLT platforms with TARGET Services for wholesale settlement in central bank money, and Appia as longer-term ecosystem design. ECB speech

That distinction suggests a useful test: time asset movement, completed payment and the ability to reuse funds separately. Suppose a securities ledger updates within seconds but a payment institution has not finished its own processing. A fast confirmation for the buyer is not necessarily spendable funds for the seller. This is not an assessment of Pontes performance; it is a generic test for settlement arrangements.

Faster delivery also does not automatically mean less funding. A design requiring both parties to provide cash and securities before every trade may reduce waiting risk while increasing preparation costs. A design that batches activity might economise on funds while adding coordination time. Comparisons need the same scale, operating window and failure scenarios, not just the fastest demonstration.

An August 28 BIS speech argued for different forms of money in one unit to be redeemable at par into central bank money with finality. BIS speech This is a policy position, not a guarantee that every tokenised product operates without risk.

Our more user-centred question follows: what can the recipient actually do next? An asset transferable only within a closed network has different utility from one usable across payment and collateral processes. Completion should be tested against the user's next obligation, rather than defined solely by a successful interface message.

Include the cost of leaving

Ireland's feedback document says evidence remains limited on tokenisation models' commercial viability and resilience under stress. DP12 feedback

Limited evidence does not make a project worthless. It means a successful pilot cannot establish that every participant has an incentive to migrate. An issuer might save administration while a custodian takes on integration work; a supplier might earn more while investors receive no fee reduction. Benefits should be assigned to their recipients rather than credited collectively to one product.

An overlooked case is one in which two networks work perfectly but a customer wants to change providers. If departure requires fresh identity checks, conversion of assets, new legal documents and confirmation from the old system, some everyday savings may be surrendered at migration. Portability therefore includes accepted records, continuous rights and a workable handover of responsibility, not just compatible software.

There are competing reasonable readings. Supporters may regard duplicate systems as transition costs that disappear with scale. Sceptics may expect more participants to increase interface and governance complexity, preserving duplication. It is too early to declare either universally correct. Track whether old processes are actually retired, and how exceptions are handled after retirement.

The next evidence should be operational

More persuasive progress would be repeated outcomes over time: lower total processing costs for comparable transactions, recovery times after failure, manual work to add participants, and complete records available to departing customers. These are our proposed evaluation measures, not a uniform supervisory scorecard already imposed by the central bank.

Ireland's engagement programme is an observation point, and European settlement work is relevant context. Neither replaces a firm's business case. Researchers should separate policy plans, operational capabilities and measured benefits. Only sustained, verifiable evidence about the latter two can move the discussion beyond issuance totals to whose work improves and who remains responsible for risk.