The XRP blockchain recently underwent a significant upgrade that addressed a critical issue affecting full history servers. Due to limitations in their software, these servers were previously unable to display the complete blockchain history.
The Full History Server Issue
Full-history nodes (FH nodes) play a vital role in the XRP ecosystem by storing and serving the entire blockchain history. However, due to a constraint in the SQLite database used by these nodes, the page size when displaying the full history was limited. This limitation prevented FH nodes from providing accurate and complete historical data.
The Solution: Rippled 2.2.3
To resolve this issue, the XRP community developed and released Rippled version 2.2.3. This new node software version includes updates that eliminate the page size restriction, allowing FH nodes to serve the full blockchain history without any limitations.
Upgrade Requirements
Full history server nodes must upgrade to Rippled 2.2.3 to benefit from the resolved issue and ensure accurate historical data. Validators, on the other hand, can continue using Rippled version 2.2.2 for now.
Final Words
The recent XRP Ledger upgrade is a significant step forward in enhancing the reliability and functionality of the blockchain. By addressing the full history server issue, the upgrade ensures that all participants in the XRP ecosystem have access to accurate and complete historical data. This is crucial for maintaining the integrity and transparency of the network.
What Are Full History Servers?
Full History servers are those nodes that contain the full list of all transactions that have ever happened on the XRP blockchain. These are different from the validator nodes which only hold a partial history with them.
