As a seasoned crypto investor with a decade of experience under my belt, I have witnessed the ebb and flow of numerous blockchain projects, including XRP. The recent upgrade on the XRP Ledger (XRPL) has caught my attention, particularly due to its focus on addressing a network issue that affected full history nodes.
The XRP Ledger (XRPL) is about to undergo an update specifically designed to address a network problem. The main challenge leading to this update was the failure of full history (FH) nodes as a result of a limitation in SQLite’s page size.
A validator on the XRP network, known as Vet, recently posted about a resolution on their blog. As per Vet, the problem with the Full History Servers in the XRP Ledger has been successfully integrated into an official version of the rippled release within the XRPLF Repository – specifically, rippled 2.2.3. This latest update is now ready for users to download and install.
As per a screenshot posted by Vet, it’s suggested that users of the Rippled (XRP ledger server) run version 2.2.3 if they are operating full history servers with a page size of 4096. This recommendation doesn’t apply to validators as they won’t encounter this issue. They can opt to continue using version 2.2.2 or upgrade to 2.2.3, as the latter does not bring any new modifications compared to version 2.2.2.
What happened?
During the weekend, there was a concern within the XRP community about an issue on the ripple server which led some Full History (FH) nodes to stop functioning properly.
Typically, comprehensive history servers diligently save and provide all transaction histories. Unfortunately, issues arose with FH nodes because of a limitation in SQLite related to page size.
According to certain XRPL dUNL validators, this problem was brought up several weeks ago, but it hasn’t received immediate resolution yet.
As a passionate crypto investor, I’d like to share some insights from a recent post by XRP Cafe founder, xrpl_adam. Contrary to the widespread assumption, the current issue he addressed does not affect the consensus or the overall health of the network associated with Ripple (XRP).
To clarify, Clio redundancy allows that majority of public XRPL endpoints can retrieve historical transaction data without needing a real Forwarding Header (FH) server to deliver the outcomes from past transactions directly.
As per Xrpl Adam’s explanation, this problem wasn’t a recent development on the XRP Ledger; it had been documented years ago. Back then, it was pointed out that specific rippled servers carrying the full ledger history might encounter an issue with their SQLite database page size. This problem would hinder these servers from functioning effectively.
The founder of XRP Cafe, on the other hand, thinks it would have been more beneficial if the need for a fix had been emphasized earlier, so as to prevent Failure Handling (FH) nodes from failing during the recent weekend period.
Read More
- USD COP PREDICTION
- POWR PREDICTION. POWR cryptocurrency
- SSV PREDICTION. SSV cryptocurrency
- USD VES PREDICTION
- USD PHP PREDICTION
- NAKA PREDICTION. NAKA cryptocurrency
- EUR RUB PREDICTION
- USD RUB PREDICTION
- BAN PREDICTION. BAN cryptocurrency
- NBLU PREDICTION. NBLU cryptocurrency
2024-09-16 19:24