XRPL Nears Approval Threshold
The XRP Ledger is approaching activation of Batch V1.1, an amendment that would allow up to eight connected transactions to be processed as a single operation. In a Tuesday snapshot, 27 of the network’s 35 trusted validators had voted in favor, putting support at roughly 77%.
The upgrade needs 80% validator approval before it can move forward. If another validator backs the amendment, the required threshold would be reached and a 14-day activation countdown would begin.
Batch V1.1 is designed to make complex transfers more reliable by grouping multiple transactions into one atomic operation. All transactions in a batch must either succeed or fail together, preventing situations where only part of a transaction sequence is completed.
For instance, users conducting a token swap could link both sides of the transfer so that neither payment settles independently if the other one fails.
Validator support must remain at or above 80% for the full 14-day period. Validators can change their positions during the countdown, meaning the amendment must maintain sufficient backing until activation.
Developers Addressed 11 Issues
The proposed activation comes after developers completed fixes for 11 issues identified during additional security testing of Batch V1.1.
Ripple’s developer division, RippleX, outlined the work in a technical review published Monday. The amendment was included in the xrpld 3.3.0 release and is now undergoing the XRP Ledger’s validator voting process.
The identified problems covered areas including signatures, authorization controls and vulnerabilities capable of causing server crashes. Common Prefix classified one of the issues as critical, warning that an attacker could potentially reuse a user’s signed permission to carry out more transactions than originally authorized.
RippleX said the revised implementation underwent reviews by four senior engineers, audits from Halborn and Common Prefix, a public security contest and automated testing.
Batch Could Support Payments and Fees
RippleX has said commercial projects are already under contract or being developed to use the Batch functionality, although the companies involved had not been disclosed as of Tuesday.
The feature could also be useful for wallets and marketplaces that need to execute several related payments simultaneously. A marketplace, for example, could combine a customer’s payment with a platform fee in the same batch, ensuring both actions are completed together.
The current version follows a significant security issue discovered in the original Batch proposal earlier this year. Researchers found that the earlier design could, under certain circumstances, allow an attacker to insert transactions from another account without the account holder’s authorization.
That original implementation never reached the XRP Ledger mainnet. Developers replaced it in the 3.3.0 software release on Aug. 6 and subjected the updated version to further internal reviews, external audits and public bug hunting.
With support currently just below the required 80%, the next validator vote could determine whether Batch V1.1 officially enters its activation countdown.
