# Ripple Custody 1.36 (June 26, 2026) Version 1.36 is a short-term support (STS) SaaS release that introduces support for the following new features: - System-signed intents. - Omnibus. - Support for the Thales Luna PCIe HSM 7 (A700) card. ## System-signed intents Ripple Custody version 1.36 introduces *system-signed intents*, which let an authenticated service caller submit selected intent proposal types without sending a client-side payload signature. The platform signs the proposal internally, and policy evaluation admits it only when a matching policy uses `intentOrigin: "SystemSigned"`. System-signed intent configuration is enabled by default at deployment level in current release packages. This does not activate system-signed traffic by itself. System-signed proposals remain disabled until: - Gateway has provisioned the system signing key. - The active Gateway system signing public key is registered in Notary. - `NOTARY_SYSTEM_SIGNED_INTENTS_ENABLED` is set to `enabled: true`. - A matching policy with `intentOrigin: "SystemSigned"` allows the service caller and intent type. Gateway provisions the system signing keypair automatically on first boot and stores the wrapped signing key in the Gateway database. The dedicated signing component unwraps the key for signing; Gateway does not hold the unwrapped private key. Typical use cases are service-to-service automations that need to propose a narrow set of repeatable intents without managing a user signing key. In this release, the main documented use case is Omnibus automation: creating deposit wallets, submitting deposit sweeps, and propagating ledgers to deposit wallets. These service-generated proposals still pass through Notary and policy controls. System-signed intents should remain tightly scoped to the service caller, target domain, and allowed intent types. User-triggered business flows, such as Omnibus creation and withdrawals, continue to return unsigned Custody intents for the client to sign through the normal user-signed intent flow. For more information, see: - [System-signed intent configuration](/products/custody/deployment/reference/system-signed-intents) - [Intent request structure](/products/custody/governance/intents/intent-request-structure#system-signed-proposal-request-body) - [Submit a system-signed intent with the API](/products/custody/governance/intents/manage-intents-and-approvals#submit-a-system-signed-intent-with-the-api) - [Create a policy for system-signed intents](/products/custody/governance/policies/manage-policies#create-a-policy-for-system-signed-intents-with-the-api) ## Omnibus Ripple Custody version 1.36 introduces *Omnibus*, which lets an organization hold pooled on-chain funds in an omnibus wallet while tracking each tenant's position off-chain with virtual accounts. Omnibus supports pooled custody workflows where: - A single omnibus wallet holds accepted funds on-chain. - Virtual accounts track tenant balances and internal movements off-chain. - Deposit wallets identify incoming funds before Omnibus sweeps them into the omnibus wallet. - Internal transfers between virtual accounts do not create blockchain transactions or require on-chain fees. - Withdrawals leave the omnibus wallet on-chain and follow normal custody policy, approval, signing, and broadcast controls. Omnibus uses system-signed intents for automated operations such as creating deposit wallets, sweeping deposits, and adding account ledgers. User-triggered Omnibus operations, such as omnibus creation and withdrawals, return unsigned Custody intents for the client to sign and submit through the normal intent flow. Omnibus currently supports non-native assets on Solana, XRPL, and EVM networks. Gas Station can fund native gas for non-native token sweeps and withdrawals on supported networks. For more information, see: - [Omnibus overview](/products/custody/accounts-and-assets/omnibus/overview) - [Setup and governance](/products/custody/accounts-and-assets/omnibus/setup-and-governance) - [Manage omnibus](/products/custody/accounts-and-assets/omnibus/manage-omnibus) - [Deposits](/products/custody/accounts-and-assets/omnibus/deposits) - [Withdrawals](/products/custody/accounts-and-assets/omnibus/withdrawals) - [Internal transfers](/products/custody/accounts-and-assets/omnibus/internal-transfers) - [Balances and reconciliation](/products/custody/accounts-and-assets/omnibus/balances-and-reconciliation) ## Thales Luna PCIe HSM support Ripple Custody version 1.36 introduces support for the **Thales Luna PCIe HSM 7 (A700)** card as an additional HSM option alongside the **Thales Luna Network HSM 7** appliance. Both use the Luna 7.x cryptographic interface and firmware family. The main difference is the transport layer: Network HSM uses network connectivity and certificates, while PCIe HSM is installed directly in the host server. For more information, see [Thales Luna HSM integration guide](/products/custody/deployment/integrate-kms/on-premise-hsm/thales-luna). ## Distribution and deployment Ripple progressively deploys Version 1.36 across SaaS environments starting June 26, 2026. ## 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).