# Ripple Custody 1.21 (June 30, 2025)

Version 1.21 is a SaaS release and introduces MPC key management and a new API operation for searching for ledger addresses across accounts and domains.

## Multi-party Computation (MPC) key management

The Multi-Party Computation (MPC) key-management option, initially introduced as a closed beta with limited functionalities (for example, no derivation capabilities) in Ripple Custody v1.16, is now available.

To guarantee a smooth integration of this new technology within our ecosystem, only selected customers are being onboarded. We anticipate making it available to all customers in Q4 of 2025, allowing them to open new vaults using MPC if desired.

Ripple’s proprietary MPC solution uses a 3-of-4 threshold signing scheme, distributing key shards between customer- and Ripple-hosted infrastructure to prevent unilateral key usage. MPC supports flexible node deployment in cloud environments like AWS, with Ripple nodes ensuring high availability.

The `v0_CreateVault` intent now includes a new `parameters.type` field, where you can specify either `HSM` or `MPC` key management at the time you create the vault. It is important to set this correctly at the time you open a new vault to enable correct behavior of the system.

Note:
- The default key derivation strategy for new vaults is now set to *hard* derivation. Users who still wish to create vaults using *soft* derivation or *random keys* would need to opt in at vault registration — contact your Ripple liaison. Existing vaults will not be affected by this change. For more about key derivation, see [Key derivation](/products/custody/v1.26/overview/blockchain/accounts/key-derivation).
- On-prem customers should note that this is a breaking change. If you are running a version of core higher than 1.17.x and want to register a new vault, you must have a version >=1.26.x for vault. Existing vaults are not affected.


For more information about MPC key management, contact your Ripple liaison.

## Get an address across all accounts and domains

Ripple Custody Version 1.21 introduces a new API operation [Get address from all generated addresses across domains](/products/custody/v1.26/api/reference/openapi/accounts/getaddresses), which lets you search for a given ledger address across accounts and across all your domains.

You can use the operation to verify whether a given address is under custody.

The return payload is a list of address objects, each of which includes the following fields:

* The `id`, which is the ID of the source entity for the address.
* The `address` string itself.
* The `ledgerId` for the retrieved address.
* The `domainId` and `accountId` associated with the address.
* The `createdAt` date, which identifies when the address was generated.
* The `CustodyType`, which has the value `SelfCustody`.
* The `type`, which has the value `AccountAddressReference`.


Note
* This API operation requires correct permissions for the requester, otherwise the list of addresses will be limited by the read access. You must have read access to accounts in all domains where the search should be performed.
* If the API operation does not provide the response for a search by `address` but you do have read access to accounts in all domains, then this indicates that the specified address is not under custody.


## Distribution and deployment

The 1.21 version will be progressively deployed across SaaS environments starting on June 30, 2025 with production environments scheduled for deployment on July 16, 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).