RippleX Provides Update On XRP Ledger Bug Incident

According to U.Today, RippleX has issued an important update concerning the XRP Ledger following a recent bug incident that affected the network. On November 25, 2024, at 1:39 p.m. UTC, the XRP Ledger encountered a problem where several nodes crashed and restarted simultaneously, causing a temporary halt in transaction processing for about 10 minutes. During this period, the network's consensus mechanism prioritized safety over progress, ensuring no funds were lost. By 1:49 p.m. UTC, the network resumed normal operations. Brad Chase, Vice President at RippleX, addressed the community in a social media post, providing insights into the cause of the incident and the steps taken to resolve it. The issue originated from a bug introduced over six months ago, which caused the caching layer of the 'rippled' software to return inconsistent results, leading to server crashes. Although the bug went unnoticed during testing, it was discovered at the end of the testing phase for rippled version 2.3.0. A fix was developed and released internally, and the RippleX team worked closely with the community and UNL operators to implement updates and secure the network. The community's prompt response to the update has been commendable, with 33 out of 35 validators on the default UNL and nearly half of known servers already upgraded to rippled 2.3.0. However, unpatched nodes remain vulnerable, and RippleX urges all users to update their infrastructure to the latest version. To mitigate risks for unpatched users, RippleX plans to withhold specific technical details until most servers have been upgraded. Node operators have until December 12 to complete the upgrade, after which more technical information will be shared. This delay in sharing details is intended to prevent potential exploitation of the bug by malicious actors. RippleX emphasizes the importance of upgrading to version 2.3.0 promptly to ensure network security.