As of September 8, 2026, the BatchV1_1 upgrade on the XRP Ledger has received support from 24 out of 35 validators on the primary Unique Node List (UNL). At 68.57%, this falls short of the activation threshold requiring more than 80%, or at least 29 votes. The network still needs five additional validator approvals just to reach the qualifying baseline.
Securing 29 votes is merely the first step. XRP Ledger governance rules require that 80% support hold continuously for 14 full days. If even a single validator withdraws support during this window and the percentage drops below the minimum threshold, the countdown timer automatically resets to zero. Since this opening requirement has not yet been achieved, reports predicting activation in September remain purely speculative.
Replacement for Previously Withdrawn Code
The BatchV1_1 upgrade is a revision of the original Batch amendment that was disabled last February. The withdrawal of the initial draft came after security researcher Pranamya Keshkamat and Cantina’s AI tool Apex uncovered a critical authorization flaw in the codebase.
The previous vulnerability would have allowed attackers to bypass verification checks and submit unauthorized transactions directly from a victim’s wallet. The system avoided a fatal incident because the original amendment was never activated on the mainnet, ensuring that no user funds were ever put at risk of theft.
Four Modes in a Single Transaction Bundle
Once activated, BatchV1_1 allows an account to bundle up to eight distinct transactions into a single coordinated operation. The feature comes with four built-in execution modes: ‘all or nothing’, ‘only one’, ‘until failure’, and ‘independent’.
The upgrade paves the way for efficient advanced use cases. Network users will be able to execute instant atomic token swaps, mint NFTs and create sell offers simultaneously, consolidate platform fees, and orchestrate actions across multiple accounts at once.
Node Technical Readiness Hurdles
The sluggish adoption pace is rooted in mandatory technical requirements for operators. Node managers must first install the software release supporting BatchV1_1 before casting their votes. Simultaneously, Clio history server operators are required to upgrade systems to version 2.8.0 to maintain synchronization across the broader ecosystem.
Reported via crypto.news.
Also read: How to Read Candlesticks for Beginners
Disclaimer: This article is for informational and educational purposes only, not financial advice. Cryptocurrency assets are highly volatile and carry significant risk. Always do your own research (DYOR) and never invest more than you can afford to lose.
