DTCC and Digital Asset Test Tokenized Treasuries Through the Collateral Cycle

Digital Asset and the Depository Trust & Clearing Corporation announced on September 23, 2024 that an industry group had completed a pilot using tokenized representations of U.S. Treasury securities as collateral. The project tested more than an ordinary transfer: participants modeled the creation of Treasury “digital twins,” delivery against margin calls, return of collateral and seizure following a hypothetical default.

The exercise was conducted during June and July 2024 on a Canton Network test environment connected to DTCC’s LedgerScan system. Its importance was institutional rather than speculative. The pilot examined whether distributed-ledger applications could coordinate banks, investors, custodians, central counterparties and market infrastructure while preserving the controls expected in regulated securities markets.

Why collateral was the difficult test

Collateral protects a lender or trading counterparty when another party cannot meet an obligation. Moving it efficiently requires more than recording ownership. Systems must establish which assets are available, prevent the same asset from being pledged twice, apply prices and haircuts, document encumbrances and give a secured party enforceable control if a counterparty defaults.

Digital Asset’s report said the pilot immobilized underlying Treasury securities and created corresponding electronic records. Those records were then used in simulated margin workflows. When collateral was delivered, the tokenized Treasury was encumbered and the related registry information updated. When margin was returned, the asset became available for another transaction. In the default scenario, the workflow transferred ownership to secured parties only after required off-chain notices and approvals.

That scope mattered because many blockchain demonstrations stop after issuance or settlement. The September 23 record addressed the less visible legal and operational machinery that determines whether tokenized securities could function as dependable collateral. It did not establish that courts or regulators had approved the design for general use; the legal analysis described how the pilot’s contracts and workflows were intended to fit existing commercial-law concepts.

What the records show

The detailed project report identifies 26 participating organizations, 21 participant nodes, 11 distributed applications and 104 cross-application transactions in a production-like test environment. Its participant categories included four investors, four banks, three custodians or collateral agents, three financial-market-infrastructure organizations, six technology providers and six observers from legal, regulatory, academic and consulting organizations.

The September 23 press release gives a narrower summary: 14 Canton nodes, ten distributed applications and 100 transactions. The surviving records do not reconcile those totals. The defensible conclusion is therefore that more than 100 test transactions were completed across multiple applications; the node and application counts depend on whether the broader report or the public announcement is used.

DTCC’s LedgerScan supplied a consolidated view of ownership, encumbrance and reconciliation across the simulated traditional and digital records. Canton’s synchronization layer coordinated atomic actions between applications while limiting each participant’s access to authorized data. These capabilities were demonstrated in the pilot; they were not independently benchmarked in the published material.

What remained unproven on September 23

The project used TestNet and simulated workflows rather than production transactions carrying disclosed market value. The participants did not publish the face value of the Treasury securities represented, realized cost savings, error rates, transaction latency measurements or a timetable for commercial deployment. No cryptocurrency price or token-market movement can be attributed to the announcement from the cited evidence.

The next questions were whether named institutions would move the workflows into production, whether regulators and courts would accept the intended control and closeout arrangements across relevant jurisdictions, and whether operational benefits would persist at market scale. On September 23, 2024, the pilot was credible evidence of technical and workflow feasibility—not proof of adoption, legal finality or improved market liquidity.