The XRP Ledger’s Batch V1.1 amendment is one validator vote away from reaching the 80% threshold required for activation, marking a significant step after a security rebuild addressed a critical flaw in the original version.
Security Rebuild Addresses Critical Flaw
The Batch V1.1 amendment, also known as XLS-56, is designed to enable multiple transactions from different accounts to execute atomically within a single ledger close. If any transaction in a batch fails, the entire operation reverts, ensuring an all-or-nothing outcome. This feature, which does not require smart contracts, is intended for use cases such as atomic swaps, coordinated settlements, and potentially streamlining NFT minting and transfers.
The original Batch V1.0 amendment contained a signature-validation bug that was discovered before its mainnet deployment. The flaw, identified in February, involved an early return in the checkBatchSign function. This could have allowed validation to return success without verifying all signers if a signer account did not yet exist on the ledger, potentially enabling unauthorized transactions on behalf of other accounts. Crucially, because the bug was found pre-mainnet, no funds were at risk.
Rigorous Testing and Review Process
In response to this critical flaw, a comprehensive security rebuild was undertaken for Batch V1.1. RippleX developer Mayukha Vadari reported that the amendment shipped with xrpld version 3.3.0 and is now up for validator voting. The rebuild process was extensive, incorporating a senior engineering review, adversarial testing, external security reviews, and AI-assisted analysis. This included review by four senior engineers, a Sherlock Batch Attackathon, a Halborn reassessment, a Common Prefix audit, Cantina AI scanning, and rigorous Devnet and testnet regression testing. The team also addressed additional bugs identified through newer AI red-teaming efforts, fixing issues related to MPT validation bypasses, node crashes, path size validation, signature verification, signer ordering, and transaction hashing.
Validator Sentiment and Next Steps
Validator sentiment is currently close to the activation threshold. The most recent snapshot shows 27 trusted validators have voted in favor of the amendment, with eight against, resulting in approximately 77% support. This places the amendment just one vote shy of the 80% required to initiate the 14-day activation countdown. FrancisBovineSwift described the current voting status as “nearly there.”
This security rebuild for Batch V1.1 follows other recent scrutiny of XRPL amendments, including the withdrawal of the Permission Delegation amendment due to a high-severity bug found before mainnet deployment. The current Batch V1.1 amendment has undergone additional review in light of these past events.
To enhance transparency in the amendment process, an XRPL testing dashboard was launched this month, tracking which transaction types, fields, and result codes have been exercised on Devnet, making amendment testing more visible to the community.
While Batch V1.1 is nearing activation, the exact date remains dependent on the final validator votes. The specific details of all ‘other issues’ addressed during the rebuild beyond the primary signature-validation bug are not fully detailed in the provided information.
Why This Matters
The materials describe a narrow update: The XRP Ledger’s Batch V1. The exact date of activation is dependent on the final validator vote.
Broader Context
Source materials place the factual news in this context: The XRP Ledger’s Batch V1.1 amendment is one validator vote short of reaching the 80% threshold needed to begin its 14-day activation countdown, after a security rebuild that followed a critical flaw in the original version.
Leave a Reply