The XRP Ledger is approaching a dual protocol change on October 9, combining a long-anticipated transaction bundling capability with a security-focused amendment that requires many server operators to update their software. The BatchV1_1 amendment would enable users to submit as many as eight transactions in a single operation, while the companion fixBatchV1_2 amendment addresses security-sensitive issues identified in related code.

As of October 3, 30 of the network’s 35 trusted validators, or 85.71 percent, supported BatchV1_1. The separate security amendment held backing from 34 validators. Protocol changes on the XRP Ledger take effect only after more than 80 percent of trusted validators maintain support for two consecutive weeks. Any drop below that threshold resets the countdown.

How Batch Transactions Would Work

BatchV1_1 implements the XLS-56 standard for grouped execution. It allows an account to package multiple operations into one submission rather than sending them individually. Developers can choose among four execution modes. One mode requires every included transaction to succeed or none take effect, enabling coordinated exchanges such as a simultaneous payment and asset delivery. Other modes process only the first successful action, halt at the first failure, or treat each operation independently.

The all-or-nothing option is designed to reduce the risk that only one side of a multi-step trade completes. Participants in multi-account batches must authorize the full group. Transaction fees in XRP still apply, covering the underlying costs plus an overhead charge and any signature-related fees. Failed batches can still incur charges even when no operations settle.

This version replaces an earlier Batch implementation that developers disabled after discovering a critical bug. The corrected amendment regained the required validator majority on September 25 after a brief dip below the threshold, restarting the two-week activation clock and shifting the earliest possible date from late September to October 9.

Security Amendment Creates Upgrade Deadline for Operators

Alongside the feature upgrade, XRP Ledger developers released server software version 3.4.1 on September 25 as an emergency update. The release introduced the fixBatchV1_2 amendment, which corrects how grouped actions are validated, rejects certain improperly wrapped inner transactions, and adds integer-arithmetic hardening in the payment engine and related helpers.

If fixBatchV1_2 activates, servers still running earlier software versions will become amendment-blocked and lose the ability to stay synchronized with the network. Ordinary XRP holders do not need to take any action. The projected sequence places the security amendment activation around 10:12 a.m. EDT on October 9, followed by BatchV1_1 near 10:46 a.m. EDT, provided both retain the necessary validator support.

Developers have described the changes as preventive. Full source code covering the security-sensitive portions has not yet been published and is scheduled for later release together with a retrospective analysis.

Activation Remains Conditional on Sustained Support

Both amendments remain subject to continued validator backing through the full two-week period. The process relies on decentralized consensus among trusted validators rather than unilateral decisions. Server operators maintaining nodes, exchanges, wallets, or other infrastructure dependent on live ledger data have been urged to install version 3.4.1 ahead of the potential activation window.

The Batch capability is expected to expand options for settlement, atomic exchanges, and more complex multi-step operations once adopted by applications and users. Activation of the amendments themselves does not automatically change how existing software behaves; developers and services must choose to use the new transaction format.