The XRP Ledger’s Batch V1.1 amendment is now one validator vote away from beginning the network’s 14-day activation process after developers said they fixed 11 additional software issues uncovered in security reviews.
Support reached 27 of the 35 trusted validators on Tuesday, or about 77%, just below the 80% threshold required under XRPL governance rules. If one more validator backs the proposal and that support holds, the amendment can enter its activation window, though it would still need to keep enough votes for two full weeks before going live.
What the amendment would do
Batch V1.1 is designed to let users combine up to eight transactions into a single operation. It also supports execution rules that can make linked actions succeed or fail together rather than being processed independently.
That structure could be used for token swaps between two users, where each side of the exchange depends on the other. If one transfer cannot be completed, the other would not settle on its own. RippleX has also said wallets and marketplaces could use the feature to handle a customer payment and a platform fee in the same coordinated operation.
According to RippleX, some commercial projects are already under contract or in development to use Batch, although the company has not publicly identified them.
Support has climbed, but activation is not guaranteed
Validator backing has increased over the past week. On Sept. 8, Batch V1.1 had 24 votes from the 35 validators on the default Unique Node List, equal to 68.57%. Three additional validators have since moved in favor of the amendment.
On XRPL, amendments do not activate as soon as they cross the threshold. They must first maintain at least 80% support for 14 consecutive days. With 35 trusted validators currently counted, one more supporting vote would be enough to start that countdown.
Even then, the process could still be interrupted. Validators can change their positions, and if support drops below 80% at any point during the two-week period, activation would pause. A recent example came in July, when the fixCleanup3_2_0 amendment entered its activation window at 85.71% support and later activated on July 29 after retaining sufficient backing.
Why Batch V1.1 replaced the original proposal
The current vote comes after developers withdrew an earlier Batch design when researchers found a serious flaw before the feature reached the XRP Ledger mainnet. Under certain conditions, that issue could have allowed an attacker to include transactions from another user’s account inside a batch without the required authorization.
No user funds were put at risk because the original amendment never activated. Developers then rebuilt the feature, and Batch V1.1 was later included in xrpld 3.3.0, which was released on Aug. 6.
RippleX software engineer Mayukha Vadari said the original signature-related problem was discovered in February before mainnet deployment. The follow-up work included a root-cause fix, reviews by four senior engineers, a Sherlock security contest, and audits by Halborn and Common Prefix.
Security reviews found 11 more issues
RippleX said the latest review of Batch V1.1 uncovered 11 additional issues involving signature handling, authorization checks and conditions that could crash servers. The fixes were incorporated into the version now under validator consideration.
One of the findings was classified as critical by Common Prefix. According to RippleX’s summary, that issue could have allowed an attacker to reuse permission previously signed by a user and carry out more transactions than the user intended to authorize.
RippleX said the implementation also went through automated testing, internal review by four senior engineers, and outside audits by Halborn and Common Prefix, in addition to the public security contest.
Part of a broader XRPL software cycle
Batch is one of several proposed protocol changes introduced in the xrpld 3.3.0 software cycle. Other proposals outlined before the release included Confidential MPT, Sponsor, Dynamic MPT and Permission Delegation.
In XRPL’s amendment system, inclusion in node software does not make a feature active on mainnet. Each proposal follows its own validator vote. That has already led to different adoption speeds across the 3.3.0 feature set.
The next confirmed step for Batch V1.1 is straightforward: it needs one more validator vote to cross the 80% mark and begin its 14-day activation window, provided current support remains in place.
Source: crypto.news