The XRP Ledger Batch V1.1 amendment is on track for activation shortly after September 29, 2026, as 30 of 35 tracked validators maintain support above the required 80% threshold. The upgrade allows bundling up to eight transactions to settle atomically, supporting delivery-versus-payment use cases. Ripple reports that undisclosed asset managers are preparing to use the feature, which was rebuilt and heavily audited following a critical signature flaw in the original V1.0 version in February 2026.
Batch V1.1 activation timeline
- ▪The XRP Ledger Batch V1.1 amendment shipped with xrpld version 3.3.0 on August 6, 2026.
- ▪The XRP Ledger Batch V1.1 amendment is projected to activate shortly after September 29, 2026 at 14:06:41 UTC if validator support remains above the required threshold.
- ▪The 14-day activation countdown for XRP Ledger Batch V1.1 began on September 15, 2026 at 14:06:41 UTC.
Validator support threshold maintenance
- ▪The XRP Ledger requires at least 80% validator support, equivalent to 28 out of 35 tracked votes, to be maintained for 14 consecutive days to activate an amendment.
- ▪If validator support for XRP Ledger Batch V1.1 falls below the 80% threshold during the countdown, the clock pauses and a new uninterrupted 14-day period is required.
- ▪As of September 20, 2026, the XRP Ledger Batch V1.1 amendment, shipped in xrpld version 3.3.0, had support from 30 of 35 tracked validators, representing approximately 85% support
Transaction bundling settlement modes
- ▪The XLS-56 specification defines four processing modes for Batch transactions: All or Nothing, Only One, Until Failure, and Independent.
- ▪The All or Nothing setting in XRP Ledger Batch V1.1 requires the entire group of transactions to execute successfully or prevents the batch from taking effect.
- ▪The XRP Ledger Batch V1.1 feature allows users to bundle between two and eight inner transactions into a single parent operation.
Delivery-versus-payment use cases
- ▪XRP Ledger Batch V1.1 supports delivery-versus-payment transactions by linking an asset transfer and the payment for that asset within the same atomic operation
- ▪Exchanges, wallets, and marketplaces can use XRP Ledger Batch V1.1 to package a customer payment with a service charge as a single grouped operation.
Asset manager commercial preparation
- ▪Ripple has not publicly disclosed the identities of the specific asset managers or commercial partners building around XRP Ledger Batch V1.1.
- ▪RippleX head of engineering Ayo Akinyele stated that commercial projects and asset managers are preparing to use XRP Ledger Batch V1.1 ahead of Batch V1.1's activation
Batch V1.0 security flaw
- ▪The signature-validation flaw discovered in XRP Ledger Batch V1.0 on February 19, 2026 could stop checking batch signers after encountering a newly created account, potentially allowing unauthorized transactions
- ▪RippleX's expanded security review conducted before returning XRP Ledger Batch V1.1 to the validator vote in September 2026 included internal adversarial testing, AI-assisted analysis, a Sherlock attack contest, and assessments by Halborn and Common Prefix
- ▪The Batch V1.0 vulnerability never became active on the XRP Ledger mainnet, and no user funds were exposed or put at risk.
- ▪Developers withdrew the original Batch V1.0 proposal after security researcher Pranamya Keshkamat and Cantina AI's Apex tool identified a critical signature-validation flaw on February 19, 2026.
Story comments
Loading comments…