XRPL Batch upgrade nears activation after developers fix 11 bugs

The XRP Ledger’s Batch V1.1 amendment has moved within one validator vote of starting its two-week activation process after developers fixed another 11 software issues uncovered during security reviews. Summary XRP Ledger’s Batch V1.1 has secured 27 of 35 validator votes, leaving it one vote short of the 80% activation threshold. Developers fixed another 11 issues involving signatures, authorization checks and potential server crashes before the latest vote. Batch would let users combine up to eight transactions into one operation and require linked payments to complete together. The current version replaced an earlier Batch proposal after researchers found a serious authorization flaw before it reached mainnet. RippleX said Monday that the latest review of Batch V1.1 identified problems involving transaction signatures, authorization checks and server crashes, with the fixes incorporated into the version now being considered by XRP Ledger validators. Support stood at 27 of the 35 trusted validators on Tuesday, equal to roughly 77%, leaving the proposal just below the 80% level required to enter the network’s activation period. XRP Ledger Batch upgrade closes in on 80% support Batch V1.1 would allow as many as eight transactions to be grouped into a single operation, with execution rules that can require linked transactions to succeed together. For a token swap between two users, the feature could make both transfers dependent on each other. If one side of the exchange fails, the other transaction would not be completed independently. Wallets and marketplaces could use the same structure to process a customer payment and a platform fee together. RippleX said commercial projects using Batch are already under contract or development, though the developer team has not publicly identified the companies involved. Validator support has risen quickly 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%, crypto.news previously reported. Three more validators have since backed the amendment. Under XRP Ledger governance rules, an amendment must maintain at least 80% validator support for 14 consecutive days before it can activate. With 35 trusted validators currently counted, another supporting vote would take Batch V1.1 above the threshold and begin that period. You might also like: Clearpool plans XRPL expansion and CPOOL migration The outcome would not be locked in once the countdown starts. Validators can change their positions, and support falling below 80% during the 14-day window would interrupt the activation process. A similar process played out in July when the fixCleanup3_2_0 amendment secured 85.71% support and entered its activation window. The package subsequently activated on July 29 after retaining enough validator backing for the required period.