What to Know Ripple Custody version 1.43 adds Canton support, allowing institutions to hold and transfer Canton Coin and eligible CIP-56 tokens securely. Institutions must provide Canton vali
Ripple has added Canton Network support to Ripple Custody version 1.43, enabling institutions to hold and transfer Canton assets. According to Ripple’s documentation, the update supports native Canton Coin and CIP-56 tokens within its existing digital asset custody platform.
Banks and funds can manage these holdings alongside other supported assets, using the same transaction policies and audit records. The release adds custody access to a network that regulated institutions use for tokenization, settlement, and repurchase agreements.
Customers can hold Canton assets through their existing Ripple Custody installation without introducing a separate custodian for those holdings. Access covers on-premises deployments and software customers using Ripple’s hybrid model, with institutions managing Canton through application programming interfaces.
These interfaces provide account management, asset transfers, real-time balances, and indexed transaction histories within the platform’s established custody operations. Institutions must supply a Canton validator themselves or connect through a node provider, as Ripple does not operate that infrastructure.
Ripple Custody connects to the validator and manages accounts while storing their signing keys in the customer’s configured vault. Before signing a transaction, the platform checks its details against approved instructions and applies the institution’s existing custody policies.
Canton Coin, also known as Amulet, pays for network traffic and funds validator rewards within the Canton ecosystem. Separately, the integration supports CIP-56 tokens that issuers publish through the Digital Asset Registry, with customers registering each supported asset.
Also Read: Bitcoin Worth $2.43 Million Moves Toward Kraken After 15 Years of Dormancy
Transfer pre-approvals let institutional accounts receive assets without signing every incoming transaction, supporting cold vaults and longer internal approval processes. Customers can also use two-step transfers, which allow receiving accounts to accept or reject asset offers before completing receipt.
Meanwhile, senders can withdraw outgoing offers when recipients have not acted, providing control over transfers that remain pending. Ripple Custody applies these functions alongside its policy checks, keeping supported Canton movements within the institution’s established approval framework.
The platform also lets customers register Canton development, test, and main networks as separate ledgers within one custody installation. Token issuers remain responsible for deploying their token contracts, while validator operators install and update software for the assets they hold.
Ripple’s documentation assigns those network responsibilities to issuers and operators, while the custody platform handles keys and supported transactions. The release does not support arbitrary Canton application commands or contract deployment, and it excludes CIP-56 allocation workflows.
Additionally, Ripple lists delivery-versus-payment workflows among unsupported functions, defining the integration’s operational scope around asset custody and transfers. Version 1.43 gives institutional customers Canton asset management through Ripple’s custody infrastructure, subject to validator requirements and documented functionality limits.
Also Read: Solana New Addresses Rise 33% as Ethereum and Chainlink Record Limited Growth
The post Ripple Adds Canton Custody Support for Banks Holding Tokenized Assets appeared first on 36Crypto.
