Ripple says asset managers are preparing for XRP Ledger Batch V1.1, a payments upgrade that lets multiple linked transactions settle as a single, all-or-nothing operation. The amendment can group up to eight XRP Ledger transactions under one parent operation, so that either every transaction completes or the entire group is cancelled. The upgrade allows asset transfers, payments and platform fees to settle together, or fail together, as one operation.

Support for the feature currently stands at 30 of 35 tracked validators, according to the XRPL Dashboard, a tally above the 80% supermajority threshold the amendment must hold for activation to proceed. An amendment needs 28 votes to start its activation countdown, a process that began on September 15 at 14:06:41 UTC. Under the XRP Ledger's amendment process, protocol changes take effect only after sustained supermajority support among validators, a mechanism designed to ensure broad consensus before changes reach the live network. If support stays above the required 80% threshold for fourteen consecutive days, activation could follow on September 29.

Ayo Akinyele, head of engineering at RippleX, said commercial projects are already building with XRP Ledger Batch V1.1 in mind.

Conditional Path to Activation

The vote gives Batch V1.1 a conditional route to going live. Validators can change their positions at any point during the countdown. If support falls below 80%, the clock stops, and a new fourteen-day period must begin once the amendment regains the threshold.

Batch V1.1 groups transactions under a parent operation. Users can submit as many as eight linked transactions, with each transaction retaining its individual details. The all-or-nothing setting prevents partial settlement when any single transaction in the group fails.

Unlike a multi-step workflow, the grouped operation gives counterparties an explicit settlement condition: if one leg fails, the ledger does not complete the other. That design could simplify settlement for funds, trading venues and token issuers on the XRP Ledger, and it offers developers a way to combine transfers without relying on callbacks or manual reconciliation. The feature itself does not guarantee adoption, since projects still need to complete testing, compliance and preparation work.

Delivery-Versus-Payment Drives the Use Cases

The grouping function is particularly relevant for asset managers building digital markets. A fund can transfer a tokenized asset while receiving payment within the same ledger operation, giving Batch V1.1 a direct role in atomic settlement.

Akinyele identified delivery-versus-payment as a key use case. The method links asset delivery and payment rather than asking one party to send first, which can reduce exposure to incomplete settlement during a trade.

Ripple also pointed to fees as another application. Exchanges, wallets and marketplaces can attach service charges to a customer transaction, allowing the payment and the fee to process as one grouped operation.

RippleX has not named the commercial projects working with the feature. Akinyele said more details will follow after partners formally finalize their plans and launch timing, adding that activation would move the development work closer to production.

A Return a Security Flaw

The planned activation follows the withdrawal of Batch V1.0. Researchers identified a critical signature-validation flaw in February. Under certain conditions, the code could stop checking signatures early, allowing an attacker to include transactions from another account without authorization.

Validators had not activated the original amendment when developers withdrew it. The vulnerable code therefore never controlled the live ledger, and the flaw exposed no user funds directly.

RippleX used the incident to redesign parts of the signing and authorization model. The replacement shipped in xrpld version 3.3.0 on August 6, and Ripple said the code now under consideration matches that release.

The review was broadened to include AI-assisted analysis and a Sherlock attack contest. Security firms Halborn and Common Prefix conducted assessments, and RippleX applied internal adversarial testing before seeking validator approval. The company said the expanded process supported the amendment's return to the vote.

Akinyele said the team raised the review standard, addressed the defect and submitted Batch V1.1 for another validator vote.

Under the current schedule, the amendment window runs through September 29. Support must remain at or above 80% throughout the period. Any decline below that level would pause activation and require another countdown once support recovers.

Source: Blockonomi