Batch V1.1 aims to allow users to consolidate up to eight related transactions into a single operation, with 27 out of 35 trusted validators currently in favor of the change.
By Shaurya Malwa|Edited by Omkar GodboleUpdated 9 hrs agoPublished 10 hrs ago2 min readMake preferred on ShareShare this articleCopy linkX (Twitter)LinkedInFacebookEmailMake preferred on XRP Ledger is on the brink of a major payments upgrade. (Ripple Labs)SummaryShow- The Batch V1.1 upgrade for XRP Ledger is just one validator vote away from initiating a two-week countdown to activation.
- Developers have resolved 11 additional issues, including those related to signatures and server crashes, after withdrawing a prior version due to a critical security flaw.
- This feature could facilitate seamless token swaps, customer payments, and platform fees in a single operation, with RippleX indicating that commercial projects are either under contract or in development.
The XRP Ledger, a decentralized blockchain designed for global transactions, is just one vote short of enabling the bundling of related transactions into a singular operation, enhancing the efficiency of multi-step transfers.
The proposed Batch V1.1 upgrade would permit users to merge as many as eight linked transactions into one operation. This bundling process ensures that either all transactions succeed or fail as a unit, thereby mitigating the risk of incomplete transfers.
For instance, in a token swap, both parties could guarantee that their transactions are executed simultaneously rather than risk one completing while the other does not.
As of a recent snapshot on Tuesday, 27 out of 35 trusted validators, approximately 77%, have expressed support for the upgrade. Since XRP Ledger modifications require 80% approval to proceed, the absence of just one validator's vote is crucial at this moment, and one additional vote will trigger the two-week countdown to activation.
The support level must stay above this threshold for the entire 14-day period before the upgrade can be enacted, during which validators have the option to modify their votes.
This activation effort comes on the heels of 11 significant bug fixes. On Monday, Ripple's development unit, RippleX, outlined these corrections in a technical review of Batch V1.1, which is not yet operational on the primary network.
The Batch V1.1 amendment was included in the xrpld 3.3.0 release and is currently open for voting.
— Mayukha Vadari (@msvadari) September 14, 2026
After identifying a v1.0 signature bug in February (prior to Mainnet, with no funds at risk), we re-engineered it: root-cause fix, four senior reviewers, a Sherlock attackathon, and audits from Halborn and Common Prefix. We…
The latest technical review uncovered 11 issues related to signatures, authorization checks, and bugs that could potentially cause server crashes. One flaw, classified as critical by security firm Common Prefix, could have permitted an attacker to reuse a user's signed permission to carry out more transactions than intended.
RippleX noted that the review involved four senior engineers and included audits from Halborn and Common Prefix, along with a public security competition and automated testing processes.
Additionally, RippleX indicated that commercial projects utilizing Batch are currently under contract or in development, although specific company names have not been disclosed. CoinDesk has inquired whether RippleX can reveal which companies are set to use Batch and if the 11 fixes have been independently verified against the version currently being voted on by validators.
Wallets and marketplaces may also leverage this feature to combine customer payments with platform fees, ensuring both transactions are processed concurrently.
This development follows a more severe issue identified earlier this year, where researchers found a vulnerability in the original Batch proposal that could, in specific circumstances, allow an attacker to initiate transactions from another user's account without their consent.
Read More: XRP Ledger upgrade reinstates features previously withdrawn due to critical bugs
This problematic version never reached the live network. Developers replaced it in the XRP Ledger's 3.3.0 software release on August 6 and subjected the new iteration to another series of internal reviews, external audits, and public bug testing.