XRP Ledger infrastructure has returned to normal operation following a July manifest flood attack, according to telemetry data from Ripple CTO Emeritus David Schwartz. His personal node recorded “rock solid” performance between August 25 and September 8, with 423 concurrent connections and average peer latency of 165 milliseconds. Abuse metrics dropped to nearly zero after the deployment of the xrpld 3.2.1 hotfix, which limits manifest size and alters cache handling. The attack did not affect ledger consensus. The data offers an early test of the security changes.
In a post, David Schwartz released telemetry data from his personal XRPL node for August 25 to September 8. He stated, “All issues with my hub have been fixed and it has been rock solid for the past two weeks.”
The private node helps connect other nodes within the XRP Ledger network. This update follows the July 31 attack, when hackers sent thousands of counterfeit manifest certificates to validator nodes. Connection issues included “onReadMessage” problems during ledger state checks. The attack did not prevent the consensus of new ledgers.
In response, developers released the xrpld 3.2.1 hotfix. Limits were set on manifest size, and caching of data from unknown participants was altered. Over a month later, Schwartz’s telemetry shows these changes under normal conditions.
His statistics indicate about 400 concurrent connections from August 25 to September 8. There were 135 inbound and 271 outbound connections. Average peer latency was 165 milliseconds, with a brief spike to 1.49 seconds on September 6 that did not disrupt consensus. Connection losses averaged 84.6 per five minutes, considered normal background noise. The “Abuse” metric dropped to almost zero, indicating new software filters out most undesirable traffic.
The telemetry offers an early hint of the effectiveness of the xrpld 3.2.1 changes. While data comes from Schwartz’s personal hub, the consistent connection numbers, low latency, and zero abuse readings point to enhanced readiness. The July disruption had no impact on ledger finality, and software improvements appear to have succeeded.
Also Read | Can the CLARITY Act Survive Its Sept. 15 Senate Vote?
Also Read | Strategy Deploys $176M on STRC Buyback After Pausing Bitcoin Accumulation
