RippleX Declares XRP Ledger Batch Amendment Ready for Activation
Ripple’s developer division, RippleX, has announced that the XRP Ledger’s Batch amendment is ready for activation. A technical review published Monday details how the feature was rebuilt following the discovery of a critical security flaw in the original version. The corrected Batch V1.1 is included in the xrpld v3.3.0 release and enables multiple transactions from different accounts to settle atomically within a single ledger close. RippleX describes this capability as foundational for atomic swaps and multi-party coordination on the network.
Why the Original Batch Was Pulled
The original Batch amendment, known as XLS-56, was withdrawn after security researchers and Cantina AI identified a critical flaw in its signature-validation routine on February 19, 2026. The checkBatchSign function, responsible for confirming that each inner-transaction account authorized a batch, contained an early-return bug. When the function encountered a signer whose account did not yet exist on the ledger, it incorrectly returned success and skipped validation of all remaining signers. RippleX stated that this flaw could have allowed an attacker to execute transactions on behalf of victim accounts without access to their private keys. Because the amendment was still in its voting phase and had not yet activated on the mainnet, no funds were at risk.
How Batch V1.1 Was Hardened
Batch V1.1 replaces the original amendment and eliminates the early-return bug. According to RippleX, the root-cause fix was merged via pull request #6446 and reviewed by four senior engineers. Additional assurance came from a Sherlock Batch Attackathon contest, a Halborn re-assessment, and a Common Prefix audit. An AI-assisted static analysis pipeline incorporating a Cantina scan has been integrated into the release process, complemented by regression testing on devnet and testnet. The amendment is included in the xrpld v3.3.0 release, which bundles it with five other proposals.
Atomic Transactions and What Comes Next
Batch is designed to allow multiple XRPL transactions to execute as a single all-or-nothing unit, meaning a batch either fully succeeds or fully reverts — a design intended for atomic swaps and coordinated settlements. As with every XRP Ledger amendment, Batch V1.1 must achieve an 80% validator majority for 14 consecutive days before activation, according to the network’s amendment tracker. Consequently, the amendment remains in its voting phase. The ledger has attracted broader attention this month: the Bank for International Settlements recently tested the network to anchor official statistics on-chain, while XRP has expanded further into traditional finance amid growing ETF demand and derivatives access.
