Key facts
- RippleX has submitted Batch V1.1, a rebuilt atomic-transaction amendment for the XRP Ledger, for validator voting.
- The previous version, Batch V1.0, was pulled in February 2026 due to a signature-validation flaw.
- The flaw could have allowed unauthorized transactions by skipping signer verification if an account did not exist.
- Batch V1.1 has been rebuilt with a root-cause fix and undergone audits from Halborn and Common Prefix.
- The amendment requires 80% of trusted validators to vote 'Yes' for 14 consecutive days to activate.
- Support for Batch V1.1 was at approximately 77% among UNL validators as of September 14, 2026.
RippleX has submitted Batch V1.1, a rebuilt atomic-transaction amendment for the XRP Ledger (XRPL), for validator voting. The update aims to enable atomic settlement and linked payments, a feature previously pulled due to a critical security flaw in Batch V1.0.
On February 19, 2026, security researchers Pranamya Keshkamat and Cantina AI identified a logic error in the Batch v1.0 codebase. This flaw, located within the checkBatchSign function, could have allowed an attacker to execute victim-account transactions without proper authorization if a signer account did not yet exist on the ledger. The feature was subsequently pulled from the XRP Ledger 3.3.0 upgrade.
Mayukha Vadari, a RippleX staff engineer, announced on September 14, 2026, that the rebuilt Batch V1.1 is now included in xrpld v3.3.0 and is open for validator voting. The rebuild involved a root-cause fix, a review by four senior engineers, an attackathon, and security audits by Halborn and Common Prefix. Reviewers identified 11 additional issues, including signature edge cases and authorization checks, all of which RippleX states have been fixed in the current version.
The Batch V1.1 amendment allows up to eight transactions from different accounts to execute atomically within a single ledger close, meaning either all transactions succeed or none do. This functionality is designed to support atomic settlement, paired payments, and delivery-versus-payment without requiring a smart-contract layer. RippleX views this as XRPL's answer to coordinated multi-party settlement capabilities found on other blockchains.
For the amendment to activate, it requires 80% of trusted validators to vote 'Yes' for 14 consecutive days. As of September 14, 2026, support stood at approximately 77% (27 out of 35 UNL validators). One additional 'Yes' vote would initiate the 14-day countdown, while a reversal would reset it. Ripple has already voted in favor of BatchV1_1 and other 3.3.0 amendments.