Key Highlights
- The XRP Ledger received 29 affirmative validator votes for the Batch V1.1 amendment on September 15.
- Activation is scheduled for September 29 under the network’s standard amendment process.
- XLS-56 allows up to eight transactions from different accounts to execute atomically within a single ledger close.
The XRP Ledger is set to activate the Batch V1.1 amendment after receiving 29 yes votes on September 15. Activation is scheduled for September 29.
According to Hussein Zangana (known online as Vet), the Director of Community at the XRP Ledger Foundation, the amendment enables several transaction patterns. These include atomic swaps for delivery-versus-payment structures in repo markets, in which tokenized securities are exchanged at the same time as a corresponding payment.
Cross-asset swaps can combine NFTs, multi-purpose tokens and trustline tokens in a single transaction. Platforms can collect service fees within the same transaction as the primary activity. Multiple decentralized exchange swaps with different slippage parameters can be bundled so that the first successful swap completes. NFT-for-NFT trades are also supported.
The amendment, identified as XLS-56, permits multiple transactions from different accounts to execute atomically within a single ledger close. In all-or-nothing mode, failure of any inner transaction causes the entire batch to revert.
The feature supports multi-party coordination, including atomic swaps and coordinated settlements that do not require trust assumptions between parties. Up to eight XRP Ledger transactions can be bundled in one batch and linked with dependencies.
Original batch amendment and identified flaw
An earlier version of the Batch amendment, referred to as v1.0, entered the voting phase but was not activated on the mainnet. On February 19, 2026, security researchers and Cantina AI identified a critical logic flaw in the signature-validation routine.
The function checkBatchSign, responsible for confirming that each inner-transaction account had authorized the batch, contained an early-return error.
When the routine encountered a signer whose account did not yet exist on the ledger, it returned success and skipped validation of remaining signers. The flaw would have allowed an attacker to execute arbitrary transactions on behalf of other accounts without access to their private keys.
No funds were at risk because the amendment had not been activated. Unique Node List validators were advised to vote no. Ripple’s engineering team reproduced the issue with an independent unit test. An emergency software release was issued that marked both the original Batch amendment and the related fixBatchInnerSigs amendment as unsupported.
Batch V1.1 is a replacement amendment that incorporates a corrected implementation. The updated code is included in xrpld version 3.3.0. Development focused on resolving the signature-validation bug identified in February and on additional hardening of the feature.
Related amendment activity
Separately, on August 28, Ripple has recommended that the XRP Ledger community withdraw the XChainBridge amendment, known as XLS-38, along with the related fixXChainRewardRounding amendment.
XLS-38 was proposed to enable native cross-chain bridges on the XRP Ledger through a decentralized network of witness servers that observe and attest to transactions across chains.
The design was intended to support custom sidechains, including private chains, permissioned networks and experimental environments, as well as a bridge between the XRP Ledger EVM sidechain and the mainnet that would use XRP as the native gas token.
The Batch V1.1 activation process follows the standard XRP Ledger amendment procedure, in which validators vote and a threshold of support is required before the feature becomes active on the network. The September 29 activation date reflects the outcome of the current voting round that reached 29 affirmative votes.
Also Read: Circle, Ripple Invest in Velocity as Funding Hits $48M
