Ripple Pushes Toward September Launch for XRPL Batch Amendment

The Batch V1.1 amendment, defined under the XLS-56 specification, introduces a refined way to package multiple transactions into a single operation. This capability supports diverse processing modes, including the "All or Nothing" setting, which is critical for delivery-versus-payment (DvP) workflows. By bundling an asset transfer with its corresponding payment, the system ensures that a failure in one leg prevents the entire operation from executing, thereby reducing counterparty risk for institutional users.

Ayo Akinyele, head of engineering at RippleX, confirmed that internal development is underway, though the company has not yet disclosed the identities of the specific asset managers preparing to utilize the feature. The current progress follows a comprehensive security overhaul. In February, researchers identified a signature-validation flaw in the original Batch proposal, prompting developers to pull the amendment and implement more rigorous authorization safeguards. The updated version, integrated into xrpld 3.3.0, underwent extensive adversarial testing and third-party assessments to ensure network integrity.

For the amendment to go live, the 80% validator support threshold must remain unbroken for a full 14-day period. While the current support level of approximately 85% keeps the September 29 target date within reach, the window remains conditional. If validator consensus dips below the required 28 votes before the countdown concludes, the process will reset. This rollout coincides with a broader trend of institutional interest in the XRP Ledger, following recent pilot programs involving firms like JPMorgan and Mastercard to test tokenized asset settlements.