Ripple Custody rolled out version 1.43 on October 5, 2026, adding institutional support for the Canton Network and the Canton Coin (CC) token, also known as Amulet. The release lets institutions hold and transfer Canton-denominated assets alongside their existing digital holdings without onboarding a separate custodian.

What does version 1.43 actually do?

The headline capability is custody and transfer of Canton Coin and any CIP-56 tokens issued through the Digital Asset (DA) Registry, the token standard used for assets created on Canton. The update went live through both on-premises installations and hybrid SaaS deployments, but access remains API-only — with no direct support for arbitrary Canton application commands or delivery-versus-payment (DvP) workflows.

How does the BYOV architecture work?

The integration runs on a bring-your-own-validator (BYOV) model. Clients connect the custody platform to validators that they — or their node providers — already operate. Signing keys stay in the customer's own HSM or KMS.

The arrangement means Ripple does not hold the keys authorizing any transaction; institutional clients retain sole signing authority across the deployment. Existing custody policies and approval workflows carry over to every Canton transaction on the platform.

Two operational controls ship alongside the integration: pre-approvals for incoming assets and two-step transfer offers, which require a transaction to be proposed first and accepted before settlement. Prepared transactions carry a 24-hour signing window before they expire, giving compliance teams a full day to review.

Why does Canton matter to regulated finance?

Canton operates as a public Layer 1 blockchain built around what its developers describe as a "network of networks" structure. The architecture offers sub-transaction privacy — participant nodes see only data relevant to their role rather than the full ledger. Major institutions including Goldman Sachs and BNY Mellon already use Canton infrastructure for tokenized asset workflows.

That institutional base is the clearest commercial logic for Ripple's move. Canton has positioned itself as the execution layer for regulated tokenization rather than a general-purpose chain, and Ripple's existing custody roster already spans tokenization issuers, stablecoin operators and licensed custodians.

What are the current limits?

API-only access means institutions need internal engineering capacity to integrate Canton workflows into the platform. The absence of DvP and arbitrary application command support keeps more sophisticated Canton use cases — atomic settlement across asset classes, custom smart-contract interactions — outside the custody product for now.

Ripple has not disclosed a timeline for those features. Operational consequences for clients concentrate on consolidation.

Institutions can now manage Canton assets alongside other tokenized holdings using the same approval workflows, audit trails and signing infrastructure they already operate. For multi-chain tokenization portfolios, that removes one of the historical justifications for retaining a Canton-specific custodian.

The boundary points — DvP, arbitrary application commands, expanded compliance tooling — represent the most likely targets for the next update. Watch for subsequent Ripple Custody release notes: DvP in particular is the connective tissue institutional tokenization desks have been waiting on.