XRPL Batch V1.1 amendment nears activation as validator support reaches 27 of 35

The XRP Ledger (XRPL) is close to activating its Batch V1.1 amendment. The proposal has secured 27 out of 35 trusted validator votes, just one vote short of the 80 % threshold required to begin the mandatory 14‑day activation window.

Recent fixes and security review

Developers addressed 11 additional issues identified during security reviews. The problems involved transaction signatures, authorization checks and conditions that could cause server crashes. Audits were performed by Halborn and Common Prefix, and four senior engineers conducted a final review.

What Batch V1.1 enables

Batch V1.1 allows up to eight transactions to be combined into a single operation. Linked payments can be set to settle together, meaning that if one transaction in the batch fails, the others are aborted. This atomic settlement model can be used for token swaps, combined customer payments and platform fees, and other coordinated actions.

Governance and activation timeline

XRPL governance requires an amendment to maintain at least 80 % validator support for 14 consecutive days before activation. With 27 votes (≈77 %), the amendment is one vote away from entering that period. Validators may still change their positions, and a drop below the threshold would pause the process.

Background and previous attempts

The current Batch V1.1 replaces an earlier version that was withdrawn after researchers discovered a serious authorization flaw. The flaw could have let an attacker insert unauthorized transactions into a batch. No funds were at risk because the flawed amendment never activated. The revised implementation was included in xrpld 3.3.0, released on August 6, alongside other proposed features such as Confidential MPT, Sponsor, Dynamic MPT and Permission Delegation.

Commercial interest

RippleX indicated that commercial projects are already under contract or in development to use Batch, though specific companies were not disclosed.