Image Credit: Shutterstock
XRP Ledger’s BatchV1_1 upgrade remains short of the validator support needed for activation, with 24 of 35 validators backing the amendment as of September 8.
That puts support at 68.57%. XRPL amendments must remain above 80% for 14 consecutive days before they activate, meaning the countdown for BatchV1_1 has not started.
BatchV1_1 Needs Five More Votes Before 14-Day Countdown
With 35 validators in the current voting set, BatchV1_1 needs at least 29 affirmative votes to move above the 80% threshold. Another five validators would therefore need to support it if the validator count remains unchanged.
Crossing 80% would not activate BatchV1_1 immediately. Support must stay above the threshold for two weeks, and the timer resets if it falls back to 80% or lower. There is no confirmed activation date.
A September activation remains possible only if validator support rises above the threshold soon enough and remains there for the full 14-day period.
BatchV1_1 Would Bundle Up to Eight Transactions
BatchV1_1 would allow users to package between two and eight transactions inside a single Batch transaction.
Developers can select different execution modes depending on whether all transactions must succeed, processing should stop after a failure or each transaction should be handled independently.
The structure can support atomic swaps, NFT transactions paired with offers, platform fee collection and multi-account operations.
February Flaw Forced Withdrawal of Earlier Batch Amendment
BatchV1_1 replaces an earlier Batch amendment that was withdrawn after researchers discovered a critical authorization flaw in February.
The vulnerability could have allowed an attacker to execute transactions from another account without possessing its private keys, potentially enabling unauthorized payments or account changes.
Validators were told to vote against the amendment, and rippled 3.1.1 prevented it from activating. The vulnerable version never went live on XRPL Mainnet.
The corrected BatchV1_1 implementation shipped with rippled 3.3.0 on August 6. With 24 of 35 validators currently supporting it, five additional affirmative votes are needed before the 14-day activation countdown can begin if the voting set remains unchanged.
