# Ripple Custody 1.29 (December 5, 2025)

Version 1.29 is a SaaS release that introduces two new Ripple Custody features:

- UTXO allowlisting via the UI
- HSM backups


## Unspent transaction output (UTXO) allowlisting via the UI

Version 1.29 contains the UI release of our new UTXO change address strategy. This feature supports the critical operational needs of financial institutions by allowing transaction change from assets like Bitcoin (BTC) to be sent to a consistent, primary address.

Previously, Ripple Custody followed the standard BIP32 convention of generating a new change address for every UTXO transaction. Now, when you propose an intent to create a transaction or transfer, you can send any leftover funds (the unspent "change") back to the first-ever generated address in the wallet, i.e. the `PrimaryAddress`.

### Key benefits

- **Simplified address allowlisting**: By sending change to a single, predictable primary address, you can now easily allowlist this address with counterparties and for regulatory purposes.
- **Reliable internal transfers**: This new strategy ensures that outgoing transactions always originate from the same address (once UTXOs are consolidated), allowing for reliable validation of internal transfers across different domains.
- **Instance-wide control**: In v1.29, you can enable this behavior on a per-instance basis via a new feature flag `HMZ_FEATURE_USE_PRIMARY_FOR_CHANGE`. Contact your CPE for more information.


### Migration best practice: consolidating existing UTXOs

If you are enabling this feature on an **existing instance** that has already processed Bitcoin transactions, your current funds are likely distributed across multiple historically generated change addresses.

To fully realize the benefits of a single allowlisted address, you must consolidate your funds:

Note:
Before or immediately after enabling this feature, perform a **UTXO consolidation**. Select all UTXOs currently residing in previous change addresses and transfer them to your main `PrimaryAddress`. This ensures that all future change output originates from and returns to your single, allowlisted address. Contact your CPE for help with UTXO consolidation.

## Hardware security module (HSM) backups

Ripple Custody Version 1.29 introduces the ability for customers to generate backups of the wrapped seeds for key-management systems (KMS) deployed using a hardware security module (HSM).

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 HSM backups, Ripple Custody Version 1.29 introduces the following changes:

* Two intents now support creation ofHSM backups:
  * `v0_CreateBackup` lets you request the generation of a backup to download.
  * `v0_AcknowledgeBackup` lets you acknowledge the receipt of the backup.
* Three API operations now support retrieval of HSM backups:
  * [**Get Backup information**](/products/custody/v1.34/api/reference/openapi/backups/getbackup) lets you check the status of a specific backup to know when it is ready for download.
  * [**List Backups**](/products/custody/v1.34/api/reference/openapi/backups/getbackups) lists all pending and processed backups.
  * [**Get Backup trusted entity details**](/products/custody/v1.34/api/reference/openapi/backups/getbackuptrustedentity) lets you download the completed backup.


Important:
You must execute these backup operations from the *root domain*.

## Distribution and deployment

The 1.29 version will be progressively deployed across SaaS environments starting on December 5, 2025 with production environments scheduled for deployment on December 12, 2025.

### Activation and support

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](https://metaco.atlassian.net/servicedesk/customer/portal/1) or contact your Customer Partner Engineer (CPE).