The XRP Ledger is targeting October 9 for a batch upgrade that would enable users to bundle multiple transactions into one submission, potentially reducing the risk of partial trade completion. The upgrade implements XLS-56, a standard for grouped execution, and requires validator support above 80% for two consecutive weeks to activate.
Bundling Up to Eight Transactions
Under the pending upgrade, users could package several operations into a single submission rather than sending each transaction separately. Users would still pay transaction fees in XRP, the network's native cryptocurrency, with charges applying to activity involving XRP and other assets recorded on the shared blockchain.
As of October 3, 30 of 35 trusted validators were backing the batch upgrade, equivalent to 85.71% support. Validators check transactions and participate in decisions on network changes.
All-or-Nothing Execution for Conditional Trades
A key feature of the batch upgrade is all-or-nothing execution, which would allow a buyer exchanging payment for a digital asset to make both transfers conditional on success. If either step fails, neither transfer takes effect. This design permits operations involving one account or multiple accounts, enabling participants to coordinate exchanges without completing one side independently.
The upgrade offers four execution modes, giving developers different ways to handle success and failure scenarios. Participants in multi-account exchanges must authorize the entire group for the transaction to proceed.
Processing Costs Remain
Bundling does not eliminate transaction costs. The combined charge includes underlying fees, an overhead charge, and applicable signature charges. Failed attempts still incur XRP fees, and processing charges remain payable even when an all-or-nothing submission's actions do not take effect.
Security Amendment and Software Requirements
Alongside the feature upgrade, the XRP Ledger released server software version 3.4.1 on September 25 to address security-sensitive issues. The release introduced fixBatchV1_2, a separate amendment correcting how grouped actions are checked. If it activates, servers running older software will become unable to stay synchronized with the network.
The security amendment's projected activation is October 9 at approximately 10:12 a.m. EDT, followed by the batch feature around 10:46 a.m. EDT, provided each retains required validator support.
Background on XRP Ledger Activity
The batch settlement feature follows growth in XRPL transaction activity. Data from September 2 showed average daily transactions rose 21% to 2.4 million during January through July. The upgrade also reflects broader momentum in tokenization, which represents assets such as funds or bonds as blockchain-based tokens that can be transferred between holders.
