XRP Ledger Upgrade Awaits Final Support

Batch V1.1 is nearing the approval required to go live on the XRP Ledger, with 27 of 35 trusted validators supporting the amendment in the latest Tuesday snapshot. That puts approval at approximately 77%, just below the network’s 80% requirement.

The amendment would introduce a way to combine up to eight related transactions into a single operation. Once activated, the transactions would be treated atomically, meaning they would all be executed together or all fail together.

This could make multi-step transfers considerably safer. For example, two users exchanging tokens could place both sides of the transaction into one batch, preventing one transfer from completing if the other does not.

The XRP Ledger requires amendments to maintain at least 80% validator support for 14 consecutive days. Validators remain free to change their votes during that period. If Batch V1.1 receives one more supporting vote, the activation countdown would begin.

11 Problems Addressed Before Launch

The vote comes after developers completed another round of security and reliability work on the feature. RippleX, Ripple’s development arm, published a technical review Monday detailing 11 issues found during testing.

Batch V1.1 was included in the xrpld 3.3.0 release and is currently being evaluated through the XRP Ledger amendment process.

The issues involved areas such as signature processing, authorization checks and defects that could potentially crash servers. Common Prefix rated one vulnerability as critical because it could have allowed an attacker to reuse a user’s signed permission and execute more transactions than the user originally approved.

RippleX said the updated code was examined by four senior engineers and underwent audits from Halborn and Common Prefix. Developers also used automated testing and a public security contest to search for additional vulnerabilities.

Potential Uses Across XRPL

RippleX has said commercial projects are already under contract or being developed around Batch V1.1, although the companies have not been identified publicly as of Tuesday.

The functionality could be particularly useful for wallets and marketplaces that need to execute several connected payments. A platform could, for example, combine a customer’s payment and its own fee into one operation, ensuring that both are processed together.

The revised implementation follows a significant flaw discovered in the original Batch proposal earlier this year. Researchers found that, under certain conditions, an attacker could potentially insert transactions from another account without the owner’s authorization.

Because of that vulnerability, the original design never reached the XRP Ledger mainnet. Developers replaced it with a revised implementation in the xrpld 3.3.0 release on Aug. 6 and subjected the new version to further internal reviews, external audits and public security testing.

With validator support currently at 77%, Batch V1.1 is one vote away from reaching the level needed to start its 14-day path toward activation.