Version 1.28 is a SaaS release that introduces a new Ripple Custody feature:
- Multi-party computation (MPC) backups
Ripple Custody Version 1.28 introduces the ability for customers to generate a backup of a key-management system (KMS) deployed using multi-party computation (MPC).
Ripple does its own backups for disaster recovery purposes. This feature is for customers who want or require the ability to create their own backups to maintain in their own possession.
To accommodate customer-generated MPC backups, Ripple Custody Version 1.28 introduces the following changes:
- Two scripts are provided by your Ripple liaison to help create and validate backups:
- The backup key-generation script — This script generates both a public encryption key that you will provide to Ripple Custody for creating backups, and a private decryption key that you store in your own KMS separate from Ripple.
- The backup verification script — This script lets you verify the validity of a backup that you have generated and downloaded in JSON form.
- Both the
v0_CreateVaultandv0_UpdateVaultintents now have abackupEncryptionKeyparameter where you can specify the encryption (public) key to use when you request a backup. - Two new intents:
v0_CreateBackuplets you request the generation of a backup to download.v0_AcknowledgeBackuplets you acknowledge the receipt of the backup.
- Three new API operations:
- Get Backup information lets you check the status of a specific backup to know when it is ready for download.
- List Backups lists all pending and processed backups.
- Get Backup trusted entity details lets you download the completed backup.
For more information, see MPC backups.
The 1.28 version will be progressively deployed across SaaS environments starting on October 24, 2025 with production environments scheduled for deployment on December 1, 2025.
Ripple takes great care in testing its applications and ensuring that there are no regressions or breaking changes. Should you experience unexpected behavior, reach out to the Support team by creating a ticket on our Support Portal or contact your Customer Partner Engineer (CPE).