The aim of this new version is to improve the decentralization, security and efficiency of XRP Ledger, which is the distributed ledger of XRP.
A series of changes have reduced memory usage by 50% and streamlined validation and proposal routing, benefiting operators of single servers and large clusters. Part of these memory savings come from a change introduced by Ripple’s CTO, David Schwartz, which removes a layer of caching to further improve memory and runtime.
The version released by Ripple of XRPL
The new version improves security and reduces the amount of bandwidth required, allowing servers to more easily stay in sync with the rest of the network.
In addition, history partitioning makes it easier to host the full history, distributing it across multiple servers and eliminating the need for a single server to have sufficient disk space, and tickets are introduced to improve out-of-order transaction execution, which is particularly beneficial for facilitating multi-signature transactions.
The reporting mode now allows for more efficient processing of client requests, serving more clients with fewer servers and resources.
In particular, it is the introduction of so-called forward ledger replay that is a key improvement for XRP Ledger, precisely because it improves security and reduces the amount of bandwidth. However, this is an experimental feature that can be enabled via options.
Bharath Chari of XRP Ledger Foundation said:
“Enhancements, such as today’s improvements to memory usage, are key to growth and innovation on the Ledger. We look forward to supporting the wider ecosystem, including the superb code development by the RippleX team. Testament to this will be our focus on producing an evolving list of validators and enhancing the core code and infrastructure behind the XRP Ledger”.
The goal of the XRP Ledger Foundation is precisely to accelerate the development and adoption of XRPL by involving developers, while RippleX is one of the contributors to the XRPL community.