The XRP Ledger has received a major software upgrade aimed at making the network more efficient and stable. Released this week, XRP Ledger version 3.4.0 introduces a long list of performance improvements, bug fixes, and protocol changes. The update also brings two new amendments, including an upgraded version of the network's lending functionality.
For ordinary XRP users, most of the changes will happen behind the scenes. However, they are important because XRP Ledger servers are responsible for processing transactions, keeping copies of the ledger, and communicating with other machines.
One of the most notable performance changes is designed to help XRP Ledger servers stay more up to date. Previously, a server could continue deleting older ledger data even when there were gaps in its recent transaction history. Version 3.4.0 changes that behavior: online deletion will now pause when such gaps are detected. In simple terms, the change should help nodes avoid falling behind while they are simultaneously trying to clean up old data.
The update also includes several smaller optimizations intended to make XRP Ledger software faster and more efficient. For instance, developers optimized certain checks involving Multi-Purpose Tokens, or MPTs, so that servers do not repeatedly read the same information from the ledger when there is a need to determine whether assets are frozen.
Version 3.4.0 also includes numerous fixes designed to make the ledger more resistant to unusual inputs and edge cases. There are protections against oversized transaction messages, improvements to how servers handle incoming peer data, stricter validation of certain transaction fields, and safeguards against database operations that could otherwise consume excessive resources.
The new release contains a significant amount of maintenance work as well. Developers have modernized parts of the codebase, replaced older software libraries, and improved testing infrastructure. XRP Ledger operators are being urged to upgrade their servers to version 3.4.0 as soon as possible, as upgrading is necessary to ensure continued service as the network prepares for the new amendments.
