XRP Ledger’s Batch V1.1 amendment is still above the required validator support level, keeping its possible September 29 activation on track. Ripple says asset managers and other projects are already preparing to use the feature, although the companies involved have not been publicly named.
Batch V1.1 can combine up to eight transactions into one operation. This allows different parts of a payment or asset transfer to be completed together. One important use is delivery-versus-payment, where an asset and its payment can settle in the same atomic transaction.
The feature has four processing modes: All or Nothing, Only One, Until Failure, and Independent. With All or Nothing, the entire group must succeed or the batch does not take effect. This can help reduce the risk of one part of a linked transaction going through while another part fails.
As of September 20, Batch V1.1 had 30 votes from 35 tracked trusted validators. The XRP Ledger requires at least 80% support for 14 straight days before an amendment can activate. That means the current 30 votes are above the required 28-vote level.
The current voting period began on September 15 at 14:06:41 UTC. If support remains above the required level for the full 14 days, activation could take place shortly after the same time on September 29. However, the date is not guaranteed because validators can change their votes during the countdown.
Batch V1.1 was included in xrpld version 3.3.0, released on August 6. It replaced the original Batch proposal after developers discovered a serious signature-validation problem earlier this year.
The original version was stopped before it could activate on the XRP Ledger mainnet. Researchers found that under certain conditions, the system could stop properly checking transaction signatures after encountering a newly created account. Developers said this could have allowed an unauthorized transaction to be included without the account owner’s private key.
Developers changed the signing and authorization system for Batch V1.1, adding stronger checks and removing the issue that could cause the validation process to incorrectly succeed. Another 11 issues involving signatures, authorization checks and possible server crashes were also addressed during later security work.
The Batch design has also received updates from the developer ecosystem. Support for the revised Batch V1.1 signing format was added to the JavaScript binary-codec in version 2.9.0 in August.
Ripple says some asset managers and commercial projects are already being built with Batch V1.1 in mind. However, the company has not yet identified those firms or provided firm production launch dates.
The feature could be useful for tokenized assets and institutional settlement because it allows multiple related transactions to be tied together. It can also support uses such as multi-account swaps, platform fees and other more complex transaction structures.
The broader XRP Ledger ecosystem is also seeing more activity around tokenized assets and institutional settlement. Batch V1.1 does not require the use of XRP for the asset being transferred. It works at the transaction level and can group supported XRPL transactions involving different accounts and assets.
For now, the main focus is the validator vote. With 30 of 35 tracked validators supporting Batch V1.1 as of September 20, the amendment remains above the required threshold. If that support stays uninterrupted for the full 14-day period, the current projection points to activation on September 29.
