Assets and Payments in a Single Group on XRP Ledger: If One Fails, the Other is Canceled
The Batch V1.1 update on the XRP Ledger has entered its activation countdown to combine asset and payment transfers into the same group.
According to a statement made to CoinDesk by Ayo Akinyele, Head of Engineering at RippleX, asset managers and certain commercial projects are preparing to use the XRP Ledger’s Batch V1.1 feature. The update could go live around September 29, provided the necessary validator support is maintained.
Batch V1.1 can combine up to eight transactions in a single transaction group. Operating on an “all or nothing” model, the entire group is canceled if all transactions within the group are not successful. This aims to prevent issues such as one party sending an asset while the other fails to complete the payment.
The Batch feature can also be used for exchanges, wallets, and marketplaces. Platforms will be able to process transaction fees within the same group as the customer transaction. RippleX stated that some projects have already been developed with this feature in mind and that activation could bring these efforts closer to the production stage.
30 out of 35 validators are supporting the update. While the threshold required to start the activation process is 28 votes, support must remain at at least 80 percent throughout the countdown. The 14-day process began on September 15, and if this condition is maintained, Batch V1.1 is expected to activate on September 29.
However, if validator support falls below 80 percent, the countdown will stop, and a new 14-day process will begin once the necessary majority is re-established.
Batch V1.1 Redesigned Following Security Vulnerability
The current version of the update was prepared following the previously withdrawn Batch V1.0. A critical signature verification vulnerability discovered in V1.0 in February could have allowed attackers, under certain conditions, to unauthorizedly add transactions belonging to another account to a group.
Since the vulnerability was found before the feature was activated on the live ledger, it was never exploited on the XRP Ledger and funds were never at risk. Following this, RippleX did not just fix the bug; they redesigned the signature and authorization model.
The new version was included in xrpld 3.3.0, released on August 6. During the review process, internal attack testing, AI-powered analysis, the Sherlock security competition, and evaluations by Halborn and Common Prefix were utilized. Akinyele said that following this process, the redesigned feature was presented for validator voting.