XRP Ledger Rebuilds Batch Amendment After Critical Security Flaw

XRP Ledger Batch V1.1 rebuilt by RippleX after a critical security flaw, with security audits and validator voting for activation.

RippleX has released a rebuilt version of the XRP Ledger’s Batch amendment after the original implementation was withdrawn following the discovery of a signature validation flaw.

According to BSCN, the vulnerability could have allowed unauthorized transactions involving accounts that did not possess valid private keys. The issue prompted RippleX to remove the initial implementation while the underlying cause was investigated and a revised version was developed.

RippleX Releases Batch V1.1

The rebuilt implementation, identified as Batch V1.1, includes several additional security measures introduced during the review and development process.

RippleX said the revised version underwent security reviews, audits, attack testing and expanded regression testing. The company also said four senior engineers reviewed both the root cause of the vulnerability and the subsequent fix.

The additional testing was intended to examine the revised implementation more extensively before it proceeds through the XRP Ledger’s validator-based activation process.

The Batch amendment is designed to introduce batch transaction functionality to the XRP Ledger, but its activation remains dependent on validator approval.

External Security Assessments Added

Beyond RippleX’s internal review process, the revised implementation was also assessed externally by Halborn and Common Prefix.

The involvement of outside security firms adds another layer of review following the flaw identified in the original implementation. BSCN reported that the external assessments were part of the security work conducted on Batch V1.1 before its inclusion in the XRP Ledger software release.

The revised implementation is now included in xrpld v3.3.0, the software release associated with the amendment.

Batch Amendment Remains Under Validator Voting

Although Batch V1.1 has been incorporated into xrpld v3.3.0, the amendment has not yet been activated on the XRP Ledger. It remains subject to validator voting.

Activation requires an 80% validator majority to be maintained for 14 consecutive days. The requirement means that reaching the threshold at a single point is not sufficient; the required level of validator support must remain in place throughout the specified period.

For now, the next stage for the rebuilt Batch amendment is the ongoing validator voting process, which will determine whether the required activation threshold is maintained.

writer: Ethan Collins
Crypto Journalist
Ethan Collins reports on developments across the cryptocurrency and blockchain sector. His work covers market movements, protocol updates, regulatory changes, and emerging trends in digital assets.
He focuses on presenting complex topics in a clear and accessible manner for a broad readership.