Image Credit: Shutterstock
XRP Ledger’s Batch V1.1 amendment has secured support from 27 of 35 trusted validators, leaving it one vote short of the 80% threshold needed to start its 14-day activation countdown. The feature is not active on the network.
If the voting set remains at 35 validators, one additional affirmative vote would bring support to 28 of 35, or 80%, and start the two-week majority period. Validator support must then remain at the required level through the full activation window.
Batch V1.1 Can Link Up to Eight XRP Ledger Transactions
Batch V1.1 would let users submit up to eight transactions inside one batch. Its all-or-nothing mode allows linked transactions to succeed together or fail together, reducing the risk that only part of a coordinated operation is completed.
The structure can support atomic token swaps between accounts, coordinated settlements and transactions that combine a payment with a platform fee. Other execution modes are available when developers do not require every transaction in a batch to succeed together.
Revised Amendment Fixes Critical Authorization Flaw
Batch V1.1 replaces the original Batch amendment, which was disabled before activation after researchers identified a critical authorization flaw. Under specific conditions, the vulnerability could have allowed an inner transaction from another account to execute without that account holder’s valid authorization.
XRP Ledger developers withdrew validator support and marked the original amendment unsupported in rippled 3.1.1. The replacement tightened signing and authorization checks and was released with rippled 3.3.0 in August.
A subsequent security review of the revised implementation identified and fixed 11 additional issues involving signatures, authorization, and server stability.
28 of 35 Validator Votes Would Start 14-Day Majority Period
With the voting set currently at 35 validators, reaching 28 affirmative votes would meet the 80% threshold required to begin the activation countdown. That would not make Batch V1.1 immediately available.
The amendment must maintain the required validator support for 14 consecutive days before it can activate. Validators can change their votes during that period. If support falls below the required threshold before the majority period is completed, the countdown resets.
