The feature would let users bundle up to eight transactions, including asset-and-payment transfers, but a brief drop below the network’s 80% support threshold restarted its two-week activation clock.

• The XRP Ledger’s Batch upgrade was delayed by at least 10 days after validator support briefly fell below the required threshold, putting its earliest activation at Oct. 9 if support holds.
• Batch would allow users to submit up to eight transactions together, including all-or-nothing exchanges that could enable simultaneous payment and delivery of tokenized assets.
• A separate upgrade allowing account owners to delegate specific tasks without sharing signing keys was also delayed and could activate as early as Oct. 8.

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

The feature, called Batch, would let users submit up to eight transactions together. Its all-or-nothing option could let a buyer pay for a tokenized asset and receive it in one operation, preventing either side of the trade from completing alone.

RippleX’s head of engineering, Ayo Akinyele, previously told CoinDesk that projects were being built around Batch and that Ripple would share more about 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 give 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 started a fresh two-week countdown, putting its earliest activation at Oct. 9 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.

Batch had been counting down since Sept. 15. It is already a second attempt at introducing the feature, after developers withdrew the original version over a critical signature-checking flaw before activation. 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 so-termed PermissionDelegationV1_1 would allow a business to authorize another account to perform approved actions without sharing the signing keys that control its funds. A token issuer could assign payment and compliance duties to different operational accounts.

Read More: XRP Ledger retries upgrade that lets banks split payment and compliance duties

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 around 21:25 UTC.

As stablecoins move into regulated finance, APAC is becoming a key proving ground. This report maps the region’s rules, use cases, and RLUSD’s role.