XRP Ledger Fixes Full History Node Failures with Rippled 2.2.3 Upgrade

The XRPL has issued a critical update to address a problem affecting the network’s Full History node. An SQLite page sizing limitation was the cause of the problem that led to the FH nodes failing.

According to a post on the X platform shared by a validator named Vet, the latest version of Rippled focuses solely on the issue with the Full History Servers. The goal of Rippled 2.2.3 is to resolve the page size issue with SQLite databases that were impacting FH nodes. The upgrade is advised to restore the Full History servers with 4096 pages and bring them back to full functionality.

Validators were given the option to upgrade to version 2.2.3 or remain on the older version 2.2.2 even though the problem didn’t affect them. Since the current release addresses the node failure issue rather than bringing about any modifications, both of these versions are compatible because the most recent release addresses the node failure issue rather than bringing any new features.

The XRP community has been concerned with the Full History node failures since the issue was brought to light last weekend. A few FH nodes containing the entire ledger record of transactions began to malfunction due to the SQLite page size restriction. Even though it was thought the issue had dealt with years ago, it appeared again and caused FH node failure.

Several validators in the XRPL network had identified the issue weeks before the current troubles but failed to receive the necessary attention. Despite these shortcomings, consensus and network health do not appear to have been compromised. 

XRP Cafe founder Adam mentioned that the majority of XRPL endpoints didn’t require a Full History server to obtain historical transaction data because clio redundancy was in place. However, he stated that the repair should have been completed earlier to prevent the FH node failure over the weekend.

While there are issues with FH nodes, the XRPL community was assured that the server’s functionality has been restored. SQLite’s page size issue did not impact validators, who are critical to the network’s consensus and security.

The XRP Ledger is set to undergo a significant update soon with the introduction of Multi-Purpose Tokens (MPTs). This project will add various functionalities to the blockchain by focusing on tokenized asset management and efficiency.

MPT will provide users with real-time data regarding on-chain transfers which will improve tracking speed of transactions. This initiative is expected to enhance decision-making processes because users would receive timely information on managing their assets effectively.

Fungible and non-fungible tokens wouldn’t be suitable for critical on-chain tokenization use cases without MPTs. This also complements the XRPL’s basic qualities like the protocol-native approach, which incorporates any protocol changes into the consensus layer itself.

The XRP price has been range-bound between $0.50 and $0.60 for most of the past month. Source: Brave New Coin XRP Liquid Index

The SEC vs. Ripple case was recently resolved, with Ripple agreeing to settle for a $125 million fine. As a result, there has been a noticeable spike in whale transactions on the XRP network. Significant XRP transfers have been found, especially involving well-known exchanges like Binance, Bitstamp, Bitso, and Upbit. 

Chris Larsen, co-founder of Ripple has recently transferred 50 million XRP units valued at around $29 million to an unidentified wallet. As the network expands, this spike in whale activity indicates growing market interest in XRP.

Additionally, market response to Ripple’s continuous release of one billion XRP each month has been inconsistent. Although some investors are concerned about the possible implication of inflation, Ripple insists that these transactions are necessary for the expansion and financial success of the ecosystem.