One Vote Could Trigger XRPL Countdown
The XRP Ledger is closing in on the approval needed to activate Batch V1.1, a feature that would let users combine up to eight related transactions into one operation. As of Tuesday, 27 of the network’s 35 trusted validators supported the amendment, equivalent to about 77%.
XRPL requires 80% validator support for network amendments to activate. One additional supporting vote would therefore be enough to cross the threshold and launch the 14-day activation countdown.
Batch V1.1 introduces atomic transaction bundling, allowing multiple linked transactions to be handled as a single unit. If one transaction fails, the others in the batch also fail, reducing the risk of a partially completed transfer.
A token swap is one example. Two parties could link their transfers so that both sides are completed together, rather than allowing one payment to go through while the other fails.
The 80% support level must be maintained throughout the entire 14-day activation period. Validators can revise their votes during that window, so reaching the threshold does not by itself guarantee activation.
Batch V1.1 Gets Further Security Checks
The latest voting process follows fixes to 11 issues discovered during a deeper review of the Batch V1.1 implementation.
Ripple’s development division, RippleX, published details of the work on Monday. The amendment was delivered through the xrpld 3.3.0 software release and has since entered the validator voting stage.
The 11 findings covered signature handling, authorization checks and defects that could potentially cause servers to crash. Security firm Common Prefix identified one critical vulnerability that could have allowed an attacker to reuse a signed permission from a user and execute additional transactions beyond what had been authorized.
According to RippleX, the updated implementation was reviewed by four senior engineers and examined through audits conducted by Halborn and Common Prefix. It also underwent a public security contest and automated testing.
Businesses Could Use Batch for Payments
RippleX has said commercial applications built around the Batch feature are either under contract or in development, although it had not identified the companies involved as of Tuesday.
The functionality could prove useful for wallets, marketplaces and other payment platforms. A marketplace, for example, could combine a customer’s payment and the platform’s fee into one atomic batch, ensuring that both actions are processed together.
The new implementation was developed after researchers uncovered a more serious flaw in the original Batch proposal earlier this year. Under certain conditions, the vulnerability could have allowed an attacker to add transactions belonging to another user’s account without obtaining that user’s approval.
That earlier version was never deployed on the live XRP Ledger. Developers replaced it with the implementation included in xrpld 3.3.0, released on Aug. 6, and subjected the revised version to additional internal reviews, external audits and public bug hunting.
For now, Batch V1.1 remains below the 80% activation threshold. The next validator vote could determine whether the XRP Ledger begins its two-week countdown toward the upgrade.
