XRP Ledger Upgrade Is to Address FH Node Issue

• XRP Ledger has released a rippled 2.2.3 update to address issues with Full History nodes
• The issue was related to an SQLite database constraint that caused FH nodes to stop working
• The update is not required for validators but is recommended for full-history servers

XRP Ledger has released a 2.2.3 update to address a technical issue with Full History nodes that was caused by a page size limitation in the SQLite database and led these nodes to fail.

This update is already available for installation and is recommended for Full History servers using a page size of 4096 bytes.

XRP Ledger Update And Full History Node Solution

The main reason for releasing the update was the glitchy behavior of full history nodes, which caught the attention of the XRP community. These nodes are usually responsible for recording and maintaining the full transaction history of the network. However, due to a SQLite limitation, the FH nodes could not function accurately.

An XRP dUNL validator named Vet shared information about the implemented fix via an X social media post, noting that the rippled 2.2.3 update has been integrated into the XRPLF repository and is now available for installation.

This update is recommended for full history servers using a page size of 4096 bytes, while validators can continue to use version 2.2.2 or upgrade to 2.2.3.

A Bit of History About FH Node Problem

The full history node problem is not new to the XRP Ledger and the founder of XRP Cafe, Xrpl Adam, explained that this fault was documented years ago.

Although this issue has occurred before, according to some XRPL dUNL validators, it has not received the attention it deserves, resulting in node failures over the past weekend.

Xrpl Adam also emphasized that the FH node issue does not affect the consensus of the network or its current state, as most public XRPL endpoints can serve requests without having to access full history servers due to clio redundancy.

Conclusion

Fixing technical issues, especially those aimed at stable and sustainable network behavior is very good news.

And even though the XRP Ledger is late with the fix, it's a great example of how open source and the community are productive for projects and able to take proactive measures.