Ripple says asset managers and other commercial projects are already preparing to use the XRP Ledger’s Batch V1.1 upgrade as the amendment nears a possible September 29 activation.
Batch V1.1 lets asset managers and other commercial projects group two to eight XRP Ledger transactions into a single operation. One of its main modes lets all linked transactions succeed together or fail together, which can support delivery-versus-payment transactions where an asset and its payment need to settle at the same time.
The amendment had support from 30 of 35 tracked validators as of September 20, above the 28 votes needed to maintain the XRP Ledger’s 80% supermajority threshold.
The 14-day activation countdown began on September 15 at 14:06:41 UTC, putting Batch V1.1 on track to activate shortly after the same time on September 29 if support remains above the required level.
Asset Managers Are Preparing for Batch V1.1
RippleX Head of Engineering Ayo Akinyele said commercial projects are already being developed around Batch V1.1, including work involving asset managers.
Ripple has not named specific firms or announced launch dates for those integrations. More details are expected after the feature activates and commercial plans are finalized.
One of the clearest institutional use cases is delivery-versus-payment. In a traditional asset transfer, one side may send an asset while another side separately sends payment.
Batch V1.1 can bundle both transfers into one atomic operation, so they settle together or fail together, which could help with tokenized securities and other financial assets where reducing settlement risk matters more than processing a payment quickly.
Batch V1.1 Can Group Up to Eight Transactions
The XLS-56 specification allows one Batch operation to contain between two and eight inner transactions. Batch V1.1 supports several processing modes:
- All or Nothing
- Only One
- Until Failure
- Independent
The All or Nothing mode is especially relevant for financial settlement because every transaction in the batch must succeed for the operation to complete.
Exchanges, wallets, and marketplaces could also use the feature to combine customer transactions with service fees.
For example, a platform could process a customer payment and its fee in one batch instead of submitting two unrelated transactions, reducing the risk of one part completing while another fails.
| Mode | Behavior |
|---|---|
ALLORNOTHING | All inner transactions must succeed for the batch to take effect. If even one fails, the entire batch is discarded with no effect on the ledger state. |
ONLYONE | Only the first transaction to succeed in the bundle is applied. All subsequent transactions are either skipped or ignored. |
UNTILFAILURE | Executes inner transactions sequentially in order until a failure occurs. Successful transactions up to that point remain, but all transactions following the failure are discarded. |
INDEPENDENT | Evaluates and applies every inner transaction independently. One operation’s success or failure has no bearing on the execution of the others. |
Table 1. Supported XRP Ledger Batch V1.1 Processing Modes
September 29 Activation Is Still Conditional
Batch V1.1 has entered the XRP Ledger amendment activation process, but September 29 is not guaranteed.
The XRP Ledger requires an amendment to maintain support from at least 80% of trusted validators for two consecutive weeks before activation.
If support falls below the required threshold before the countdown ends, the majority is lost, and the two-week activation process must restart once enough validators support the amendment again.
As of September 20, Batch V1.1 had 30 votes out of 35 tracked validators. The minimum needed to maintain the current threshold is 28.
We previously covered the amendment when it was still one vote away from reaching the activation threshold. You can read that earlier update in our XRP Ledger Batch V1.1 upgrade coverage.
The latest development is that Batch V1.1 has moved beyond that stage and entered the 14-day activation window.
Batch V1.1 Replaces an Earlier Version With a Critical Bug
The current amendment is a rebuilt version of the original Batch implementation. Developers withdrew Batch V1.0 after researchers identified a critical signature-validation issue. Under certain conditions, the flaw could have allowed transactions belonging to another account to be included without proper authorization.
The vulnerable amendment had not activated on the XRP Ledger mainnet, so it did not govern live transactions, and the feature did not expose any user funds.
RippleX then redesigned parts of the signing and authorization system before returning the amendment to validators.
Batch V1.1 was included in xrpld version 3.3.0, released on August 6. The updated amendment replaces the original Batch implementation and addresses the earlier security flaw.
Security Review Expanded Before the New Vote
The redesigned version went through a broader security review before reaching its current validator vote.
RippleX said testing included internal adversarial work, AI-assisted analysis, a Sherlock security competition, and assessments from security firms Halborn and Common Prefix.
The additional review matters because the batch changes how authorization works across several linked transactions, not just a simple interface feature.
The earlier bug was serious enough to stop the first amendment before activation, so the security workaround in V1.1 is an important part of the upgrade’s institutional case.
Why Asset Managers Could Use Batch V1.1
The institutional use case goes beyond processing several transactions at once.
Asset managers dealing with tokenized assets may need ownership transfer, payment, and related fees to settle together.
Without atomic settlement, one side of a transaction could complete while another fails, leaving counterparties exposed.
Batch V1.1’s All or Nothing mode can reduce that settlement risk by treating the linked actions as one operation.
That makes delivery-versus-payment one of the more practical use cases for institutions considering the XRP Ledger for tokenized assets and settlement infrastructure.
Ripple has not identified the asset managers preparing deployments, so the size and scope of those projects remain unknown.
Batch V1.1 Could Also Help Exchanges and Payment Platforms
Exchanges, wallets and payment platforms could use Batch V1.1 to combine several related actions into one coordinated transaction flow.
For example, a payment platform could pair a customer transfer with a service fee. A marketplace could group an asset transfer with its payment. A trading application could also use Batch to coordinate several actions that need to complete in a specific order.
The benefit is not simply fewer transactions. The larger advantage is control over how those transactions succeed or fail together.
What Comes Next
Batch V1.1 needs to maintain at least 80% validator support through the full two-week amendment window. If the current majority holds, the upgrade should activate shortly after 14:06 UTC on September 29.
After activation, attention will shift from validator voting to actual usage.
Ripple has said it expects to share more information about asset managers and other commercial projects once the feature is live. Those deployments will better test whether Batch V1.1 becomes meaningful infrastructure for institutional settlement rather than remaining mainly a developer feature.
What this means for you: Batch V1.1 is close to activation, but the bigger milestone will be what happens after launch. Validator approval enables the feature, while real adoption will depend on whether asset managers, exchanges, and other projects actually put Batch-based systems into production.
