BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
Altcoins

XRP Ledger’s Batch Upgrade Is Near. What Changes on September 29?

The XRP Ledger could gain a new way to carry out several linked transactions in one operation on September 29. That date is conditional: the BatchV1_1 amendment must keep the required validat

AnonymousCryptoCompass newsroom
September 24, 2026
2 min read
NEWS
Hero article visual / chart / editorial image
CryptoCompass editorial visual for altcoins coverage.

The XRP Ledger could gain a new way to carry out several linked transactions in one operation on September 29. That date is conditional: the BatchV1_1 amendment must keep the required validator support throughout its two-week countdown.

The feature would let developers put up to eight transactions in a batch, according to the XRP Ledger’s Batch documentation. The practical change is control over what happens when one step fails.

For example, an app could mint an NFT and offer it for sale together. In one Batch mode, if the offer fails, the mint is reversed too. That prevents a user from being left with only half of the intended operation.

A Batch Does Not Always Mean “All or Nothing”

This distinction matters. BatchV1_1 provides four modes, and the developer chooses which fits the transaction.

Mode What happens All or Nothing Every step succeeds, or none does Only One Stops after the first successful step Until Failure Applies steps until one fails Independent Attempts every step, even if another fails

That flexibility could help with swaps, platform fees and other operations that now require several separately submitted transactions. The All or Nothing mode is especially useful when two sides of an exchange should settle together, an application explored in the earlier look at why asset managers are watching Batch.

Is September 29 Guaranteed?

No. XRPL amendments need more than 80% support from trusted validators for two consecutive weeks. The latest published count I could verify was 30 of 35 validators as of September 22, above the required level. If support falls to 80% or less before activation, the countdown resets. A scheduled activation therefore does not mean the feature is live today.

BatchV1_1 also has an important backstory. Developers stopped an earlier Batch amendment after finding a critical authorization flaw before it activated on mainnet. The replacement addresses that flaw and went through the amendment process separately.

Coinpaper has already covered the proposed September 29 activation. The next milestone is whether validator support holds and the network enables BatchV1_1. After that, the measure of its usefulness will be whether developers build applications that actually use its four modes.