Plume announced on Aug. 6 that it had joined the DTCC Digital Assets Solutions Industry Working Group, placing the real world asset network alongside firms such as Charles Schwab, Nasdaq and Alpaca.
- Plume joined DTCC’s tokenization working group alongside Nasdaq, Charles Schwab, Alpaca and other financial firms.
- DTCC’s working group has expanded beyond 100 members and partners ahead of October’s service launch.
- July production trades tested tokenized Treasuries, equities, collateral, securities lending and margin workflows across networks.
- DTC custodies assets worth $114 trillion, but Plume’s membership does not tokenize that entire amount.
- Kimber Transfer Agency’s SEC registration supports Plume’s onchain ownership records for tokenized securities and funds.
The group provides industry feedback on The Depository Trust Company’s tokenization service and helps test the operating standards needed to move traditional securities into tokenized form.
The announcement gives Plume a seat in a group that expanded from more than 50 firms in May to over 100 members and partners by mid-July. However, membership does not mean DTCC selected Plume as a supported blockchain, issued assets through its network or entered a commercial integration. Neither company announced a deployment timetable or contract value.
Plume joins after DTCC completed production trades
DTCC formed the working group to gather input from asset managers, banks, brokers, exchanges, custodians and blockchain companies. Its original public list included BlackRock, Goldman Sachs, JPMorgan, Circle, Robinhood, Ondo Finance, Nasdaq and Charles Schwab. Plume was not named in the May list, but its official announcement says it has now joined the expanded group.
The timing follows DTCC’s July 15 production event. More than 30 firms used DTC-held securities in live tokenized transactions on LFDT’s private Besu network and the public Canton network. The tests covered collateral pledges, securities lending, Treasury repo delivery versus payment, equity settlement, token transfers and central counterparty margin workflows.
Plume was not named among the firms that participated in those July transactions. Its membership therefore appears to have started after the production event, although Plume and DTCC have not disclosed the exact admission date or the workstreams it will support. This timing is an inference based on the two public announcements.
As previously reported in earlier DTCC tokenization coverage, the group was created to review technical workflows, market readiness and interoperability before the service entered wider production.
DTCC tokenization service targets an October launch
DTCC plans to launch the service in October 2026. It will allow DTC participants to create tokenized representations, sometimes called digital twins, of eligible securities held in DTC custody. Participants will be able to deliver those representations to approved wallets and convert assets between traditional and tokenized records.
The service operates under a three-year SEC no-action letter issued in December 2025. The authorized asset set includes Russell 1000 shares, exchange traded funds tracking major indexes and U.S. Treasury bills, notes and bonds. SEC Commissioner Hester Peirce described the program as a limited pilot and said DTC’s official books would track transfers between registered participant wallets.
DTC held assets valued at more than $114 trillion at the end of 2025, while DTCC subsidiaries processed $4.7 quadrillion in securities transactions during the year. Those figures describe DTCC’s wider market infrastructure. They do not mean the entire $114 trillion custody base will become tokenized when the service launches.
In related coverage, DTCC plans to connect the service to Stellar during the first half of 2027. The July production event used Besu and Canton, showing that DTCC is pursuing a multichain structure rather than committing the service to one network.
The development was covered further in a Stellar tokenization update, which examined the planned expansion to a public blockchain.
Plume brings regulated recordkeeping experience
Plume said it intends to contribute expertise in compliance standards. The network says it uses compliance partners, transaction controls and built-in anti-money laundering tools for tokenized assets. These are company descriptions of its infrastructure, not an independent finding that every transaction or product complies with applicable law.
Its clearer U.S. credential comes through Kimber Transfer Agency. An SEC filing shows Plume Network Inc. owns 100% of Kimber’s voting securities. Kimber’s transfer agent registration became effective on Sept. 26, 2025, allowing it to carry out registered transfer agent functions subject to federal requirements.
Transfer agents maintain issuer ownership records, process changes in ownership and support distributions. Plume says Kimber can maintain both onchain and offchain shareholder records for tokenized securities. SEC registration does not amount to an endorsement of Plume, its network or any investment product.
As crypto.news reported in Plume transfer agent coverage, the company has positioned Kimber as a bridge between blockchain ownership records and established U.S. market infrastructure.
What happens next before the full rollout
The immediate deadline is DTCC’s planned October launch. Working group members are expected to continue reviewing operating practices, technical workflows and interoperability. DTCC has not published a Plume-specific task, network connection or tokenized asset launch.
Plume cofounder Chris Yin said the collaboration could help “bring global markets onchain.” The statement is forward looking. Its outcome depends on regulation, participant adoption, technical integration and whether issuers choose tokenized formats.
After October, attention will shift to production volume, supported assets, wallet participation and the networks selected for expansion. Stellar connectivity is targeted for the first half of 2027, while the SEC no-action position runs for three years under stated conditions.
For Plume, the clearest near-term measure will be whether working group participation produces a formal DTCC integration or new issuer relationships. Until either company announces such an arrangement, the development should be treated as an advisory role in the service’s design rather than a confirmed deployment on Plume.
