Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
XRP Ripple Custody version 1.43 adds support for the Canton Network
Ripple Custody version 1.43 officially adds support for the Canton Network, allowing organizations to securely hold and transfer Canton Coin and eligible CIP-56 tokens. In this update, institutions will need to provide a Canton verification node, while Ripple Custody will manage account keys, transaction approvals, balances and history through its existing infrastructure.
Core Functions and Compliance Controls
This release provides managed access services to networks used by regulated agencies in scenarios such as tokenization, settlement and repurchase agreements. Banks and funds can use the same trading strategies and audit records to manage such assets with other supporting assets. Customers can hold Canton assets through existing Ripple Custody deployments without introducing additional custodians.
This support covers on-premises deployment and software customers using Ripple's Hybrid Model, where organizations can manage Canton assets through application programming interfaces (APIs). These interfaces provide functions such as account management, asset transfer, real-time balance query, and indexed transaction history within the platform's established custody operation framework.
Technical architecture and division of responsibilities
To be clear, Ripple does not operate Canton's infrastructure. Organizations must provide their own Canton verification nodes or connect through a node provider. Ripple Custody is responsible for connecting to the authentication node and managing accounts, while storing the signature key in a customer-configured vault. Before signing a transaction, the platform will check the transaction details based on approved instructions and apply the institution's existing custody policies.
Canton Coin (also known as Amulet) is used to pay for network traffic and fund verifier rewards. In addition, integrated support for CIP-56 tokens issued by issuers through the digital asset registry, customers need to register each supported asset.
Transfer approval and operation boundaries
In order to enhance institutional control, the platform has introduced a "transfer pre-approval" function, allowing institutional accounts to receive assets without having to sign every incoming transaction, which helps support cold wallet storage and a longer internal approval process. At the same time, the "two-step transfer" mechanism allows the receiving account to accept or reject the asset offer before completing the receipt; if the receiving party fails to take action, the sender can also withdraw the pending outgoing offer.
Ripple Custody combines these features with its policy checks to ensure that supported Canton asset flows comply with the institution's established approval framework. In addition, customers can register Canton's development network, test network, and main network as separate ledgers in a managed installation instance.
Unsupported Function Range
The document clearly states that the token issuer remains responsible for deploying its token contracts, and the verifier operator is responsible for installing and updating software for the assets it holds. Ripple's managed platform handles only key management and supported transactions, is irresponsible for Canton application command or contract deployment, and does not support CIP-56 distribution workflows.
In addition, the Delivery-versus-Payment (DVP) workflow is also listed as an unsupported feature. This shows that the operational scope of this integration is strictly limited to the fields of asset custody and transfer. 1.43 Version enables institutional customers to manage Canton assets through Ripple's managed infrastructure, but only meets verifier requirements and follows the functional limitations specified in the document.
