XRP Ledger's BatchV1_1 amendment currently has 68% validator support with 24 of 35 validators voting in favor, according to XRPScan data. The amendment requires more than 80% support to be maintained continuously for fourteen days before activation can begin. As reported by XRPL documentation, amendments activate only after holding support from more than 80% of trusted validators for two consecutive weeks. If support falls below that level during the period, the timer resets. The feature could potentially reduce external infrastructure needs for coordinating dependent actions and could go live by the end of September if the threshold is maintained continuously.
The amendment requires more than 80% support to be maintained continuously for fourteen days before activation can begin. XRPL version 3.3.0 introduced BatchV1_1 on August 6 as a replacement for the original Batch amendment, which was disabled in February after researchers found a critical authorization flaw. According to reports, Pranamya Keshkamat and Cantina AI's Apex security tool identified an error in the logic used to verify batch signers, which could have allowed attackers to skip checks for some participants and submit unauthorized transactions. The corrected version removes the early-exit error, adds authorization safeguards, and narrows how each signer is checked, with an independent audit reviewing the replacement before release.
Batch transactions can contain up to eight inner transactions packaged inside an outer transaction that manages sequencing, fees and authorization. The four execution modes include 'All or nothing' requiring every inner transaction to succeed, 'Only one' applying the first successful operation, 'Until failure' processing transactions until one fails, and 'Independent' attempting every included transaction regardless of other results. This feature will simplify app development by enabling dependent on-ledger actions without complex infrastructure. Potential uses include atomic token swaps, NFT minting followed by offers, bundled platform fees, and coordinated actions involving multiple accounts. Multi-account batches require every participating account to authorize the full collection.
