Version 1.14 is a SaaS release and introduces the following new features:
- Custody
For information about distribution and deployment of this version, see Distribution and deployment.
This release introduces the following updates to the Custody functionality.
You can now trade fungible tokens in the XRPL decentralized exchange (DEX) from both the Ripple Custody UI and API.
In on-premise environments, this feature is not enabled by default. To request it, open a new ticket in our Support portal.
This new functionality includes:
- A new XRPL fungible token asset: A unique identifier for each token is created using the issuer and currency code.
- Introduction of the
operationfield in XRPL transaction order intents to encapsulate specific transaction details for the following operations:Payment: Send XRPL tokens and XRP.TrustSet: Create and manage trust lines.AccountSet: Set various account flags useful for trust line management.DepositPreauth: Authorize or unauthorize accounts to send funds.Clawback: Allow token issuers to claw back tokens from accounts.OfferCreate: Create offers on the DEX.
- Updated indexer functionality:
- Enhanced indexing to handle XRPL fungible tokens and related transactions.
- Tracks balance changes for both XRP and fungible tokens.
- Dry run changes:
- Improved error handling to provide specific XRPL transaction result codes for better debugging.
When creating XRPL-specific transaction policies and transaction order intents (operation.type = Payment), do not use the top-level parameters destination, amount, and destinationTag, as these have been deprecated. Instead, use the new operation fields: operation.destination, operation.amount, and (optional) operation.destinationTag. As always, remember to check the Release history and API deprecation regularly for the most up-to-date information about deprecated fields.
For more information, see:
- Manage XRPL tokens in the Ripple Custody UI guide.
- Manage XRPL tokens in the Ripple Custody API guide.
The upgrade will be done progressively starting on September 2, 2024 across the various environments. The production environment will be upgraded last, with a deployment planned on September 16, 2024. This may be delayed, based on customer feedback.
There is no on-premise version of this release.
To ensure you stay up-to-date with the latest API deprecations, end of support for previous versions, and how this might affect your operating model, remember to regularly check the Release history and API deprecation.