XRPL Batch Upgrade Delayed 10 Days After Support Falls Below 80%

The XRP Ledger’s BatchV1_1 upgrade will not activate on Sept. 29 as previously expected after validator support briefly fell below the network’s required threshold, resetting the amendment’s two-week countdown.

BatchV1_1 regained support from 30 of 35 trusted validators on Sept. 25, putting its earliest activation around Oct. 9 at 14:46 UTC if that backing remains in place. The XRP Ledger’s official amendment rules require an amendment to maintain support from more than 80% of trusted validators continuously for two weeks before it can become part of the live network.

That means even a short dip below the threshold wipes out the accumulated countdown. Once support returns, the full two-week period begins again.

The Delay Shows Why XRPL Upgrade Dates Are Conditional

Coinpaper had previously covered the expected Sept. 29 Batch activation, while an earlier explainer looked at how XRPL amendments are actually controlled.

This latest delay demonstrates the distinction in real time: releasing code does not make a feature live, and even reaching the required validator majority does not guarantee a fixed activation date.

XRPL’s amendment process records when a change gains majority support. If support later falls back to 80% or below, the network records a lost-majority event and removes the pending amendment from its countdown until enough validators support it again.

Batch Could Still Change How Multi-Step XRPL Transactions Work

The feature itself has not changed.

BatchV1_1 would allow users and applications to package between two and eight transactions into one batch. The official Batch specification supports four execution modes: All or Nothing, Only One, Until Failure and Independent.

The most notable is All or Nothing. Developers could structure an operation so every step succeeds together or the entire batch fails.

For example, an application could transfer a tokenized asset and payment in the same operation, reducing the risk that only one side completes. XRPL documentation also gives examples involving NFT minting, offers, platform fees and multi-account swaps.

That is why the upgrade has attracted interest beyond simple transaction bundling.

BatchV1_1 also carries an important security history. It replaces an earlier Batch implementation that developers withdrew before activation after discovering a critical authorization flaw. The corrected version was incorporated into the later xrpld release and entered the amendment process separately.

Coinpaper covered that security backstory when the new activation window first appeared.