# Harmonize 1.10 (December 1, 2023) Version 1.10 includes a combination of various new features for ledger management, tokenization management, upgrades to our enterprise technology stack, expanded key management options and improvements to the user experience. - Ledger management - [Improved fee management for UTXO-based ledgers](#improved-fee-management-for-utxo-based-ledgers) - [Updating on-chain transactions for UTXO-based ledgers](#updating-on-chain-transactions-for-utxo-based-ledgers) - Tokenization management - [Full smart contract lifecycle management (EVM)](#full-smart-contract-lifecycle-management-evm) - [ERC-1155](#erc-1155) - Enterprise technology stack - [Extension of Telemetry support](#extension-of-telemetry-support) - [Trusted address validation](#trusted-address-validation) - [Upgraded indexer connectivity](#upgraded-indexer-connectivity) - Key management - [KMS-Connect support for Thales Hardware Security Modules (HSMs)](#kms-connect-support-for-thales-hardware-security-modules-hsms) - User experience - [Policy management](#policy-management) For information about distribution and deployment of this version, see [Distribution and deployment](#distribution-and-deployment). ## Ledger management ### Improved fee management for UTXO-based ledgers Working closely with our clients, we have redesigned the computation and the configurability of transaction fees on UTXO-based ledgers (for example, Bitcoin, Litecoin). The new feature allows more granular fee management, introducing decimal values for fee rates. The feature will help clients reduce on-chain transaction fees and optimize the transaction success rate. ### Updating on-chain transactions for UTXO-based ledgers We have extended the existing feature to prepare and broadcast replacement transactions on the blockchain from EVM-based ledgers to all supported UTXO-based ledgers. Due to a variety of reasons such as network congestion, misconfiguration, insufficient fees and others, on-chain transactions can remain in the mempool of the ledger, i.e. not being picked up and confirmed - and thus not settled. Yet, the corresponding amounts of those transactions are not available for other transactions. The feature allows for the preparation of replacement transactions (for example, with higher fees) which can be designed to either cancel or actually replace the pending transaction(s). These critical operations are subject to the full protection of our policy engine. ## Tokenization management ### Full smart contract lifecycle management (EVM) Harmonize further extends its tokenization support capabilities by now capturing all relevant on-chain data from the deployment, the lifecycle management and the deletion of a smart contract on EVM-based ledgers. Harmonize accounts thus can manage, track and record all smart contract activity in its tamper-proof audit trail. ### ERC-1155 We have added support for the ERC-1155 token standard on EVM-based ledgers (Ethereum, Polygon, Binance Smart Chain, Avalanche), enabling our clients to represent multiple fungible and non-fungible tokens in the same smart contract. Harmonize now supports the capability to create, redeem, receive, store and send tokens based on that standard, an increasingly popular choice for many NFT projects. It allows efficient, low-fee smart contract operations on the blockchain. The support of ERC-1155 further extends our capabilities to deploy and manage the lifecycle of the corresponding smart contract from within Harmonize, in a seamless and fully governed manner. ## Enterprise technology stack ### Extension of Telemetry support As an extension of our last release version 1.9, we have now included additional logs, metrics and traces of each Harmonize component in Telemetry. This is yet another manifestation of our continuous commitment to live up to our enterprise DNA. ### Trusted address validation To further increase the security and trust level of the system, we have added additional cryptographic proofs for the association of created blockchain addresses with a corresponding Harmonize account. ### Upgraded indexer connectivity Indexers, Harmonize components to connect to the various blockchain ledgers via nodes, have been reworked for improved efficiency of operations and to natively support additional “Node-as-a-Service” providers. ## Key management ### KMS-Connect support for Thales Hardware Security Modules (HSMs) KMS-Connect, a feature introduced in version 1.9, now additionally supports HSMs from Thales (Luna) for key management. This step validates the applicability of this connectivity module to seamlessly and securely connect to existing and future key management backends and thus enables Ripple to significantly reduce implementation time for additional key management solutions. The current release supports the establishment of new KMS connections using the KMS-Connect module. Existing KMS connections for Thales are not affected by it. ## User experience ### Policy management The Harmonize frontend now supports features to directly update the approval workflow of an existing policy. Additionally, frontend users are able to duplicate existing policies, which further facilitates the creation of fine-grained policy sets, especially in the context of governing smart contracts and tokenization use cases. ## Distribution and deployment ### SaaS The upgrade will be done progressively starting on 11/12/2023 across the various environments. The production environment will be upgraded last, with a deployment planned on 08/01/2024. This may be delayed based on customer feedbacks. If customers want to have 1.10 on their PROD before this date, it can also be arranged. ### On-premise Version 1.10 will be available for our on-premises customers 01/12/2023 onward and can be downloaded and installed. The usual process of pulling the containers from Ripple's repository using the “1.10.0” tag applies. As all new releases, this version triggers the deprecation of the previous version (v.1.9.x) which will continue to be supported for the next 6 months, unless specified otherwise in the master contract with Ripple. Should you decide to skip the upgrade of version 1.10, we plan to release the next version by the end of January 2024, ensuring you can remain on v.1.9.x without any issue. See the Platform Versioning page on our documentation website for more information on the versioning of Harmonize. Please remember to regularly visit the versioning page of the documentation to understand and anticipate API deprecations, end of support for previous version, and how this might affect your operating model. ## Activation and support The deployment of 1.10 will require you to take actions on the secure components (for On-Premise deployments). Please reach out to our customer support team for additional information. Should you be interested in activating any of the new features, you can reach out to the Ripple team for a dedicated presentation of the new capabilities. Also, the configuration of new functionalities can sometimes present technical challenges and require the support of our team: kindly reach out to us should you need any technical assistance, by sending an e-mail to the Ripple support team.