Batch is an XRP Ledger feature that lets an account submit up to eight inner transactions as one group, all or nothing. A first version was pulled after a bug. The rebuilt one was due to switch on in early October, and we couldn’t confirm that it did.
| Item | Detail |
|---|---|
| Specification | XLS-56 |
| Group size | Up to eight inner transactions (xrpld 3.3.0 release notes) |
| Rebuilt amendment | BatchV1_1, shipped in xrpld 3.3.0 on August 6, 2026 |
| Earliest activation | October 9, 2026, per reports |
| Status | No source directly confirms BatchV1_1 is enabled; check a live amendment tracker |
What Batch does
Normally each XRP Ledger transaction stands alone. If a workflow needs two or more steps, one can succeed while another fails. Batch removes that gap. Outlets covering the amendment describe uses such as swapping one asset for another in a single step with no partial fill, bundling a customer payment with a service fee, and delivery-versus-payment settlement, where an asset and its payment move together. Those are intended uses. We haven’t seen production deployments reported yet, so treat them as capabilities, not results.
Two rounds of bugs
The xrpld 3.3.0 release notes say the original Batch amendment was disabled in version 3.1.1. CryptoMeter reports that developers found a critical signature-validation flaw during testing, and that the redesign received additional work on signatures, authorization checks and potential server crashes. Both outlets say it did not reach the live network as an enabled feature. We could not open an official write-up of the original flaw, so we don’t describe its mechanics.
A second issue came later. A vulnerability summary relayed by KuCoin says versions 3.3.0 and 3.4.0 did not enforce a required wrapper field on Batch inner transactions. Servers could disagree about validity, which risked network liveness problems if BatchV1_1 activated without a fix. The fixBatchV1_2 amendment in xrpld 3.4.1 addresses this. The summary says no funds were lost and no keys were exposed. KuCoin relays this from other news outlets, not from Ripple directly.
How the vote went
On September 19, 30 of 35 tracked validators supported BatchV1_1 (about 86%, per CoinDesk as cited by CryptoMeter), which started a 14-day countdown aimed at September 29. In late September support dipped below 80% and the countdown reset, putting the earliest date at October 9 (CryptoMeter, September 26). On October 8, Bitcoinist had it still in its activation window, expected around October 9 if support held. A KuCoin relay reports fixBatchV1_2 activated on October 9, with BatchV1_1 due the same day.
Who Benefits and How
- Developers building swaps, payments with fees, or delivery-versus-payment settlement on the XRP Ledger get an all-or-nothing group without a trusted middleman.
- End users would feel it only through apps that adopt it, and we’ve seen no production deployments yet.
- Banks and exchanges: Batch is a technical building block and does not by itself mean any bank or exchange has adopted it.
What the numbers don’t show
Some coverage quotes an 82.86% approval figure, but that number belongs to a different amendment, fixCleanup3_3_0. The Batch figure we can source is 30 of 35 validators on September 19. The September 29 date didn’t hold, which shows how fragile activation dates are. Claims that Batch saves users escrow fees have no source, and Batch is not a replacement for every escrow use. Audit and contest names that some outlets cite were not verified against official sources, so we leave them out.
Quick answers
How many transactions can a batch hold? Up to eight inner transactions, per the xrpld 3.3.0 release notes.
Is Batch live on the XRP Ledger? It was due to activate on or after October 9, 2026, and a related fix is reported active. We could not confirm the final state, so verify on an amendment tracker.
Does Batch remove the need for escrow? For some simple swaps, an atomic group can replace a trusted middleman. Complex or conditional deals may still need escrow.
Why did the first version fail? A critical bug was found, and the amendment was disabled in xrpld 3.1.1. Outlets describe it as a signature-validation flaw, but we could not confirm details from a primary source.
Sources
- XRPL.org: Introducing XRP Ledger version 3.3.0 (Aug 6, 2026)
- CryptoMeter: XRP Ledger Batch Upgrade Slips to Oct. 9 After Validator Support Falls Below Threshold (Sep 26, 2026)
- Bitcoinist: XRP Ledger Batch Upgrade Nears Activation After Validator Vote Reset (Oct 8, 2026)
- AltcoinBuzz: XRP Ledger Fix Wins Every Validator Vote, Activates Oct 9 (Oct 6, 2026)
- KuCoin News: Ripple Discloses Two Vulnerabilities in xrpld 3.4.1 (accessed Oct 13, 2026)
