XRP Ledger Batch V1.1 Nears Activation as Asset Managers Prepare - Blockonomi

by · Blockonomi

TLDR:

Table of Contents

Toggle

  • XRP Ledger Batch V1.1 has support from 30 of 35 tracked validators, but activation depends on maintaining at least 80% support through September 29.
  • The feature groups up to eight transactions, allowing asset transfers, payments and platform fees to settle together or fail as one operation.
  • Ripple says asset managers and commercial projects are building around delivery-versus-payment, while partner details have not been disclosed.
  • Developers withdrew Batch V1.0 after a signature flaw, then released V1.1 with redesigned authorization and reviews by Halborn and Common Prefix.

Ripple says asset managers are preparing for XRP Ledger Batch V1.1, a payments upgrade for linked transactions. It can group eight XRP Ledger transactions in one operation. The all-or-nothing setting completes every transaction or cancels the group.

The design supports delivery-versus-payment, linking asset transfers with payment. RippleX engineering head Ayo Akinyele said commercial projects already account for XRP Ledger Batch V1.1.

The XRPL Dashboard lists support from 30 of 35 tracked validators. The amendment needs 28 votes to start its countdown. That process began September 15 at 14:06:41 UTC. Activation could follow September 29 if support stays above 80% for fourteen days.

XRP Ledger Batch V1.1 Moves Toward Conditional Activation

The vote gives XRP Ledger Batch V1.1 a conditional path toward activation. Validators can change their positions during the countdown. If support falls below 80%, the clock stops. A new fourteen-day period must begin after the amendment regains the threshold.

XRP Ledger Batch V1.1 groups transactions under a parent operation. Users can submit as many as eight linked transactions, with each transaction retaining its details. The all-or-nothing setting prevents partial settlement when one transaction fails.

Unlike a multi-step workflow, the grouped operation gives counterparties a settlement condition. If one leg fails, the ledger does not complete the other leg. That design may simplify settlement for funds, trading venues and token issuers using the XRP Ledger. It also gives developers a way to combine transfers without relying on callbacks or manual reconciliation. The feature does not guarantee adoption, since projects still need testing, compliance and preparation.

That function matters for asset managers building digital markets. A fund can transfer a tokenized asset while receiving payment within the same ledger operation. The use case gives XRP Ledger Batch V1.1 a direct role in atomic settlement.

Akinyele identified delivery-versus-payment as a key use case. The method links asset delivery and payment, rather than asking one party to send first. This can reduce exposure to incomplete settlement during a trade.

Ripple also identified fees as another application. Exchanges, wallets and marketplaces can attach service charges to a customer transaction. The payment and fee can then process as one grouped operation.

RippleX has not named the commercial projects using the feature. Akinyele said more details will follow after partners formally finalize plans and launch timing. He added that activation would move development work closer to production.

Delivery Versus Payment Shapes the Upgrade Use Cases

The planned activation follows the withdrawal of Batch V1.0. Researchers found a critical signature-validation flaw in February. Under certain conditions, the code could stop checking signatures early. An attacker could then include transactions from another account without authorization.

Validators had not activated the original amendment when developers withdrew it. The vulnerable code therefore never controlled the live ledger. The flaw exposed no user funds directly.

RippleX used the incident to redesign parts of the signing and authorization model. The replacement shipped in xrpld version 3.3.0 on August 6. Ripple said the code now under consideration matches that release.

The review covered internal adversarial testing and AI-assisted analysis. It also included a Sherlock attack contest. Security firms Halborn and Common Prefix conducted assessments.

RippleX also used internal adversarial testing before seeking validator approval. The company said its wider review covered the work before V1.1 returned to the vote.

The expanded process supports the return of XRP Ledger Batch V1.1 to the validator process. Akinyele said the team raised the review standard, addressed the defect and submitted Batch V1.1 for another validator vote.

The amendment will continue through September 29 under the current schedule. Support must stay at or above 80% throughout the window. Any decline below that level would pause activation and require another countdown after support recovers.

Advertise Here