DTCC said on May 4 that it plans to facilitate initial, limited production trades using DTC’s tokenization service in July, followed by a service launch in October 2026. More than 50 financial firms are contributing to the development work.

The announcement gives a staged timetable for moving DTC-custodied assets into tokenized form. It does not say that all securities held at DTC are already available on blockchains.

Existing ownership rights are part of the design

DTCC says the service is intended to preserve the entitlements, investor protections and ownership rights associated with assets held in their traditional form.

That is a central requirement for institutional tokenization. Changing the record or transfer technology should not leave an investor guessing whether the token carries the same rights as the security it represents.

The working group includes custodians, asset managers, brokers, trading venues and infrastructure providers. Named participants range from banks and established market firms to blockchain-focused businesses, reflecting the number of operational systems that must connect.

DTCC says the group will help test technical and operational workflows, including how tokenized assets can work across different chains. A successful transfer alone is not the whole post-trade process; custody records and asset servicing also need to remain coherent.

Limited production comes before the broader launch

The July milestone is explicitly described as initial and limited. The October date is a plan for the service launch, not an already completed event.

DTCC also points to a December 2025 SEC no-action letter covering a defined service for DTC participants and their clients over three years. It describes eligible assets including Russell 1000 constituents, certain index ETFs and U.S. Treasury securities.

That defined scope should not be expanded into a claim that every security or tokenization model has regulatory clearance. The eligible asset set and service conditions remain relevant.

The May update is useful because it identifies both the next production step and the broader target date, while leaving room for the implementation work still to be completed.