As reported, a minor issue was detected with the fix included in the xrpld 3.4.1 release; the $XRP community subsequently flipped their votes to allow Batch to simultaneously launch with its fix update.
Batch (XLS-56) allows multiple XRPL transactions from multiple accounts to be executed atomically in a single ledger close. If an inner transaction fails in the all-or-nothing mode of the feature, the entire batch is rolled back.
Batch is required or serves as an accelerant for several high-value XRPL use cases already under contract or in active pipeline, such as atomic multi-party settlements.
In line with XRPL’s consensus process, amendments must maintain two weeks of support from more than 80% of trusted validators to be enabled.
If support drops below 80%, the amendment is temporarily rejected, and the two-week period restarts. Given the past setbacks it faced, the Batch feature launch is a significant milestone for the $XRP community. If everything goes well and support remains above 80%, Batch will be launched.
What’s next?
The permission delegation amendment is expected to arrive on the mainnet in the next four days, on October 8, 2026.
At the recently concluded $XRP Seoul event, RippleX head of engineering JA Akinyele shared a keynote on what is being built into the $XRP Ledger to support the next wave of developers, institutions, and users.
To handle the growing demand for complex financial operations on-chain, the XRPL architecture is undergoing rigorous upgrades that include formal verification, adversarial testing, and new structural features like transaction batching, which enables bundled, all-or-nothing operations to boost system efficiency and developer scalability.
