A broader operational toolkit

Ripple Custody’s version 1.43 release notes, dated October 5, add support for Canton, Circle’s Arc network and Sui. The long-term support release covers both SaaS and on-premises deployments. It also brings XRP Ledger multi-purpose token operations into the user interface, expanding what operators can manage without relying exclusively on API integrations.

The documentation makes availability distinctions that matter. Canton requires the relevant accounting update and a validator operated by the customer or its provider; in this release it is managed through the API. Sui management is also API-only. Support for a network is therefore a specific operational capability, not a promise that every feature is available through every deployment model or interface.

Custody is more than storage

Institutional custody involves deciding who can authorize an action, recording what happened and coordinating transfers with other systems. Adding a network can require changes to accounting, transaction formats and approval procedures. A familiar platform can help organize that work, but each integration still has its own requirements.

Our analysis is that broader support could reduce the need to operate separate processes for every asset environment. The potential benefit comes from consistent controls and records across networks. It does not follow that the networks themselves become interchangeable, or that their settlement and asset models have identical characteristics.

Interfaces expose policy decisions

The new multi-purpose token interface includes issuer actions such as authorization, freezing and clawback. These are meaningful control features. An asset holder needs to understand the rules attached to a token, while an issuer needs procedures governing when its powers can be exercised.

Making an operation easier to perform does not decide when it is appropriate. Organizations still need permissions, review and clear records. The release notes also flag integration and deployment changes for customers upgrading from older versions, underscoring that operational readiness includes reviewing existing systems before adopting new capabilities.

The practical test will be how customers use the expanded toolkit in live processes. Useful evidence would include supported workflows, dependable reconciliation and documented responsibilities across the custody arrangement. For the wider tokenization market, the release is an infrastructure development rather than proof of immediate demand. It adds tools for managing assets across several networks, while the value of those tools depends on the financial products and operational controls built around them.

Source: https://docs.ripple.com/products/custody/support/change-history/v143