The XRP Ledger’s Batch V1.1 amendment is one validator vote short of the 80% threshold needed to begin its 14-day activation countdown, following a security rebuild after a critical flaw was found in the original version. The revised code has passed senior engineering review, adversarial testing, and two external security audits. The update replaces Batch V1.0, whose signature-validation bug was discovered in February, potentially allowing unauthorized transactions. The new version also fixes several other issues, including MPT validation bypasses and node crashes. Validator support currently sits at 77%, with one more affirmative vote required to move forward.
The XRP Ledger’s Batch V1.1 amendment is one validator vote short of the 80% threshold needed to begin its 14-day activation countdown. RippleX developer Mayukha Vadari stated the amendment shipped with xrpld 3.3.0 and is currently up for voting.
The original Batch V1.0 contained a signature-validation bug found in February while the amendment was still pre-mainnet, meaning no funds were at risk. The flaw involved an early return in the checkBatchSign function that could allow transaction validation to succeed without checking remaining signers, potentially enabling unauthorized transactions.
Batch V1.1 removed that flaw and addressed other issues found during the rebuild. The process included review by four senior engineers, a Sherlock Batch Attackathon, a Halborn reassessment, a Common Prefix audit, and Cantina AI scanning, along with Devnet and testnet regression testing.
Vadari also confirmed fixes for additional bugs found through newer AI red-teaming work, including MPT validation bypasses, node crashes, and signature verification issues. Validator sentiment is close to the required threshold, with one account, FrancisBovineSwift, describing the voting as “nearly there.” Recent snapshots show 27 trusted validators voting for the amendment and eight against, putting support at roughly 77%.
Batch, also known as XLS-56, allows multiple transactions from different accounts to execute atomically in a single ledger close without smart contracts. The feature is intended for atomic swaps, coordinated settlements, and NFT minting and transfers.
The security rebuild follows other recent XRPL scrutiny, after the network pulled its Permission Delegation amendment when a high-severity bug was found. An XRPL testing dashboard launched this month has also made amendment testing more visible by tracking exercised transaction types and result codes on Devnet.
