# Ripple Custody 1.24 (August 18, 2025)

Version 1.24 is a SaaS release that introduces three new Ripple Custody events.

## New events

Ripple Custody v1.24 introduces three new events emitted via the Ripple Custody event tracking system. These events are accessible through the Events API or, where configured, through a push-based Advanced Message Queuing Protocol (AMQP) queue integration.

The three new events are the following:

* `IntentExecuted` is an intent event emitted when the notary validates and executes an approved intent. It differs from the  `IntentClosed` event, which signals closure of any intent, whether approved, rejected, or failed. The payload includes:
  * `id` – The ID of the intent.
  * `type` – The type of the event, `IntentExecuted`.
* `AddressCreated` is emitted whenever a new account address is added to an existing account. The payload includes:
  * `id` – The ID of the new account address.
  * `type` – The type of the event, `AddressCreated`.
  * `accountReference` – The `id` and `domainId` of the  account.
* `BalancesUpdated` is emitted whenever there is any change to the account's balances, including total, reserved, or quarantined amounts. The payload includes:
  * `tickerIds` – A list of tickers whose balances have been updated.
  * `type` – The type of the event, `BalancesUpdated`.
  * `accountReference` – The `id` and `domainId` of the affected account.


For more information about Ripple Custody API events, see [Event tracking](/products/custody/v1.36/reference/events-and-webhooks/event-payload-reference).

## Distribution and deployment

The 1.24 version will be progressively deployed across SaaS environments starting on August 18, 2025 with production environments scheduled for deployment on September 1, 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).