Ripple’s developer arm RippleX has declared the $XRP Ledger’s Batch amendment ready for activation, publishing a technical review on Monday that explains how the feature was rebuilt after a critical security flaw was found in the original version. The corrected Batch V1.1 ships in xrpld v3.3.0 and will let multiple transactions from different accounts settle atomically in a single ledger close — a capability RippleX frames as foundational for atomic swaps and multi-party coordination on the network.
Why the Original Batch Was Pulled
The original Batch amendment, XLS-56, was set aside after security researchers and Cantina AI flagged a critical flaw in its signature-validation routine on Feb. 19, 2026. The checkBatchSign function, which confirms each inner-transaction account has authorized a batch, contained an early-return bug: when it hit a signer whose account did not yet exist on the ledger, it returned success and skipped validation of every remaining signer. RippleX said the flaw could have let an attacker execute transactions on behalf of victim accounts without their private keys. Because the amendment was still in its voting phase and had not activated on mainnet, no funds were at risk.
blockchainreporter.net