en.coinotag.com
XRP Ledger Resumes Operations After Temporary Halt; Cause Under Investigation
-
The XRP Ledger experienced a brief halt in block production, sparking concerns in the crypto community but ultimately ensuring user fund security.
-
Ripple’s CTO, David Schwartz, has indicated that while the network has resumed, the underlying cause of this disruption remains under investigation.
-
Schwartz confirmed via social media: “Super-preliminary observation: It looked like consensus was running, but validations were not being published.”
This article explores the recent halt in XRP Ledger block production, its causes, and the implications for user funds within the crypto ecosystem.
XRP Ledger Temporarily Halts Block Production
On February 4, the XRP Ledger (XRPL) temporarily ceased block production for approximately 64 minutes, a disruption that raised questions about the reliability of one of the most prominent blockchain technologies. During this time, network activity stalled at block height 93,927,174. The blockchain has since resumed normal operations, but investigative efforts into the root cause are ongoing.
According to reports from the self-custody Xaman Wallet, the XRP Ledger returned to full functionality shortly after the halt. “The XRP ledger is now fully operational after the recent halt, and transactions can resume as normal,” the update confirmed, putting users at ease.
David Schwartz, CTO of Ripple, addressed the incident on X (formerly Twitter). While he stated that the network was back online, he emphasized the uncertainty surrounding why the issue occurred. Schwartz commented, “Super-preliminary observation: It looked like consensus was running, but validations were not being published, causing the network to drift apart.” This indicates a lapse in the validation process, which may have caused the network to momentarily diverge.
Technical Intervention and Recovery
During the outage, validator operators took emergency measures by manually selecting a reliable starting point from the last fully validated ledger, which facilitated the resumption of transaction validations. Schwartz remarked, “It looks like, as far as we can tell, only one validator operator manually intervened.” This led to a realignment of the network, although the necessity of this manual intervention in resolving the issue remains unclear.