On November 25, 2024, the XRP Ledger (XRPL) briefly halted transaction processing, affecting the network for approximately ten minutes. The issue arose around 13:39 UTC, causing several nodes, including Full History, Current Ledger, Pathfinding, and Submission nodes, to crash and restart. RippleX has since advised validators and node operators to update their systems to the newly released Rippled 2.3.0 version.
Transaction processing resumed by 13:49 UTC, and no funds were lost during the downtime. However, few new transactions were created because the network focused on security over development during the disturbance. This mechanism is one of the essential aspects of the XRPL consensus algorithm, which guarantees the network’s sustainable functioning even in rare cases.
Also Read: SEC Chair Nominee Expected This Week, Ripple’s Rally Linked to Gensler’s Departure
Missing Ledger Segment Identified as Cause of the Incident
RippleX later confirmed that the disruption stemmed from a missing ledger segment, which interrupted communication between Ripple’s network and Full History servers, rendering them unable to view the current ledger or validate transactions. This issue stopped all exchanges with the Full History servers, making servers unable to view the current ledger or validate Ripple transactions at that time. As a result, the networks were unstable until the issue was sorted out.
Advertisement
This was traced to a caching-layer bug during a code refactor committed over six months ago. This bug resulted in different result types depending on specific scenarios, making servers freeze. Though the problem was well-tested initially, it remained unnoticed and was not used before the recent event.
RippleX Urges Immediate Upgrade to Rippled 2.3.0
In response, RippleX announced the release of Rippled 2.3.0, emphasizing the need for node operators and validators to upgrade. Lukas Schrick, RippleX’s VP of Engineering, called for the immediate implementation of the upgrade to solve similar problems that affect the network.
RippleX expressed gratitude to contributors who addressed the issue and assured the community that no vulnerabilities had been exploited. Detailed technical information about the root cause is scheduled for December 12, 2024. This timeline aims to minimize risks for nodes that have not yet implemented the patch.
Conclusion
The incident underscores the importance of timely upgrades and proactive network management in blockchain ecosystems. RippleX’s swift response and transparency aim to restore confidence and ensure XRPL’s long-term stability.
Also Read: XRP, SHIB, and BAND See Surge in Network Activity, Indicating Potential Price Volatility
Maxwell Mutuma
Maxwell is a crypto-economic analyst and Blockchain enthusiast, passionate about helping people understand the potential of decentralized technology. He writes extensively on topics such as blockchain, cryptocurrency, tokens, and more for top publications such as Coingape, Coin Edition, and The Coin Republic. His goal is to spread knowledge about this revolutionary technology and its implications for economic freedom and social good.