What changed—and what stayed put
DTCC’s July 15 production event was not a stock exchange moving onto a public blockchain. It happened deeper in the market, after a buyer and seller have agreed to trade and the system must make ownership, payment, custody, and risk records line up.
The Depository Trust Company, a DTCC subsidiary, already holds securities and records entitlements for banks and broker-dealers. In the new workflow, an eligible position could be moved from its conventional form into a digital representation. That token could then travel to an approved wallet and participate in an on-chain transaction.
The underlying security did not leave DTC custody. DTCC describes the token as a digital twin of a DTC-held asset, with the same ownership rights, entitlements, and investor protections as the traditional position. The important change was the rail used to record and move that entitlement.
That distinction prevents two common misunderstandings. These were not tokens that merely followed a stock’s price, and they were not bearer assets that anyone could move anonymously. They belonged to a permissioned institutional process tied to DTC’s official records.
How a conventional position becomes a token
Imagine a bank has an eligible ETF position credited to its DTC account. The bank sends a conversion instruction. DTC must confirm that the participant, asset, wallet, network, and requested action meet the service’s rules.
The SEC staff’s December 2025 no-action letter describes the accounting: DTC debits the participant’s conventional position and credits a digital omnibus account, then delivers a corresponding token to the registered wallet. Converting back burns the token and restores the conventional position. The underlying securities remain registered to DTC’s nominee; the token records the participant’s entitlement.
The debit and credit are the key safeguard in this description: the participant’s conventional position is reduced when the corresponding token is issued. Conversion is an accounting movement, not a second copy available to spend alongside the first. Burning the token on conversion back closes the reverse path. The security stays in custody while the representation of the participant’s entitlement changes.
What institutions did with the tokens
DTCC’s announcement lists collateral pledges, securities lending, U.S. Treasury repo delivery-versus-payment, equity delivery-versus-payment, equity delivery-versus-delivery, token transfers, and central-counterparty margin workflows.
Delivery-versus-payment is a useful example. In a conventional transaction, the security and the cash travel through coordinated processes. Each side wants assurance that it will not deliver while the other side fails. A digital workflow can connect the two legs more tightly, so the asset moves only when the payment condition is satisfied.
That is often described as atomic settlement. “Atomic” concerns whether the linked legs succeed together; “instantaneous” concerns how quickly they finish. A transaction can be conditional on both legs without eliminating the time needed to fund, approve, or submit it. The BIS analysis of securities settlement explains why a shorter cycle can reduce some exposures while increasing immediate liquidity needs. Institutions still have to arrange the cash and securities required to settle. A technically immediate transfer is not automatically the safest design for every market.
Collateral illustrates another benefit. A bank may need to pledge an asset to secure an obligation. A controlled token can make the asset’s status and movement easier to coordinate across systems. The collateral does not become more valuable; the plumbing around it can become less fragmented.
Why multiple blockchains mattered
The conversions took place on LF Decentralized Trust’s Besu technology in DTCC’s private environment and on Canton, a public network designed for institutional finance. This was therefore also an interoperability exercise.
A multi-chain strategy gives participants choices, but it creates a hard bookkeeping problem: the system must prevent duplicate claims, preserve a consistent record, and know which network and protocol are authoritative for each movement. Bridges and messaging layers do not eliminate trust; they relocate it into technical rules, governance, monitoring, and recovery procedures.
DTCC’s role is precisely why this event carried more weight than an isolated pilot. The organization already sits inside the market’s post-trade machinery, and the transactions used real production assets with a broad group of market participants. The event was also bounded in time and scope. It demonstrated live capability ahead of the planned service launch; it did not prove that every security or workflow is ready to move on-chain.
The control layer does not disappear
Regulated securities must handle court orders, sanctions, lost credentials, mistaken transfers, corporate actions, and operational failures. A design that treats every transaction as irreversible would collide with those obligations.
Approved participants and wallets therefore remain central. The SEC letter describes wallet screening, controlled transfers, monitoring, and the ability to correct lost tokens or erroneous entries. Its staff no-action position is limited to the stated facts and specified rules; it is not a blanket legal endorsement of every tokenization arrangement.
Those controls may disappoint anyone expecting permissionless finance. They are also what makes the tokens usable as regulated securities entitlements rather than look-alike digital assets.
What the milestone actually means
The production trades showed that tokenization can be inserted into existing market infrastructure without pretending the rest of the market has vanished. Custody, legal rights, participant checks, and operational responsibility remained. The new layer made the entitlement portable across approved digital workflows.
The next test is whether the record stays consistent when a network fails, a transfer needs correction, or many participants need cash at once. The July event demonstrates that the workflow ran with production assets. Reliability across those harder conditions requires evidence beyond a successful coordinated event. For the separate question of what a token holder can actually claim, see our guide to tokenized assets, custody and redemption.
Visual guide
How the pieces fit together
