The XRP Ledger is aiming to activate two amendments on Oct. 9 that would expand how transactions can be handled on the network while also requiring some infrastructure operators to update their software. The changes remain contingent on validator backing staying above the required threshold through the activation window.
If approved, the BatchV1_1 amendment would let users submit up to eight transactions together so related actions, such as a payment and an asset transfer, can settle as one coordinated operation. A separate amendment, fixBatchV1_2, addresses a security-sensitive issue and would make version 3.4.1 a necessary software update for servers that want to remain in sync with the ledger.
Validator support remains above the activation threshold
On Oct. 3, XRP Ledger’s amendment dashboard showed 30 of 35 trusted validators supporting BatchV1_1, or 85.71%. Under XRPL rules, amendments need more than 80% validator support for two consecutive weeks before they can take effect.
That requirement applies continuously: if support drops below the threshold before activation, the countdown resets. The Oct. 9 timing therefore remains a target rather than a guaranteed launch date.
BatchV1_1 would group multiple actions in one submission
The pending feature implements XLS-56, a standard for grouped execution on XRPL. In practice, it would allow up to eight transactions to be bundled into a single submission instead of being sent one by one.
The design is intended to support all-or-nothing execution, so linked actions can either all complete or all fail together. That could reduce the risk of only part of a transaction sequence settling, such as an asset being delivered without the corresponding payment, or the reverse.
BatchV1_1 is a corrected version of an earlier implementation. It replaces the previous Batch proposal after a security flaw was found.
Security amendment would force older servers out of sync
A separate amendment, fixBatchV1_2, is advancing on a similar timeline. XRPL released server software version 3.4.1 on Sept. 25 to address security-sensitive issues, including the fix covered by that amendment.
If fixBatchV1_2 activates, server operators running older software will no longer be able to stay synchronized with the network. That makes the software release effectively mandatory for infrastructure providers that want to continue tracking the live ledger correctly.
Upgrade arrives amid rising activity and tokenization efforts
The proposed changes come as XRPL has recorded higher transaction activity and broader tokenization efforts. Data summarized on Sept. 2 showed average daily transactions increased 21% to 2.4 million during the January-to-July period.
The source article also noted that tokenization on XRPL refers to representing assets such as funds or bonds as blockchain-based tokens that can be transferred between holders. Ripple has been building related infrastructure as well, including investments in Zilo and Licuido announced in August.
Next confirmed milestone is the Oct. 9 activation window
Based on the published projection, fixBatchV1_2 is expected first on Oct. 9 at about 10:12 a.m. EDT, with BatchV1_1 following at roughly 10:46 a.m. EDT. Those times hold only if each amendment maintains the required validator majority until activation.
For users, the main functional change would be the ability to coordinate up to eight actions in one submission. For server operators, the immediate confirmed step is ensuring they are running version 3.4.1 if the security amendment goes live.
Source: news.bitcoin.com