XRP Ledger's Batch V1.1 amendment has secured 27 of 35 validator votes, one short of the 80% threshold needed to begin its 14-day activation period. RippleX fixed 11 additional software issues, including a critical permission-reuse flaw, before the current vote. The upgrade would let users combine up to eight transactions into one operation.
The XRP Ledger's Batch V1.1 amendment sits one validator vote away from starting its two-week activation window, after developers fixed 11 more software issues uncovered during security reviews.
Validator support closes in on 80%
Support for Batch V1.1 stood at 27 of the 35 trusted validators on Tuesday, equal to roughly 77% — just below the 80% level XRP Ledger rules require to enter the network's activation period. That backing has grown quickly: on Sept. 8, the amendment had 24 votes, equal to 68.57%, crypto.news previously reported, before three more validators added support.
Under XRP Ledger governance rules, an amendment must hold at least 80% validator support for 14 consecutive days before it can activate. Another supporting vote would push Batch V1.1 past the threshold and start that countdown, though validators can still change their positions, and support falling below 80% during the window would interrupt the process.
What Batch V1.1 changes
Batch V1.1 would let users combine as many as eight transactions into a single operation, with rules that can require linked transactions to succeed together. In a token swap between two users, failure on one side would stop the other transaction from completing independently. Wallets and marketplaces could use the same structure to process a customer payment and a platform fee together, though RippleX has not identified which commercial projects are already under contract or development to use the feature.
Developers rebuilt Batch after a mainnet-blocking flaw
The current version replaces an earlier Batch design that researchers found carried a vulnerability that could have let an attacker place transactions from another user's account inside a batch without authorization, though no funds were at risk because that amendment never reached mainnet. RippleX rebuilt the feature, folding Batch V1.1 into the xrpld 3.3.0 release on Aug. 6.
Common Prefix classified one of the 11 additional issues found during review as critical — a flaw that could have let an attacker reuse a user's signed permission to carry out more transactions than intended. Four senior engineers, a public Sherlock security contest, and outside audits from Halborn and Common Prefix reviewed the implementation before developers addressed every reported problem.
Each of xrpld 3.3.0's five proposed amendments requires its own validator vote — Batch has climbed to 27 votes while Permission Delegation held support from seven of the 35 trusted validators when Ripple backed it in August, leaving every feature on its own path toward activation.
Source: crypto.news
Trading involves risk.
Risk Disclaimer
