DTCC Digital Asset Tokenization
A DTC service enabling the conversion of book-entry securities into on-chain tokenized entitlements for T+0 settlement and automated collateral management under a 2025 SEC No-Action Letter.
Definition
DTCC digital asset tokenization represents a potential evolution of U.S. securities settlement infrastructure — one that extends the existing depository model into blockchain networks rather than replacing it. The Depository Trust & Clearing Corporation, through its subsidiary The Depository Trust Company (DTC), received authorization from the SEC on December 11, 2025 to offer a tokenization service for securities deposited in DTC's book-entry system. The service is designed to convert existing DTC positions into tokenized entitlements — digital representations of UCC Article 8 security entitlements on pre-approved blockchain networks, intended to carry the same legal and economic rights, investor protections, and corporate action treatment as the equivalent traditional book-entry position. The token references the underlying CUSIP as the primary security identifier across both forms.
DTCC's stated long-term ambition is to make over one million securities eligible for deposit at DTC digitally eligible on an opt-in basis — connecting the securities processed annually through DTCC's infrastructure with the emerging on-chain ecosystem. DTCC processed securities transactions valued at approximately $3.7 quadrillion in 2024, with securities deposited at DTC representing tens of trillions in value. The service is designed as an extension of existing market infrastructure, not a displacement of it: firms that participate gain access to extended settlement windows, programmable collateral workflows, and digital asset ecosystem connectivity without surrendering the legal protections and operational resilience that DTC has provided for over 50 years.
The DTC No-Action Letter — scope and significance
The SEC No-Action Letter (NAL), issued December 11, 2025, authorizes DTC to offer a tokenization service on pre-approved L1 and L2 blockchain networks for a three-year pilot period. The NAL is the critical regulatory enabler: it allows DTC to launch the production service more quickly than formal SEC rulemaking would permit, under certain limitations and representations that define the pilot's boundaries. The authorization covers security entitlements — DTC's legal mechanism under UCC Article 8 for holding securities on behalf of participants — not the physical or electronic securities themselves. This distinction matters operationally: tokenized entitlements are not new native digital assets with independent legal status; they are digital representations of existing DTC-held positions, designed to carry the same investor protections and ownership rights that apply under the traditional book-entry framework. The customer protections available through broker-dealer custody rules — including SIPC coverage where a broker-dealer fails — are expected to apply equally to the tokenized form under the NAL's terms.
The NAL covers a defined universe of highly liquid assets including U.S. Treasury bills, bonds, and notes and ETFs tracking major indices, with additional scope defined in the full No-Action Letter. DTC anticipates beginning service rollout in the second half of 2026, with a phased approach that expands scope as the production environment matures. DTCC plans to provide more details on participant onboarding requirements — including wallet registration, the mapping of each participant's DTC Participant number to their on-chain identity, and the approval process for specific L1 and L2 networks — in advance of the launch. The service interacts with NSCC clearing workflows: where tokenization affects the settlement of NSCC-cleared transactions, DTCC's operational specifications will address how the netting and settlement cycle under Rule 15c6-2 (T+1) applies to converted positions.
Tokenized entitlements vs native digital assets — the legal distinction
The term "tokenized entitlement" is precise and operationally important. It distinguishes the DTC service from native digital assets — cryptocurrencies, DeFi tokens, or stablecoins — that are created on-chain without an underlying traditional security. A tokenized entitlement is a digital representation of a security position that already exists in DTC's book-entry system. When a DTC Participant converts a Treasury position into tokenized form, DTC does not issue a new security; it represents an existing DTC-held entitlement in digital form on the blockchain. The legal and economic terms do not change: the coupon payments, maturity terms, default treatment, and ownership rights are identical in both the traditional and tokenized form. Corporate actions — dividends, stock splits, tender offers — are processed by DTC regardless of whether the participant holds the position in traditional or tokenized form.
This distinction has direct compliance implications for broker-dealers. The tokenized entitlement is not a separate security requiring a new ISIN or CUSIP; it is the same UCC Article 8 entitlement held in a different operational form. Rule 17a-3 recordkeeping obligations apply to the conversion event and to the resulting position, using the same CUSIP as the book-entry equivalent. The net capital haircut under Rule 15c3-1 is expected to apply at the underlying security's haircut rate — firms should monitor for potential regulatory adjustments to capital treatment as the pilot develops, as regulators may issue additional guidance on digital-form position treatment. The customer protection reserve formula under Rule 15c3-3 is similarly expected to apply to customer-owned tokenized entitlements regardless of the form of the position. How corporate actions are delivered to positions held in tokenized form — whether to the registered wallet address or through the traditional DTC account — will be governed by DTCC's technical specifications, and broker-dealers should monitor those specifications as they are published.
The conversion mechanism — how securities move between forms
DTCC's conversion mechanism — which uses a retire-and-issue approach referred to in digital asset contexts as burn-and-mint — is the process by which securities move between traditional book-entry form and tokenized entitlement form, with DTC serving as the controlling orchestration layer throughout. The operational sequence for converting to tokenized form is: a DTC Participant submits a conversion order instructing DTC to convert a specified position. DTC retires the traditional book-entry position in its system and simultaneously issues a corresponding token to the participant's registered digital wallet on the pre-approved blockchain. LedgerScan — the ownership-tracking component of DTCC's ComposerX suite — records the conversion event and serves as the authoritative off-chain mirror: in the event of a blockchain consensus failure, hard fork, or network disruption, LedgerScan is the legally binding ownership record that DTC uses to reinstate book-entry positions. This resilience design means the tokenization service does not create single-point-of-failure dependency on any blockchain network's continued operation. Reconversion reverses the process: the participant instructs DTC to retire the token, and DTC reinstates the equivalent book-entry position.
DTCC's design explicitly rejects blockchain bridge architecture. Cross-chain bridges require locking assets on one chain and representing them on another through a third-party smart contract — a model that has been responsible for significant losses in digital asset markets through smart contract exploits. The conversion architecture keeps DTC as the controlling orchestration layer for all form changes: tokens cannot move between chains through third-party bridges; any cross-chain movement requires a new authorized conversion through DTC's mechanism, maintaining the operational control and resilience that anchors traditional markets.
ComposerX and LedgerScan — the technology stack
ComposerX is DTCC's suite of platforms underpinning the tokenization service. It manages the full tokenization workflow: smart contract controls built into each token at the point of minting (including Mint, Burn, Force Transfer, Clawback, Pause/Unpause, and Freeze/Unfreeze capabilities), connectivity between DTC's traditional systems and blockchain networks, and the compliance infrastructure required for participant onboarding and wallet management. DTCC's smart contracts initially incorporate compliance and distribution controls and connect tokenized assets with asset reference data stored on-chain; subsequent releases are planned to enable automation throughout the full trade lifecycle, from issuance to corporate actions.
LedgerScan is the ComposerX component that tracks tokenized ownership in near real time and enables consolidation and harmonization of data from traditional DTC records and blockchain ledgers — creating a single, consolidated view of each participant's position across both forms. For broker-dealers, LedgerScan functions as the authoritative off-chain mirror for tokenized entitlements: it is not merely a viewing tool but the source-of-truth reconciliation record that replaces the manual T+1 position statement for positions held in tokenized form. The Rule 17a-3(a)(5) securities record for tokenized positions is expected to reconcile against LedgerScan, just as the traditional securities record reconciles against the DTC participant account statement. In the event of a blockchain consensus failure or disruption, LedgerScan is the record DTC relies on to reinstate book-entry positions — providing institutional-grade resilience that no bridge-dependent or purely on-chain system can replicate.
DTCC tokenization service — components, function, and 2026 deployment timeline
| Component | Function | Initial Scope | Timeline |
|---|---|---|---|
| No-Action Letter (Dec 2025) | SEC authorization for 3-year tokenization pilot | DTC-custodied securities on pre-approved chains | Active — Dec 11, 2025 |
| ComposerX suite | Tokenization infrastructure — smart contracts, controls, connectivity | Full service platform | H2 2026 launch |
| LedgerScan | Near-real-time ownership tracking — consolidated on-chain + traditional ledger view | All tokenized entitlements | H2 2026 launch |
| Canton Network (Phase 1) | First production blockchain — U.S. Treasury tokenization MVP | DTC-custodied U.S. Treasuries | H1 2026 MVP |
| Expanded asset scope (Phase 2) | Russell 1000 equities + major index ETFs added to eligible universe | 1,000 largest U.S. equities + index ETFs | H2 2026 expansion |
| Long-term target | All 1.4 million DTC-eligible CUSIPs made digitally eligible | Full DTC inventory (opt-in) | Multi-year roadmap |
Operational roadmap — 2026 and beyond
DTCC is deploying the tokenization service in phases. The H1 2026 phase is the minimum viable production environment: a subset of U.S. Treasury securities deposited at DTC will be available in tokenized form on the Canton Network, in a controlled production environment with a limited group of participants. The Canton Network partnership, announced December 17, 2025 alongside Digital Asset Holdings, designates the Canton Network as the initial blockchain partner, with DTCC taking a leadership position in the Canton Foundation's governance structure. The H2 2026 phase is expected to increase scope — expanding the eligible asset universe to additional security types — and to broaden participant access beyond the initial cohort. The long-term roadmap, as publicly described by DTCC leadership, extends to making over one million securities eligible for deposit at DTC digitally eligible on an opt-in basis. Collateral optimization is identified as the first and highest-priority use case: enabling movement of collateral outside standard settlement windows, digital asset collateral workflows, and cross-border collateral mobility. DTCC has also described exploring on-chain netting capabilities through ComposerX — the digital equivalent of NSCC's continuous net settlement — as a way to preserve capital efficiency in a tokenized settlement environment.
The cash settlement leg — tokenized cash and atomic delivery-versus-payment
DTCC's tokenization service provides the tokenized asset leg of a settlement. Achieving simultaneous, irrevocable exchange of the tokenized security and the cash payment — atomic delivery-versus-payment — requires a tokenized cash equivalent on the same blockchain. DTCC has indicated that tokenized cash (via regulated stablecoins or tokenized deposits) is expected to be supported alongside tokenized entitlements. The regulatory framework governing which cash instruments are eligible for securities settlement on blockchain networks is subject to ongoing regulatory development — the SEC has historically required central bank money or regulated clearing assets for securities settlement finality, and participants should monitor how regulators address this requirement in the context of on-chain settlement. A regulated payment stablecoin maintaining a 1:1 dollar peg — such as those expected to operate under the GENIUS Act framework — is a candidate for the settlement cash leg, providing a tokenized cash instrument on the same rail as the tokenized entitlement. This is the infrastructure basis for DTCC CEO Frank La Salla's public commitment to creating a common liquidity pool across traditional and digital markets: the tokenized security and the tokenized cash must reside on the same rail for the extended settlement window and collateral mobility benefits the service is designed to deliver.
DTC tokenization — conversion pipeline
Devancore Glossary · devancore.com
DTC tokenization — conversion pipeline
Devancore Glossary · devancore.com
How it works
1. Participant onboarding — wallet registration and network approval
Before a DTC Participant can use the tokenization service, they must register digital wallets with DTC and obtain approval to operate on specific pre-approved L1 or L2 blockchain networks. DTCC will provide onboarding requirements and the network approval process in advance of the H2 2026 launch. The registered wallet is the destination for tokenized entitlements and the source for reconversions — it is linked to the participant's DTC account and recorded in LedgerScan as the authorized holder. Broker-dealers participating in the pilot must also establish the internal recordkeeping infrastructure to link wallet addresses to account designations and CUSIP records, satisfying the address attribution requirement for Rule 17a-3 blotter compliance.
2. Conversion order — initiating tokenization
When a DTC Participant decides to hold assets in tokenized form, they submit a conversion order to DTC specifying the CUSIP, the quantity, and the registered digital wallet to receive the token. The conversion order is processed through ComposerX: DTC validates that the participant holds the specified position in book-entry form, confirms the target wallet is registered and the target blockchain is pre-approved, and initiates the conversion sequence. DTCC has indicated that conversion and reconversion are designed to be completed within the same business day under normal conditions; specific processing times will be governed by the operational specifications published in advance of the service launch.
3. Burn event — DTC retires the book-entry position
DTC retires (burns) the traditional book-entry position from the participant's DTC account. LedgerScan records the burn event in near real time, updating the consolidated ownership record to reflect that the position no longer exists in traditional form. The participant's DTC account statement no longer shows the position; the on-chain wallet now holds the corresponding tokenized entitlement. The burn is irreversible without a subsequent reconversion instruction — the position cannot exist in both traditional and tokenized form simultaneously. The Rule 17a-3(a)(5) securities record must be updated at the time of the burn event to reflect the position change, posting by T+1 business day per the current standard.
4. Token minted — on-chain delivery to registered wallet
DTC mints the tokenized entitlement on the pre-approved blockchain and delivers it to the participant's registered digital wallet. The token embeds the compliance controls defined in DTCC's smart contracts: Mint, Burn, Force Transfer, Clawback, Pause/Unpause, and Freeze/Unfreeze capabilities are programmed into the token at issuance. The CUSIP is preserved as the asset identifier on-chain alongside the token. The token carries all the same legal rights as the book-entry position it represents: corporate actions (coupon payments, maturities, dividends, tender offers) continue to be processed by DTC regardless of which form the participant holds.
5. Active use — extended settlement windows and digital collateral workflows
Once the tokenized entitlement is in the participant's wallet, the participant can access the benefits DTCC designed the service to enable: extended settlement windows (the token can potentially be transferred or pledged outside standard market hours, subject to counterparty availability and applicable regulatory requirements), collateral mobility (the token can be moved across jurisdictions and time zones without the constraints of traditional settlement windows), and access to on-chain collateral workflows with other participants operating on the same pre-approved network. Collateral optimization is DTCC's primary near-term use case: a participant holding tokenized U.S. Treasuries can use them as digital collateral in repo or securities lending workflows without waiting for traditional clearing infrastructure to open. Where tokenized cash is available on the same network under an approved framework, atomic delivery-versus-payment — simultaneous settlement of the security leg and the cash leg — becomes operationally possible, reducing the settlement risk present in traditional T+1 DvP. The specific counterparty workflows, eligible use cases, and applicable regulatory requirements for each use case will be defined in DTCC's participant documentation.
6. Reconversion — returning to traditional book-entry form
When the participant wants to return to traditional form — to participate in a transaction that requires DTC book-entry delivery, or to access traditional market liquidity — they submit a reconversion instruction to DTC. DTC burns the token from the participant's wallet and reinstates the equivalent book-entry position in the participant's DTC account. LedgerScan records the reconversion event. The traditional position is restored with all the same legal entitlements as before the original conversion. The complete conversion and reconversion cycle — including the LedgerScan event records — constitutes the audit trail for the tokenized entitlement's lifecycle, and must be captured in the firm's Rule 17a-3 blotter and position record as separate transaction events.
Tokenized entitlement — active vs reconverted path
Devancore Glossary · devancore.com
Tokenized entitlement — active vs reconverted path
Devancore Glossary · devancore.com
In Devancore™
Devancore — DTCC tokenization interoperability layer
Devancore Glossary · devancore.com
Devancore functions as the integration layer between DTC's tokenization infrastructure and the firm's internal post-trade operations. Firms entering the DTCC tokenization pilot do not need to rebuild their internal systems — they need an integration layer that maps LedgerScan events to existing recordkeeping workflows, updates the position record and general ledger in real time, and ensures that every conversion order, token issuance, and reconversion is captured in the firm's Rule 17a-3 records, net capital computation, and customer reserve formula from the first day of participation.
Double-entry record automation — CUSIP mapping and Rule 17a-3 compliance
When a DTC Participant converts a position to tokenized form, two records must exist simultaneously: the on-chain tokenized entitlement (visible in LedgerScan) and the firm's internal CUSIP-based securities record. Devancore maintains this mapping automatically. The address attribution layer — the same infrastructure used for digital asset settlement enrichment — links each participant wallet address to the corresponding DTC account and CUSIP, so that every LedgerScan event (burn, mint, reconversion) generates a corresponding update to the firm's Rule 17a-3(a)(5) securities record. The conversion event itself is captured as a Rule 17a-3(a)(1) blotter entry at the time of the conversion order: CUSIP, quantity, wallet address, timestamp, and account designation are all populated from the DTC instruction and the firm's KYC and account records. Firms participating in the DTCC pilot are Rule 17a-3 compliant from day one — the blotter entry exists at the time of each conversion, not as a batch reconstruction at the end of the day.
Lifecycle synchronization — LedgerScan events to internal books
Devancore subscribes to LedgerScan event feeds and processes each conversion, token issuance, and reconversion as a real-time update to the firm's internal position record and general ledger. When DTC retires a book-entry position and issues the corresponding token, Devancore records the position change in the securities record, updates the net capital computation under Rule 15c3-1 to reflect the tokenized position (applying the underlying security's haircut rate, with monitoring for any regulatory adjustments to capital treatment as the pilot matures), and updates the customer reserve formula under Rule 15c3-3 if the position belongs to a customer account. Devancore also treats the conversion event as a non-taxable position change rather than a trade — avoiding false trade alerts in the firm's order management system while still updating the Investment Book of Record to reflect the new form of the position. The conversion event that occurs at the depository level is invisible to the firm's internal books unless the recordkeeping system is integrated with LedgerScan — Devancore provides this integration, ensuring that a conversion processed outside standard market hours is reflected in the firm's position record and net capital computation without a manual update.
The cash settlement leg — stablecoin infrastructure and general ledger automation
DTCC's tokenization service provides the tokenized asset leg. The cash settlement leg — the payment instrument that enables atomic delivery-versus-payment on the same blockchain — is subject to the regulatory framework governing which instruments qualify for securities settlement finality, and firms should monitor how regulators address this requirement as the pilot develops. Devancore's Arc Network integration is designed to support regulated stablecoin payment legs alongside tokenized entitlement transfers: where a regulated payment stablecoin — such as those expected to operate under the GENIUS Act framework — is available and approved for use in a given settlement workflow, Devancore can execute the payment leg simultaneously with the tokenized entitlement transfer. Because a regulated dollar-pegged stablecoin maintains a 1:1 peg through short-term Treasury reserves and cash equivalents, the general ledger entry under Rule 17a-3(a)(2) maps directly from the stablecoin settlement amount to the USD amount — no FX conversion or mark-to-market adjustment required. This accounting neutrality, combined with LedgerScan event capture, means the full audit trail from conversion order through settlement through general ledger posting is maintained in a single, examination-ready record. For firms building toward the common liquidity pool across traditional and digital markets that DTCC CEO Frank La Salla has publicly described, Devancore provides both the asset-leg record mapping and the cash-leg settlement infrastructure designed to operate within the emerging regulatory framework for on-chain securities settlement.
Examination readiness — LedgerScan, the blotter, and the FINRA audit package
For FINRA examinations covering broker-dealer participation in the DTCC tokenization pilot, Devancore produces the complete audit package: the LedgerScan event log (burn, mint, reconversion timestamps and quantities), the corresponding Rule 17a-3 blotter entries linking each event to a CUSIP, account, and wallet address, the maker-checker authorization log for the conversion instruction, and the net capital computation updates reflecting the position in tokenized form. This package satisfies the documentation standard that post-trade regulators are expected to apply to pilot participants: the on-chain record (LedgerScan) and the internal compliance record (blotter + position record) must be reconcilable and examination-ready at all times, not reconstructed after the fact.