Version 1.12 introduces the following new features:
- Operation traceability
- Custody
- Ledger management
- Additional platform enhancements
- User experience
- Branding updates
For information about distribution and deployment of this version, see Distribution and deployment.
We have introduced the following new fields to improve traceability of operations.
You can now provide a reason when you approve an intent in the API, UI, or app.
For an example of the API payload change, see Approve an intent.
The following information is now included in the GenesisSucceeded event:
- A
genesisfield, which includes the original, Genesis operation payload. The payload is signed by the notary. This field is only available for new installations of v1.12. - A
createdEntitiesReferencesfield, which is a list of all entities created in the root domain by the Genesis operation. This is available in all environments.
For an example, see Genesis event.
You can now specify a list of ledgers when you create an account.
We now support Polygon Amoy mainnet.
We now support Stellar testnet stellar-testnet-june-2024.
We have improved our customer deployment experience with Ripple now deploying, hosting, and maintaining the Ripple Custody Governance components.
This release includes the following improvements to the Harmonize UI.
The Harmonize UI now displays the governing strategy for a domain.
BTC fee management information is now available using a tooltip in the UI.
Harmonize is becoming Ripple Custody! Look out for branding changes to the product and documentation in the coming months.
The upgrade will be done progressively starting on 01/07/2024 across the various environments. The production environment will be upgraded last, with a deployment planned on 15/07/2024. This may be delayed, based on customer feedback.
Version 1.12 will be available for our on-premise customers to download and install from 28/06/2024. The usual process of pulling the containers from Ripple’s repository using the 1.12.1 tag applies.
As with all new releases, this version triggers the deprecation of the previous version (v.1.11.x), which will continue to be supported for the next 6 months, unless specified otherwise in the master contract with Ripple. For more information about versioning, see Versioning and release management.
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.
The configuration of new functionalities can sometimes present technical challenges and require the support of our team: reach out to us if you need any technical assistance on our ticketing portal.