The customized properties feature allows customers using the Cold Driven deployment of the Impenetrable Vault to tailor account properties according to the organizational needs.

Customized properties are designed for customers who have a wide range of clients or currency sources and need to add extra details not included in the basic account configuration. 

Each property is defined by a set of attributes that control its behavior, for example:

For more information, see Custom properties for accounts.

The Impenetrable Vault now supports up to 1000 custody accounts for their system. As an account is associated with a single public key, this significantly increases the number of cryptocurrency clients and individuals that are included on the Impenetrable Vault. 

To maintain usability at scale, the Accounts page now includes pagination:

On the Smart contracts screen the Review/Edit and Delete buttons are now enabled for use and do not depend on selecting a row in the Smart contract table.

To improve safety and reduce the need for an administrator to spend time restoring a user account on a new phone, the user themself can now reset and re-create a new Recovery Phrase. The user restore feature is designed in the event that the user either changes, loses or has their phone stolen. This feature is for uMPC-driven or uMPC-only environments using the Galaxy Custody Mobile app for authentication. 

When the user has the old phone and is switching to a new phone, a simple phone approval process occurs using both phones and the Recovery phrase to confirm the switch.

When the user does not have the original phone, in the event that it is broken, lost or stolen, the new phone must start a new Recovery seed phrase process to register the account on the new phone. 

In each instance, a Recovery lockout period occurs ensuring that if your original Recovery seed phrase has been compromised by another person, there will be a minimum time period to report this to your administrator and withhold access to the account using this seed phrase. 

This feature does not apply to users created on the Impenetrable Vault.

For more information, see Switching mobile devices.

For uMPC only systems, the Desktop app comes with some currencies included in the Custody Infrastructure system. However, not all currencies listed or added to the system remain relevant. Coins that are no longer needed can now be removed from the Coin Management listings and do not appear on the system clearing your interface of unwanted data, such as coin or token prices. 

Removing a coin also results in the removal of all tokens, contacts and smart contracts associated with it. The removal process lists details of all items to be deleted to ensure the user understands the implication of deleting the coin. After reviewing these details the user can exclude the coin from the removal list.   

The existing data for these coins remains stored in the system but it is no longer displayed in the transaction history. Nevertheless, for history and audit purposes the data the user can choose to include and or all of these currencies in a transaction history downloaded request.

For full systems the Impenetrable Vault Coin Management continues to control this option.   

In the latest version, a new installation only comes with ETH and BTC preinstalled on the system. To add other native coins the Add coins feature is available in the Coin Management screen.

Clients who have removed existing coins and want to add them back also use the Add coins feature..

The Add coins feature is expanded to include the addition of Native coins as well as restoring coins previously removed, to the Coins Management page. 

Native coins and EVMs, all coins that are presently supported, can be added to the Coin Management. When adding a new token, an ERC-20 or TRC-20, the user is prompted to add the native coin (EVM or TRON) network as well, to ensure that the token can be used properly for transactions and paying fees.

Once the coin is successfully added to the DA, the interface gives the user the option to add the new coins to any existing transaction policy so that it can be used. 

The Desktop application extends the Replace by Fee feature to include Starknet coins and transactions that remain pending on the network.

A transaction listed as Sent on the Transaction history page allows the user to increase the fees originally assigned to it. Updating the fee for the earliest pending nonce helps unblock that transaction and allows subsequent queued transactions to proceed.

The Update Fee Structure window enables the user to modify the transaction’s max fee and gas limit parameters. A Suggested Fee option is also available and can be applied to quickly rebroadcast the transaction with a higher fee.

If, when sending a transaction, the Desktop or mobile app is unable to communicate with the blockchain the app automatically continues to make the connection until it succeeds in sending the transaction. This occurs without the user having to continuously resend the transaction.

To show that a broadcast issue exists, the Transaction page now displays a warning icon next to the transaction Sending status. This contains the error detail and shows the auto retry indicator so that the client knows that the app is still trying to send the transaction to the blockchain.

In the Desktop app, Approval and Transaction policy error messages are improved to list the error, the affected policies and suggest all appropriate solutions. The suggestions can either be a specific ordered list to follow or a choice of options.

Child-Pays-for-Parent (CPFP) allows a recipient to speed up a stuck, low-fee transaction by creating a new, high-fee transaction ("child") that increases the funds assigned to the unconfirmed transaction ("parent"). Miners are incentivized to include both in the same block to get the higher fee, ensuring the original payment goes through quicker.

To release Bitcoin and Bitcoin Cash transactions that are stuck in the mempool the CPFP feature allows the user to increase the suggested fee for the stuck transactions. 

Using the Transactions History page, the user can add a ‘Child’ fee to a stuck transaction using the new Update the Fee page, which displays all transactions that are stuck and affected by the existing low fee. The user can adjust the suggested fee using the Set Custom Fee button or use the automatic fee setting based on the current blockchain suggested fee. The new fee structure is sent to the blockchain and creates the new CPFP transaction. 

The addresses for Xpl, CELO, SEI, Soneium, Unichain, and Bob are added as Explorer links to the Desktop and Mobile apps. 

When setting a custom fee for a COSMOS transaction, the Desktop app validates the fee to reduce the chance that the transaction gets stuck or fails due to a low fee. If the fee is invalid the app displays a minimum fee amount that can validate the transaction.

The system checks fees for transactions on the following nonce-based currencies, based on chain specific minimum fee validation, before sending a transaction:

If the fee is too low a message informs the user that the fee must be changed.

To improve functionality and reduce bugs when creating and editing wallets, any token added to a wallet must also include its base EVM coin. For example, when adding the USDC token, Ethereum (ETH) must also be added.

If the user creates or edits a wallet without adding the EVM an error message appears, explaining the error and the solution to be applied.

When removing an EVM all of the tokens for that network must also be removed. If any tokens are left in the wallet an error message explains which tokens to remove.

The Impenetrable Vault now supports producing the pool owner witness for Cardano (ADA) stake pool registration and re-registration certificates. 

A new pool registration witness is produced by selecting a pool owner address and providing an UTXO to fund the registration, along with the pool deposit amount. The user must also supply the pool's operator key hash and VRF key hash, as well as pool details and the transaction fee (in Lovelace) among other data. 

Once all parameters are validated the Vault produces a raw transaction signed with the pool owner key only.

To complete and broadcast the transaction, the user adds the UTXO owner and pool operator signatures. The fully signed transaction is then published to the Cardano network.

Re-registration updates an existing pool’s on-chain parameters without re-paying the pool deposit. The same multi-signature process applies: the Vault provides the pool owner witness, and the remaining signatures are added externally before broadcast.

For clients who have the Blockaid service incorporated with their Custody Infrastructure system, DeFi simulation information and notifications are added to the mobile Transaction Details displays. Simulated smart contract transactions are run and the app displays the likely results that the contract will generate so that the user can give their approval based on realistic simulated outcomes.

The simulation also shows the risk assessment from Blockaid, informing the user if the transaction could have a known security risk or not. 

The Transaction details screen displays both the simulation data and the risk assessment in the new Risk & balance impact tab.

The mobile app Transaction Details information has improvements to the display of the currency icon, network icon and an updated transaction status with inbound or outbound direction indication, text and a status symbol. 

The Confirming and Completed transaction status names are added to the Transaction Details status indicator bar. 

During the transaction process the status indicator bar animates to emphasise an ongoing process when displaying the Pending, Sent or Confirming status. For terminal status, Completed, Cancelled or Failed, the animation stops. 

Each status has a related message describing the status in more details, for example the Cancelled status message lists the approver that cancelled the transaction, or Pending message lists the number of outstanding approvers.  

Version 19 includes a broad set of bug fixes focused on overall platform stability, reliability, and operational resilience. This release addresses issues affecting Kubernetes-based deployments, service recovery, health monitoring, and high-availability behavior, helping improve system consistency during restart, failover, and recovery scenarios. In addition, v19 includes fixes for configuration and environment-specific issues, along with improvements to API behavior and general functional correctness across key workflows.

This release also delivers important fixes in database connectivity and data handling, including improvements related to MongoDB and Atlas-based environments, as well as edge cases involving data integrity, serialization, and sensitive data handling. Together with targeted performance improvements in key flows, these changes make v19 a strong stabilization release that improves deployment reliability, reduces operational friction, and provides a more predictable experience for both administrators and end users.