Ripple said that as XRP Ledger prepares to activate a payment function that has been redesigned and undergone a comprehensive security review, multiple asset management firms and other commercial projects have already begun preparing for related applications.
The function, called Batch V1.1, can combine up to 8 related transactions into a single operation. Its “all-or-nothing” mechanism means that the entire operation will only be completed when all transactions in the transaction group succeed; if any transaction fails, the entire transaction group will be canceled, thereby avoiding a situation in which one participant completes settlement while another does not.
Ayo Akinyele, head of engineering at RippleX, said in an interview with CoinDesk that as the function officially goes live, Ripple will disclose more relevant information, including cooperation with major asset management firms.
Akinyele explained that Batch can integrate multiple transactions into the same operation, allowing these transactions to be executed or canceled simultaneously. For application scenarios such as Delivery-versus-payment, this mechanism is particularly important because the assets and payments in a transaction need to be transferred simultaneously in an atomic manner.
Delivery-versus-payment refers to linking the delivery of an asset with the corresponding payment, so that neither party needs to rely on the other party completing the operation in advance, but instead ensures that both transactions are executed simultaneously, or neither is executed when the conditions are not met.
In addition to asset transaction scenarios, Batch can also change how exchanges, wallets, and market service fees are handled. These platforms can directly attach service fees to customer transactions, allowing the payment amount and platform fee to be completed through a single operation without initiating an additional separate transfer.
Akinyele said that some projects have already begun development around potential applications of Batch, so once the function is officially activated, these projects will be closer to entering production environments.
He also pointed out that as the relevant plans are gradually finalized, Ripple will further announce specific partners and the official launch time.
30 Validators Support It, Activation Countdown Begins
The amendment has currently received support from 30 of the 35 validators on the XRP Ledger network, exceeding the 28 votes required to enter the activation countdown.
The activation countdown officially began at 14:06:41 UTC on September 15. Under the current arrangement, Batch V1.1 is expected to complete activation after the same time on September 29, provided that validator support remains at or above 80% throughout the entire 14-day window.
Because validators can still adjust their votes, the expected activation time of September 29 is not a final confirmed date.
The launch of this version is also the result of renewed efforts to advance the Batch function after a security issue previously emerged.
New Version Stems from Previous Security Vulnerability Fix
In February this year, researchers discovered a critical vulnerability in the Batch V1.0 signature verification process. Under certain conditions, the relevant code could stop before completing all signature verification, potentially allowing an attacker to add transactions from other accounts without authorization from the account owners.
However, because the amendment was still under validator review and had not yet been officially activated at the time, the vulnerable code never actually controlled the XRP Ledger ledger, and no funds were lost.
Before advancing the Batch function again, RippleX did not merely perform a single-point fix targeting the original vulnerability.
Akinyele said that the team used this opportunity to further review the entire implementation process and redesign parts of the signature and authorization models, while significantly expanding the scope of the security review.
The redesigned version has been released with xrpld 3.3.0, which went live on August 6. Akinyele said that the code validators are currently voting to activate is this redesigned implementation.
The security review covered multiple areas, including Ripple’s internal adversarial testing, artificial intelligence-assisted analysis, the Sherlock attack competition, and assessments by security companies Halborn and Common Prefix.
Akinyele said that before Batch V1.0 was officially activated, the team discovered a serious issue and therefore suspended the related advancement. Subsequently, RippleX redesigned and strengthened the implementation and expanded the scope of the security review. Only after completing this work did it resubmit Batch V1.1 to validators for a vote.
If Support Falls Below 80%, the Activation Process Will Restart
Currently, the activation countdown for Batch V1.1 will continue until September 29.
During this period, if validator support falls below 80%, the current countdown will stop. After the proposal regains the required majority support, the activation process will need to reopen a new 14-day window.
Therefore, whether Batch V1.1 can ultimately complete activation according to the current schedule depends not only on the number of validators currently supporting it, but also on whether the support rate can remain at the required level throughout the entire countdown period.