Your Gateway to the Latest in Cryptocurrency

XRPL Experiences Brief Downtime, Ripplex Advises Software Updates

XRPL Experiences Brief Downtime, Ripplex Advises Software Updates

On November 25, 2024, the XRP Ledger (XRPL) experienced a temporary disruption, halting transaction processing for approximately ten minutes starting at 13:39 UTC.

The issue caused multiple node types, including Full History, Current Ledger, Pathfinding, and Submission nodes, to crash and restart. RippleX has since urged validators and node operators to upgrade their systems to the newly released Rippled 2.3.0 version to prevent future occurrences.

Transaction processing resumed by 13:49 UTC, with no funds lost during the downtime. However, transaction creation slowed significantly, as the network prioritized security over functionality. This highlights the resilience of XRPL’s consensus algorithm, designed to ensure sustainable network operations even in rare disruptions.

Root Cause: Missing Ledger Segment Identified

RippleX confirmed that the interruption was caused by a missing ledger segment, which disrupted communication between Ripple’s network and Full History servers. This made it impossible for these servers to access the current ledger or validate transactions, leading to network instability.

The issue was traced to a caching-layer bug introduced during a code refactor six months ago. The bug, despite extensive initial testing, went unnoticed because it was not triggered until this recent event. It caused servers to freeze due to inconsistent result types in specific scenarios.

RippleX’s Response and Community Assurance

To address the issue, RippleX released Rippled 2.3.0 and emphasized the urgent need for node operators and validators to upgrade immediately. Lukas Schrick, RippleX’s VP of Engineering, called for swift action to safeguard the network against similar issues.

RippleX thanked contributors who worked on resolving the issue and assured the community that no vulnerabilities were exploited. A detailed report on the incident’s root cause will be published on December 12, 2024, to allow adequate time for all nodes to implement the update.

Conclusion

The XRPL’s brief outage underscores the importance of proactive updates to maintain network security. RippleX’s swift response and focus on transparency aim to reassure the community while ensuring long-term resilience.