<figure>
 <figcaption>
 Cover image via <a href="https://u.today/" rel="noopener noreferrer nofollow">U.Today</a>
 </figcaption>
</figure>
The <a href="https://u.today/xrp-ledger-set-for-upgrades-as-amendments-secure-majority" rel="noopener noreferrer nofollow">XRP Ledger </a>(XRPL) is set to receive an upgrade aimed at resolving a network issue. The primary issue that prompted this upgrade involved full history (FH) nodes failing due to an SQLite restriction in page sizing.
Vet, an XRP dUNL validator, shared this development in an <a href="https://x.com/Vet_X0/status/1835392527563665911" rel="noopener noreferrer nofollow">X post</a>. According to Vet, the fix for the XRP Ledger Full History Servers issue has been merged in an official rippled release of the XRPLF Repository - rippled 2.2.3, which is now available for installation.
<blockquote>
 The fix for <a href="https://twitter.com/hashtag/XRP?src=hash&amp;ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">#XRP</a> Ledger Full History Servers is merged in an official rippled release of the XRPLF Repository - rippled 2.2.3 and available for installation. <a href="https://t.co/Owpd6xPEHx" rel="noopener noreferrer nofollow">pic.twitter.com/Owpd6xPEHx</a>— Vet 🏴‍☠️ (@Vet_X0) <a href="https://twitter.com/Vet_X0/status/1835392527563665911?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">September 15, 2024</a>
</blockquote>
According to a screenshot shared by Vet, the Rippled (XRP ledger server) version 2.2.3 release is strongly recommended for full history servers using a page size of 4096. Since validators are not affected by this issue, they can either choose to run 2.2.2 or update to 2.2.3. This is because version 2.2.3 does not introduce any new amendments to version 2.2.2.
<h2 id="what-happened">What happened?</h2>
Over the weekend, the <a href="https://u.today/xrp-community-hit-with-critical-warning-heres-what-it-concerns" rel="noopener noreferrer nofollow">XRP community</a> drew attention to an issue on the rippled server that caused full history (FH) nodes to fail.
Under normal circumstances, full history servers happily record and serve up the full transaction history. However, FH nodes failed due to a SQLite restriction in page sizing.
This issue, according to some XRPL dUNL validators, had been highlighted weeks back but had failed to secure prompt attention.
XRP Cafe founder <a href="https://x.com/xrpl_adam/status/1835059030756065558" rel="noopener noreferrer nofollow">xrpl Adam</a> clarified in an X post that, contrary to popular belief, this issue has no impact on consensus or network health.
Furthermore, with clio redundancy, most public XRPL endpoints do not require an actual FH server to return historical transaction results.
According to Xrpl Adam, the issue was not new on the XRP Ledger, having been documented years ago. It was noted then that certain rippled servers with full ledger history may experience an issue with their SQLite database page size, preventing the server from operating properly.
The XRP Cafe founder, however, believes that the urgency of the fix should have been promoted sooner to avoid FH nodes going down, which happened over the weekend.

XRP Ledger Upgrade Incoming: Major Network Issue Addressed

Table of Contents

U_Today

Other articles published on Sep 16, 2024

Last Two Weeks of the “Rootstock World Tour” Campaign

Pepe Cuts Rates (PEPERATE) Solana Memecoin to Surge 17,000% Before Exchange Listings, As Shiba In...

Investors Monitor Floki, XRP, and AVAX Markets

Binance founder CZ is getting out of jail in 13 days

Sky Protocol’s Recent Proposal Could Impact $200M Loans Backed by Wrapped Bitcoin: Report

Top cryptos this September with potential to turn $15 into $1250 by January 2025

Join our free newsletter for daily crypto updates!