Tokenization & RWA
On 28 October 2026, DTCC announced the production launch of the DTCC Tokenization Service, operated by The Depository Trust Company (DTC), a central securities depository in the United States.
This is a significant development, but not because it proves that tokenization has become a market standard. The service has a defined scope, specific operating conditions and outcomes that remain to be assessed.
What interests me most is how tokenization is being integrated into an existing financial market infrastructure. The token is not treated as a standalone technology component, but as part of a system of records, rights and controls that must continue to function after its introduction.
That distinction matters for financial institutions and banks evaluating tokenization projects.
What DTCC Announced
The service allows eligible DTC participants to obtain tokenized representations of their positions in securities held at DTC and convert them back into traditional book-entry form. The legal distinction matters.
Registered ownership of the underlying securities is not simply transferred onto a blockchain. The service concerns security entitlements: participants’ rights in relation to securities held through the custody system. The underlying securities remain registered in the name of Cede & Co., DTC’s nominee.
DTCC describes these representations as digital twins, retaining the economic rights and investor protections associated with traditional positions.
The service operates within the scope of the SEC staff no-action letter issued in December 2025.
Initially eligible assets include selected Russell 1000 equities, ETFs tracking major indices and US Treasury securities.
The service initially supports Canton Network and a private Besu-based network, with additional networks planned for 2027. Twenty DTC participants have signed access agreements, including major international financial institutions.
Three Questions for Evaluating Tokenization Projects
The issue is not simply whether a security can be represented by a token. It is how that representation connects to the underlying rights and the processes that preserve their continuity.
First: which records have legal standing?
When positions can be held in traditional or tokenized form, institutions need to understand which records are official, how they are coordinated and what happens when discrepancies arise.
Under DTC’s model, positions are moved by book entry into a digital omnibus account, while LedgerScan records token movements. The LedgerScan records for tokenized positions form part of DTC’s official books and records.
This is not necessarily a traditional ledger taking precedence over a subordinate digital copy. It is an architecture in which different records must remain consistent and legally effective.
For a financial institution, that matters at least as much as the ability to issue a token.
Second: how is conversion governed?
DTCC provides for conversion between tokenized entitlements and traditional book-entry positions through accounting movements and token minting or burning.
The question is not simply whether conversion is technically possible. Who can request it? Which controls apply? When does it take effect? What evidence remains available?
Not every project requires two convertible forms. Some instruments are issued directly in digital form. But where conversion is part of the design, the reverse process must also be evaluated.
Issuing a token is only one part of managing the rights it represents.
Third: how are networks and operational continuity managed?
The service initially supports two networks, with others planned. This does not establish that positions can already move freely between networks or that migration would be risk-free.
It does, however, highlight why DLT infrastructure must be assessed alongside operational controls.
What requirements must a network satisfy? How are transfer restrictions enforced? Who responds when something goes wrong? And how would records and rights be preserved if the underlying infrastructure needed to change?
These questions shift attention from today’s technology choice to the project’s ability to operate over time.
What This Development Does Not Prove
The 28 October announcement describes the service’s launch and scope, but does not provide sufficient quantitative results to assess its economic impact.
Greater liquidity, collateral mobility and capital efficiency are potential benefits identified by DTCC, not outcomes already demonstrated by the newly launched service. Signing an access agreement does not necessarily mean a participant is actively using it.
The SEC staff no-action letter applies to specified activities and conditions. It is not a general regulatory approval of securities tokenization and covers a limited three-year period from launch.
Nor does the absence of quantitative results in the October announcement mean that there were no earlier operational milestones. In July 2026, DTCC had already reported production transactions involving DTC-tokenized assets.
The initial scope remains limited to selected categories of securities within an established custody framework. It would be premature to assume that real estate, interests in privately held companies or other real-world assets would follow the same path. Their ownership structures, documentation, restrictions and responsibilities may differ substantially.
The regulatory context also matters. DTC operates within the US framework. In the European Union, financial instruments are governed by the applicable securities framework, including MiFID II, while MiCAR applies to crypto-assets within its scope.
What Changes for Project Evaluation
I do not see this announcement as evidence that the market has settled on a definitive technology or operating model.
It illustrates something more practical: when established market infrastructure adopts tokenization, it must accommodate digital representations within a system where rights, records, controls and responsibilities already have defined functions.
For banks and issuers, evaluating a tokenization platform therefore involves more than asking whether it can represent an asset digitally. It requires understanding how that representation fits into the legal and operational structure, which records have legal effect, who is accountable for critical processes and how continuity is maintained.
The same questions can inform the evaluation of other asset classes without assuming that DTC’s architecture is universally applicable. The answers will depend on the rights involved, the parties and the transaction structure.
The DTCC case does not establish a universal standard. It does, however, reinforce an important principle: the quality of a tokenization project depends not only on its ability to create digital representations of rights, but also on how those representations integrate with the processes and responsibilities through which those rights are exercised.
In my view, this is where the evaluation of institutional tokenization will become increasingly rigorous.
What does this development change for your organisation?
