Validators Vote on Batch V1.1 After Security Overhaul

This article is journalistic reporting and not financial advice. Crypto investments are risky and prices can fluctuate significantly. Always do your own research before making an investment decision.

According to Ripple, asset managers and other commercial projects are preparing to use Batch V1.1, a feature that allows up to eight XRP Ledger transactions to be bundled together so they either all succeed or all fail. Validators are currently voting on activation, which is expected shortly after September 29 if support remains above 80 percent. The question is whether that threshold will hold until that date.

Batch V1.1 Must Handle Payments and Assets Together

The feature, called Batch V1.1, combines up to eight transactions into a single operation on the XRP Ledger. The all-or-nothing principle ensures that the entire group of transactions either succeeds or the whole group is canceled. This prevents one side of a deal from being completed while the other side fails.

Ripple reports that asset managers and other commercial parties are already preparing to use the feature as soon as it goes live. Batch V1.1 is expected to be activated shortly after September 29, provided validator support remains at or above 80 percent throughout the full fourteen-day period.

Why Atomic Transactions Are Relevant for Payment Infrastructure

The main application Ripple mentions is delivery-versus-payment: linking the transfer of an asset to its payment. Instead of relying on one party to send first, the ledger completes both parts together, or neither.

Additionally, Batch could enable exchanges, wallets, and marketplaces to add service fees directly to a customer transaction, rather than through separate transfers. The change currently has support from 30 of the 35 validators following the XRP Ledger, well above the 28 votes required to enter the activation countdown phase. That countdown began on September 15 at 14:06:41 UTC, but remains conditional as validators can change their votes.

For those wanting to understand the broader context: this ties into the earlier vote on a major XRP Ledger upgrade, and the role of institutional parties is revisited in the piece on the adoption of the XRP Ledger by asset managers.

What RippleX Says About the Rebuild After the Critical Bug

Ayo Akinyele, head of engineering at RippleX, explains according to the primary source that the original version, Batch V1.0, was withdrawn after researchers discovered a critical bug in the signature validation process in February. Under certain conditions, the code could prematurely stop checking signatures, allowing an attacker to take transactions from another account without the owner's permission.

Importantly, the vulnerable code never governed the active ledger: the amendment was still under review by validators and never activated, so no funds were exposed. RippleX seized the incident to redesign parts of the signing and authorization model and significantly expand the security assessment, including internal adversarial testing, AI-assisted analysis, a Sherlock attack competition, and assessments by the security firms Halborn and Common Prefix. The replacement implementation was delivered in xrpld version 3.3.0, released on August 6.

The Remaining Conditions for Activation

Batch V1.1 remains in the countdown phase until September 29. If validator support drops below 80 percent before that date, the clock stops and a new fourteen-day window must begin once the proposal regains the required majority.

Ripple reports that some projects are already being developed with Batch in mind, without naming specific partners. More details about specific collaborations and launch timing will only be shared once those plans are finalized, according to RippleX. Those wanting to follow Ripple's broader infrastructure ambitions can also look at Ripple's cross-border payment solutions, which also lean on the underlying XRP Ledger technology.