An upgrade to the XRP Ledger (XRP) that was expected to activate on Sept. 29 has been pushed back by at least 10 days after validator support briefly fell below the level required to switch it on.

The feature, called Batch, would let users submit up to eight transactions together. Its all-or-nothing option could allow a buyer to pay for a tokenized asset and receive it in a single operation, preventing either side of the trade from completing alone. That atomicity matters most for tokenized-asset settlement, where a payment that goes through without the corresponding delivery — or the reverse — leaves one party short.

RippleX's head of engineering, Ayo Akinyele, previously told CoinDesk () that projects were being built around Batch and that Ripple would share more about its work with asset managers once the feature went live.

“Some projects are already being built with Batch in mind, so activation would allow that work to move closer to production,” he said. He did not name the partners or provide launch dates.

The corrected upgrade, formally named BatchV1_1, regained support from 30 of 35 trusted validators on Sept. 25, according to the XRPL amendment dashboard. That reset started a fresh two-week countdown, putting its earliest activation at Oct. 9 at around 14:46 UTC if support holds.

Validators are operators that check transactions and vote on changes to the network. XRPL upgrades must retain support from more than 80% of trusted validators for two consecutive weeks. Losing that support wipes out the accumulated time, even if the votes return shortly afterward — which is how a brief dip managed to push activation past Sept. 29.

Batch had been counting down since Sept. 15. It is already the second attempt at introducing the feature, after developers withdrew the original version over a critical signature-checking flaw before activation, a withdrawal that stopped the flawed code from going live. The corrected implementation shipped in August with version 3.3.0 of the software that runs the ledger.

A separate upgrade that lets account owners delegate specific tasks also lost the support needed to complete its countdown. The upgrade, known as PermissionDelegationV1_1, would allow a business to authorize another account to perform approved actions without sharing the signing keys that control its funds — separating day-to-day operations from custody of the assets themselves. A token issuer, for instance, could assign payment and compliance duties to different operational accounts.

That upgrade lost its qualifying support on Sept. 23 and regained it a day later, moving its earliest activation from Oct. 5 to Oct. 8 at around 21:25 UTC. Both features now sit in fresh two-week windows governed by the same threshold, meaning any further lapse in validator support would push the dates out again — with the amendment dashboard showing whether the tallies hold.