InvestNot yet confirmed elsewhere1 publisher3 min readPublished
Thirty of 35 XRP Ledger validators switch on bundles that can settle or fail as one
XRP Ledger's Batch amendment went live on mainnet with 30 of 35 validators in favour, letting one operation bundle two to eight transactions. In its all-or-nothing mode one failed leg stops the rest, so OTC and delivery-versus-payment trades can settle on the ledger itself.
The Investor · Invest desk

What happened
- Batch makes users pick one of four execution modes per bundle (All or Nothing, Only One, Until Failure or Independent) and rejects nested batches and duplicate inner transactions.
- Developers fixed 11 software issues in Batch before the latest validator approval round, crypto.news reported on Sep. 15.
- The XRPL Foundation expects fixBatchV1_2, a security amendment from a Sep. 25 emergency release, to activate on Oct. 9 if validator support holds.
Why it matters
- exposure Back offices that confirm settlement from the outer Batch result alone can book trades that never cleared, since a successful outer result does not guarantee the inner transactions succeeded.
- cost Every failed all-or-nothing attempt still pays the Batch fee, so a desk retrying a broken trade pays for each try with nothing settled.
- decision Institutions planning delivery-versus-payment on Batch have to choose between routing value through it immediately and waiting until the security amendment is in force.
For a settlement desk, two rules in the specification matter more than the vote count. Under All or Nothing, the group completes only if every included action succeeds, and one failed transfer stops the rest [5]. In a multi-account batch, each participating account must approve the whole collection [6]. The signing rules tie that approval to the bundled actions, so one party cannot treat the other's transfer as a separately authorised payment [6]. Put a seller's token leg and a buyer's payment leg in one batch under that mode, and neither side has to send first and trust the other to follow [5][6].
Mode choice is the term a desk has to get right. Only One lets a single action succeed, Independent tries each action separately, and Until Failure runs actions in order and keeps the earlier successes once one fails [17]. On a two-leg trade, Until Failure can deliver the asset and leave the payment unsent [17]. Of the four modes, only All or Nothing guarantees that both legs clear or neither does [4][5].
Validator Vet's list of uses goes beyond OTC and delivery-versus-payment trades to NFT-for-NFT exchanges and transactions whose execution depends on another action [7]. "Its a massively important functionality for the XRP Ledger to allow crucial use cases for institutions and also retail builders," Vet said [8]. He called the feature a "big unlock" [9]. RippleX's own examples were a token swap between two users and a customer payment paired with a platform fee, and it did not name the companies behind the projects [21].
A vote of 30 for and five against, per XRPScan figures cited by crypto.news [2], works out to 85.7% in favour and 14.3% opposed [18][19]. XRPScan shows BatchV1_1 active on mainnet after the network's two-week approval period [1]. Under XRPL's amendment process, a proposal has to hold the required supermajority for two consecutive weeks before its rules take effect [15]. The report does not say why the five validators voted no [2].
The record fits more than one outcome. If the security amendment activates on schedule [12] and RippleX's contracted projects go live [20], Batch becomes a settlement tool institutions use for size. If the fix slips, careful desks wait. Usage could also arrive first from retail builders and NFT swaps, the other half of Vet's list [7]. In my view institutional size waits at least for the fix, because the only evidence of institutional demand so far is RippleX's account of projects it has not named [21]. The counter-case is that this demand already exists off-ledger and was waiting for an atomic settlement tool, and RippleX's statement that projects are under contract supports it [20]. I would be wrong if those projects settle trades under their own names soon after the fix is in force.
What to watch
- Whether fixBatchV1_2 activates as scheduled or loses the sustained validator support its activation depends on.
- The validator vote on XRPL's separate lending revision, which adds closed-ended vaults and cash-basis accounting.
- Whether any of the five validators that opposed BatchV1_1 explain their votes.
Clarity's read
What the record supports and how the coverage leans. The claims behind it follow.
Reality
- Evidence60
- Adoption20
- Hype gap+30
- Incentives60
- Confidence55
Claim ledger
Ranked by verification strength, evidence, and original report placement.
- [1]
XRPScan's dashboard shows BatchV1_1 as active on the XRP Ledger mainnet, following the network's two-week validator approval period.
- [2]
30 validators backed BatchV1_1 while five opposed it, according to XRPScan figures.
- [3]
A Batch contains an outer transaction and a list of two to eight inner transactions; the chosen execution mode determines whether the actions depend on each other.
- [4]
Batch offers four execution modes: All or Nothing, Only One, Until Failure and Independent. Users must select one mode per Batch; nesting a Batch inside another Batch is prohibited and duplicate inner transactions are rejected.
ReportedSupportedSource: crypto.news, citing the Batch specification and XRPL transaction referenceView cited source - [5]
Under All or Nothing, the group completes only if every included action succeeds; a failed transfer prevents the rest of the group from completing independently.
- [6]
In a multi-account Batch, participating accounts must approve the transaction collection, and the signing rules bind their approval to the bundled actions, preventing one participant from treating another party's transfer as a separately authorized payment.
- [7]
XRPL validator Vet pointed to over-the-counter trades, delivery-versus-payment settlement, NFT-for-NFT exchanges and transactions whose execution depends on another action as uses for Batch.
- [8]
"Its a massively important functionality for the XRP Ledger to allow crucial use cases for institutions and also retail builders,"
- [9]
Vet described the feature as a "big unlock."
- [10]
Developers fixed 11 software issues before the latest Batch approval process.
- [11]
A Sep. 25 emergency software release introduced fixBatchV1_2 to address security-sensitive issues.
- [12]
The XRPL Foundation's version 3.4.1 notice urged operators to upgrade promptly and identified Oct. 9 as the expected activation date for the fixBatchV1_2 security amendment, conditional on sustained validator support.
- [13]
XRPL's tutorial warns that a successful outer Batch result does not guarantee that its inner transactions succeeded, and instructs developers to inspect individual transaction results and verify account balances.
- [14]
In the tutorial's all-or-nothing example, a failed inner payment causes all included payments to fail, while the Batch transaction fee is still deducted.
- [15]
Under XRPL's amendment process, proposals must sustain the required validator supermajority for two consecutive weeks before their rules take effect.
- [16]
XRPL's separate lending revision introduces closed-ended vaults and cash-basis accounting, subject to validator approval.
- [17]
Only One permits a single successful action; Until Failure processes actions until an action fails, retaining earlier successful steps; Independent attempts the included actions separately without requiring every action to succeed.
- [18]
Validators in favour of BatchV1_1 were about 85.7% of the 35 counted.
- [19]
Validators opposed to BatchV1_1 were about 14.3% of the 35 counted.
- [20]
RippleX said commercial projects using Batch were already under contract or development.
- [21]
RippleX's examples included a token swap between two users and a customer payment paired with a platform fee; its account described projects in development without naming the companies involved.
Sources
1 independent publisher whose own reporting we read for this story.
- crypto.newsXRP Ledger Batch goes live, enabling bundled transactions
1 article · October 9, 2026
Topics and entities
Follow any of these and your For You feed starts watching them — no settings page required.
Topics
- DeFi Lending ProtocolsFollow
- Blockchain Protocol GovernanceFollow
- Atomic settlementFollow
Entities
- XRP LedgerFollow
- Batch amendment (BatchV1_1)Follow
- XRPScanFollow
- RippleXFollow
- XRPL FoundationFollow
- VetFollow
- crypto.newsFollow