The XRP Ledger's Batch V1.1 amendment has moved within a single validator vote of beginning its two-week activation countdown after RippleX said developers had resolved 11 additional software issues uncovered during security reviews.
XRPScan data showed that 27 of the 35 trusted validators on the default Unique Node List were backing Batch V1.1 on Tuesday, equivalent to roughly 77%. Under XRPL governance rules, a proposal must hold at least 80% support, or 28 supporting validators in the current tracked set, for 14 consecutive days before it can activate. The latest tally puts Batch V1.1 one vote short of that threshold. Support has climbed quickly from 24 votes on Sept. 8, when it stood at 68.57%.
Batch V1.1 would allow applications to group up to eight linked transactions into a single operation, with an all-or-nothing mode that ensures every required instruction succeeds together or the full batch fails. RippleX said the feature could make multi-step payment and trading flows less fragile: for example, a marketplace sale could link buyer payment, seller asset transfer and platform fee as dependent transactions, avoiding a partially completed trade. RippleX also said commercial projects using Batch are already under contract or development, though it has not publicly identified the companies.
The current version replaces the original Batch amendment after researchers found a serious authorization flaw in February before it reached mainnet. That flaw could have allowed an attacker to place transactions from another user's account inside a batch without permission. No user funds were put at risk because the affected amendment never activated. RippleX software engineer Mayukha Vadari said the rebuild included a root-cause fix, reviews by four senior engineers, a Sherlock security contest, and audits from Halborn and Common Prefix.
During examination of the replacement implementation, another 11 issues were found involving signatures, authorization checks and potential server crashes. Common Prefix classified one vulnerability as critical: it could have allowed an attacker to reuse a permission a user had signed and carry out more transactions than intended. RippleX said the fixes were incorporated into Batch V1.1, which shipped in xrpld 3.3.0 released on Aug. 6.
Validators can still change their positions after the two-week countdown begins, and support falling below 80% would interrupt activation. That process was demonstrated in July when the fixCleanup3_2_0 amendment secured 85.71% support, retained enough backing, and activated on July 29. Batch remains separate from other proposed XRPL features such as Confidential MPT, Sponsor, Dynamic MPT and Permission Delegation, each of which requires independent validator approval.
