The release version 3.2.0 of XRP Ledger is out now, marking a significant improvement to the underlying blockchain infrastructure. This time, developers have renamed the software used for operating the network from “rippled” to “xrpld.” As explained by the creators, it is more relevant for the software to have a new name, considering the entire ecosystem of the project. It follows version 3.1.3, which was successfully deployed recently.
While earlier releases introduced new user features, developers prioritized back-end upgrades and efficiency gains in this release. The developers have built the software release to enhance network performance as well as prepare the software architecture for scaling in the future. Some of the key additions include memory optimization measures, which will help save up to forty percent of server memory use.
The release also brings with it the new fixCleanup3_2_0 modification, which encompasses several enhancements in terms of security to various XRP Ledger modules. The new modifications bring increased security to single-asset vaults, lending protocol, permissions, decentralized exchanges, multi-purpose tokens, and permissions domains. XRP Ledger developers introduced new invariant checks to ensure deleted accounts do not leave inconsistencies on the ledger. The team stated that these changes will strengthen the integrity and reliability of the overall network.
About version 3.2.0, there is an additional capability brought to developers and infrastructures. With the latest update, applications will be able to retrieve information on the XRP Ledger protocol and server definitions even without the need to connect to the server. According to the developers, this can greatly help in developing wallets, blockchain explorers, and APIs, among others.
As part of the improvement process, a number of changes were included by the XRPL in order to enhance the performance and connectivity of enterprises using the network. One of such updates includes configurable block sizes along with effective database storage via nuDB. Also, gRPC server support for TLS/mutual TLS became optional, ensuring that businesses could benefit from improved performance and connectivity.
Furthermore, the update includes a default change in the peering port from 51235 to 2459, along with a variety of fixes regarding Automated Market Makers, Payments, Token Escrows, Multi-Purpose Tokens, Order Books, and RPC. The reason the transaction invariants were temporarily disabled in v3.2.0 was a decline in performance. However, there is no threat regarding the security aspect because transaction invariants currently do not perform any actions.
Highlighted Crypto News:
Grayscale Highlights Need for Decentralized AI After Anthropic Shutdown


