Ripple Custody now supports the Canton Network, letting institutional clients hold and transfer Canton Coin and CIP-56 tokens inside the custody setup they already run. The update keeps signing keys in each client's own vault and adds safeguards for incoming transfers, though access remains limited to the API for now.
Ripple Custody now supports the Canton Network, letting institutions hold and move Canton assets without leaving the custody platform they already use.
Version 1.43 brings Canton support
The feature arrives in Ripple Custody version 1.43, which launched on October 5, 2026, and lets institutions hold and transfer Canton Coin (CC), also known as Amulet. The release also covers any CIP-56 tokens issued through the Digital Asset (DA) Registry, the token standard for assets created on Canton.
Ripple built the integration on a bring-your-own-validator (BYOV) model, so clients connect the custody platform to validators they, or their node providers, already operate. Signing keys stay in the customer's own custody vault — a hardware security module or a key management service — so Ripple does not hold the keys itself. Existing approval workflows carry over to every Canton transaction, and the release adds pre-approvals for incoming assets plus two-step transfer offers, where a transfer is proposed first and accepted second. Prepared transactions carry a 24-hour signing window before they go stale.
The integration has limits: Canton support works only through the API for now, with no direct support for arbitrary Canton application commands or delivery-versus-payment workflows. It works with both on-premises installations and hybrid SaaS environments.
Why institutions are watching Canton
Canton is a public Layer 1 blockchain that has found favor with regulated financial institutions, offering sub-transaction privacy through a network-of-networks structure in which participant nodes see only the data relevant to them. Major financial institutions including Goldman Sachs and BNY Mellon are using Canton infrastructure for tokenized assets.
What it means for Ripple and its clients
The most direct effect is consolidation. Institutions can now manage Canton assets alongside their other digital holdings without bringing on a separate custodian just for Canton. The BYOV approach lets clients keep their own signing keys while Ripple's platform enforces the rules around approvals and transfers.
Still, the current version has clear boundaries. API-only access means institutions need the technical capacity to integrate, and the lack of DvP and arbitrary application command support keeps more advanced Canton use cases outside the platform for now.
Source: Crypto Briefing
Trading involves risk.
Risk Disclaimer
