Did Ripple Custody add support for Canton Coin and the Canton Network in version 1.43, released October 5, 2026?

The full answer

What Ripple’s documentation says version 1.43 adds

Ripple Custody version 1.43 adds support for Canton Coin and CIP-56 tokens on the Canton Network, according to Ripple’s own documentation. As of October 13, 2026, the Canton page says support “is available from version 1.43,” for on-premises deployments and, through a hybrid model, for SaaS customers [1]. The same documentation lists v1.43 as an LTS version [1].

Ripple says the product custodies Canton Coin and CIP-56 tokens on a validator that the customer or its node provider operates [1]. Customers hold and transfer Canton Coin (also called Amulet) and CIP-56 tokens issued through the Digital Asset (DA) Registry. Ripple Custody keeps each account’s signing key in the customer’s vault and checks every transaction against its approved intent before signing [1].

Which Canton assets and features are covered

The documentation names two asset types: Canton Coin, and any CIP-56 token that the DA Registry publishes [1]. A few working details stand out:

• Transfer pre-approvals let accounts receive assets without signing each incoming transfer, which Ripple says makes Canton work with cold vaults and long approval flows [1].
• DevNet, TestNet and MainNet can each be registered as a separate ledger in one installation [1].
• A single transfer can spend at most 100 Holdings, Canton’s unit of balance [1].

In this release, customers manage Canton through the Ripple Custody API [1]. Ripple describes no user-interface route for it.

What the release does not do

As of October 13, 2026, Ripple lists its own exclusions for the release. Customers can’t use Canton-native applications, sign arbitrary Daml commands or deploy contracts. CIP-56 allocation and delivery-versus-payment (DvP) workflows aren’t supported. Ripple does not operate a validator for customers; bringing your own validator is the only hosting model [1].

Those limits are the strongest reason not to read more into the update. The feature covers safekeeping and transfers. It does not cover trade settlement on Canton, which is where Ripple itself says much institutional activity on the network happens.

Whether Canton is now part of the XRP Ledger

It isn’t. Ripple’s documentation describes Canton as “the public Layer 1 network that many regulated institutions use for tokenization, settlement, and repo,” reached through a validator the customer runs [1]. Ripple’s pitch is that customers keep Canton assets in the same custody platform, policy engine and audit trail they use for other ledgers [1]. Nothing on the page ties the feature to XRP or to the XRP Ledger. Readers asking whether tokenization work like this creates demand for the token can see whether tokenization on the XRP Ledger needs XRP.

What Canton Coin is

The Canton Network’s FAQ calls Canton Coin “the network’s native utility token” [2]. Its FAQ document says the coin pays traffic fees across the Global Synchronizer [3]. Digital Asset’s July 2024 paper adds that users pay fees denominated in US dollars, using Canton Coin [4]. The same paper says Canton Coin is optional: node operators can prepay traffic with it or have a third party set up a traffic balance, much like a phone data plan paid in fiat [4].

How this fits the wider custody and settlement picture

Custody support is one layer. Trading, settlement and collateral movement sit on top of it, and version 1.43 leaves DvP out [1]. The gap between infrastructure and working markets is covered in what tokenized markets need, and the record of earlier Ripple and XRPL announcements is tracked in whether XRPL institutional announcements are becoming live products. For a view of what moves crypto prices beyond product news, see the page on the US inflation and jobs reports that crypto commentators cite.