XRP Ledger Batch Upgrade One Validator Vote Away
After extra bug fixes, RippleX has put Batch V1.1 back up for a vote; the upgrade is meant to make linked payments on the XRP Ledger safer and easier.

Key Takeaways
- The Batch V1.1 upgrade on the XRP Ledger has 27 of the 35 trusted validators behind it and is still one vote short of activation.
- Batch V1.1 bundles up to eight linked transactions into one operation and is meant to make linked payments simpler and more reliable.
- RippleX removed 11 additional bugs and had the upgrade reviewed again after earlier problems with the withdrawn Batch version.
The Batch V1.1 upgrade on the XRP Ledger is close to going live. The proposal now has 27 of the 35 trusted validators behind it and is still one vote short of kicking off the activation phase, after RippleX removed 11 more bugs from the software.
What Batch V1.1 Does
Batch V1.1 is meant to make linked payments on the XRP Ledger easier by combining up to eight linked transactions into one operation. In practice, that means two parties could, for example, complete a token swap at the same time, so one payment does not go through while the other fails.
According to RippleX, the upgrade has now been included in xrpld 3.3.0 and is open for voting. The XRP Ledger uses a threshold of more than 80% support among trusted validators before a change can go into effect. With 77% support, the outcome is still not decided, but one more vote would start the two-week countdown to activation.
Why the Vote Still Matters
The current vote carries extra weight because the first Batch version was withdrawn earlier this year after a serious bug. Researchers found a vulnerability that, under certain conditions, could let someone include transactions from another account without that user's permission.
RippleX says the new version was reviewed again by four senior engineers, a public bug contest, and audits from Halborn and Common Prefix. The latest review still found 11 issues, including problems around signatures, authorization checks, and errors that could crash servers. A critical bug flagged by Common Prefix could, according to the company, have made it possible to misuse permission that had already been granted.
Relevant for XRP Users
For users and teams building on the XRP Ledger, Batch is especially relevant because it can reduce mistakes with linked payments. Wallets and marketplaces can also use the feature to process, for example, a customer payment and platform fee in one go. That makes the vote not just technically interesting, but also practical for teams working with XRP and other tokens on the network.
RippleX also says commercial projects that want to use Batch are already under contract or in development, although those names have not been revealed yet.