XRPL Poised for Major Payments Upgrade as Final Vote Approaches

XRPL Needs One More Validator Vote

The XRP Ledger is approaching the launch of Batch V1.1, with the amendment receiving support from 27 of its 35 trusted validators in a Tuesday snapshot. The backing represents about 77%, leaving the proposal just short of the 80% approval level required for activation.

Batch V1.1 would allow as many as eight related transactions to be grouped into a single operation. By treating the bundled transactions as one atomic unit, the system would ensure that either every transaction succeeds or the entire batch fails.

That design could reduce risks in multi-step transfers. In a token swap, for example, both parties could have their transfers included in the same batch, preventing one side from completing if the other transaction encounters an error.

Once the amendment reaches 80% support, the XRP Ledger would begin a 14-day activation period. Approval must stay above the threshold for the entire period, and validators can alter their votes before the countdown ends.

Revised Version Clears Security Testing

The latest vote follows extensive work to address vulnerabilities discovered in the Batch V1.1 implementation. RippleX, Ripple’s development arm, said Monday that 11 issues had been identified and fixed during a technical review.

The amendment was shipped as part of xrpld 3.3.0 and is now being considered through the XRP Ledger’s governance process.

The problems uncovered during testing included issues with signatures and authorization checks, along with bugs that could potentially bring down servers. Common Prefix identified one critical vulnerability that could have allowed an attacker to reuse a user’s signed permission and authorize more transactions than intended.

RippleX said four senior engineers participated in the review. The updated implementation also underwent audits by Halborn and Common Prefix, automated testing and a public security contest designed to uncover additional weaknesses.

Payment Platforms Could Benefit

RippleX has said commercial projects are already under contract or being developed with Batch functionality in mind, although the companies involved had not been named as of Tuesday.

The feature could have several practical applications for wallets and marketplaces. A platform could bundle a customer’s payment and its own fee into one operation, making sure both transactions are completed together.

The latest implementation was developed after researchers uncovered a serious problem in the original Batch proposal earlier this year. Under certain circumstances, that flaw could have allowed an attacker to include transactions from another user’s account without authorization.

The vulnerable version never reached the XRP Ledger mainnet. Developers replaced it in the xrpld 3.3.0 release on Aug. 6 and subjected the revised implementation to further internal reviews, third-party audits and public bug hunting.

Batch V1.1 now sits at 77% validator support, meaning one additional vote could push the amendment over the approval threshold and start its two-week activation process.