XRP (XRP) Ledger's BatchV1_1 Amendment Nears 80% Threshold With 68% Validator Support

BatchV1_1 Support Reaches 68%

The XRP Ledger is closing in on activation for BatchV1_1, the reworked amendment that has been pending since the original Batch release was pulled earlier this year. Validator backing for the upgrade reached roughly 68% as of Sept. 7, based on community-tracked voting data for the network. That figure still sits below the 80% consensus bar the ledger requires, but the gap has narrowed enough for ecosystem participants to start mapping a possible activation timeline for XRP Ledger and its native asset.

Under the ledger's amendment process, a proposed change must win support from at least 80% of validators and then hold that majority for 14 consecutive days before it takes effect automatically. If backing falls below the threshold at any point in that window, the two-week countdown resets and the process starts over. Current tracking suggests that if the 80% line is crossed and maintained, BatchV1_1 could go live before the end of September — though nothing is guaranteed until the countdown completes. The amendment's road here has been turbulent: the initial Batch version was disabled after a critical bug surfaced, forcing a rework that was folded into XRP Ledger software version 3.3.0, shipped on Aug. 6. Node operators running that release already carry the amended code, so what remains is the voting step. At 68%, the upgrade needs roughly 12 additional percentage points of validator support before the observation period can even begin, making the coming voting rounds the decisive signal for whether the amendment advances or stalls, as some past XRPL proposals have.

What BatchV1_1 Changes for Developers

Technically, BatchV1_1 addresses a long-standing limitation: the protocol has offered no native way to group separate transactions. Each action on the chain is an independent transaction, forcing applications with multi-step workflows to bolt custom infrastructure onto the network. The amendment removes that constraint by letting developers package up to eight transactions inside a single transaction, with explicit definitions of how the bundled steps depend on one another. A community post that carried the latest validator tally argued the change would unlock substantial new use cases for the XRP ecosystem, a view that has circulated among builders since the reworked amendment entered voting.

latest validator tallyhttps://x.com/xmoonkie/status/2096943070927311139

The practical reach is broad. A payment service could combine a transfer and its fee settlement atomically, so no step executes without the others. market makers and liquidity operators could pair order placement with rebalancing legs so partial executions cannot strand positions. XRPL validator Vet, a frequent commentator on ledger upgrades, said builders have waited a long time for the functionality and noted it should make direct charging for services easier, closing the free-rider problem where users benefit from an app without paying. Unlike layer-3 scaling designs that move execution off a base chain, or application-specific blockchains that spin up dedicated networks, batching keeps every step of a complex workflow on the ledger itself — preserving XRPL's single-source settlement guarantees and expanding which classes of applications can be built on it at all. Readers tracking the market in real time can follow live spot and futures prices on Gate.

Two-Week Countdown Ahead

COINOTAG's read: the release notes attached to version 3.3.0 are the authoritative record here — BatchV1_1 is in the code that shipped Aug. 6, so activation is now purely a validator-voting question, not an engineering one. The upgrade lands amid a busy stretch for the ledger: Ripple re-locked 700 million XRP in escrow, burned 1,363,614 RLUSD in a cross-chain remint, and a BIS statistics-verification trial tested the network's speed. For more on the asset, see our XRP coverage hub. If support clears 80% and holds for the full window, developers gain an eight-transaction batching primitive by early October; if the vote stalls, the consensus process simply keeps counting.