XRP Ledger Batch upgrade delayed to October 9 after validator support briefly drops below threshold

The XRP Ledger's highly anticipated Batch upgrade has been delayed to October 9, 2026, after validator support briefly fell below the required 80% threshold, resetting its 14-day activation countdown. The upgrade introduces native atomic settlement, allowing up to eight transactions to succeed or fail together. To address a minor issue with the feature, XRP Ledger Operations released the xrpld 3.4.1 software update and introduced the fixBatchV1_2 amendment. Meanwhile, the separate PermissionDelegationV1_1 upgrade was also delayed to October 8, 2026, following a similar temporary drop in validator support.

Delay of the Batch upgrade

• ▪The Batch upgrade, formally named BatchV1_1, regained support from 30 of 35 trusted validators on September 25, 2026, restarting its 14-day activation countdown.
• ▪The XRP Ledger's Batch upgrade was delayed by at least 10 days to October 9, 2026, after validator support briefly fell below the required 80% threshold.

Release of xrpld version 3.4.1

• ▪The xrpld 3.4.1 software update caused no impact to the XRP Ledger mainnet and resulted in no loss of user funds.
• ▪XRP Ledger developers introduced the fixBatchV1_2 amendment alongside the xrpld 3.4.1 update to resolve a minor issue in the Batch feature.
• ▪XRP Ledger Operations released xrpld version 3.4.1 on September 25, 2026, to address a minor issue with the Batch feature and improve server stability.
• ▪The fixBatchV1_2 amendment is marked as 'Default Yes' and is currently in its two-week activation period alongside the main Batch amendment, BatchV1_1

How the Batch feature works

• ▪The Batch feature, known as BatchV1_1, allows users to group two to eight regular XRP Ledger transactions into a single main transaction that executes them together
• ▪The BatchV1_1 feature offers an all-or-nothing mode that enables simultaneous payment and delivery of tokenized assets, canceling the entire batch if any transaction fails

Development history of the Batch amendment

• ▪The corrected BatchV1_1 implementation was released in August 2026 with version 3.3.0 of the ledger software and has since passed three outside reviews.
• ▪The original Batch amendment, later replaced by BatchV1_1, was withdrawn before reaching the mainnet after auditors identified a critical signature-validation flaw that could allow unauthorized transactions

Delay of the PermissionDelegationV1_1 upgrade

• ▪PermissionDelegationV1_1 lost its required validator support on September 23, 2026, but regained it a day later, resetting its 14-day countdown.
• ▪The PermissionDelegationV1_1 upgrade, which allows account owners to delegate specific tasks without sharing master signing keys, was delayed to October 8, 2026.

Debatable claims

• ▪The XRPL Batch upgrade's lack of XRP token utility limits its market impact
• ▪The XRP Ledger's 14-day continuous voting rule unnecessarily delays network upgrades