The XRP Ledger's Batch V1.1 amendment is one validator vote short of reaching the 80% threshold needed to trigger its 14-day activation countdown. The revised code underwent extensive security review after a critical flaw was discovered in the original Batch V1.0 proposal.
The original bug involved an early return in the checkBatchSign function that could have allowed transactions to be executed without proper signature validation from all required parties. The flaw was identified in February while the amendment remained in pre-mainnet testing, meaning no funds were at risk.
Batch V1.1 shipped with xrpld 3.3.0 and is now undergoing validator voting. The revised code was reviewed by four senior engineers, subjected to an adversarial testing event called the Sherlock Batch Attackathon, evaluated by security firms Halborn and Common Prefix, scanned by AI analysis tools through Cantina, and tested on Devnet and testnet environments.
According to the most recent snapshot, 27 trusted validators have voted in favor of the amendment while eight have voted against it, representing approximately 77% support. Just one additional affirmative vote would reach the required 80% threshold.
Purpose and Functionality
Batch, formally known as XLS-56, enables multiple transactions from different accounts to execute atomically in a single ledger close. If any transaction in the all-or-nothing batch fails, the entire operation reverts. The feature does not require smart contracts.
The amendment is designed to facilitate atomic swaps, coordinated settlements, and other multi-party transactions requiring synchronized execution. It could also reduce the procedural steps needed for NFT minting and transfers.
Context
This security rebuild reflects heightened scrutiny on the XRP Ledger following the recent withdrawal of the Permission Delegation amendment due to a high-severity bug discovered before mainnet deployment. An XRPL amendment testing dashboard launched this month now provides public visibility into which transaction types, fields, and result codes have been exercised during Devnet testing.
