Key Takeaways
- XRPL users could bundle up to eight transactions in one submission.
- All-or-nothing execution would link asset delivery with payment.
- Activation requires validator support above 80% for two consecutive weeks.
8 Actions in One Submission, With Different Execution Rules
Payments and asset transfers could settle together under a pending XRP Ledger (XRPL) upgrade, reducing the risk that only part of a trade completes. The change implements XLS-56, the standard for grouped execution. Its corrected version, BatchV1_1, replaces an earlier implementation after a security flaw was discovered.
XRPL’s validator support and activation countdown dashboard showed 30 of 35 trusted validators backing BatchV1_1 on Oct. 3, equivalent to 85.71%. Validators check transactions and participate in decisions on network changes. Amendments require more than 80% support for two consecutive weeks; losing that majority resets the countdown.
The design packages several operations into a single submission rather than requiring users to send each separately. Users pay transaction fees in XRP, the network’s native cryptocurrency. Those charges apply to activity involving XRP and other assets recorded on the shared blockchain.
Digital asset platform Uphold said on X that more than 85% of validators backed the Batch upgrade, which could activate Oct. 9 if support remains above the required threshold.
Asset Delivery and Payment Can Become One Conditional Trade
A buyer exchanging payment for a digital asset could use an all-or-nothing batch to make both transfers conditional on success. If either step fails, neither transfer takes effect. The specification permits operations involving one account or multiple accounts, allowing participants to coordinate an exchange without completing one side independently.
The four Batch execution modes give developers different ways to handle success and failure. The other three settings execute only the first successful action, stop processing at the first failure, or handle each included operation independently. Participants in a multi-account exchange must authorize the entire group.
Bundling does not eliminate processing costs: the combined charge includes the underlying fees, an overhead charge, and applicable signature charges. During September’s transaction record, failed attempts still incurred XRP fees. Processing charges remain payable even when an all-or-nothing submission’s actions do not take effect.
Separate Security Fix Creates an Oct. 9 Software Deadline
Alongside the feature upgrade, XRPL released server software version 3.4.1 on Sept. 25 to address security-sensitive issues. That 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 settlement feature follows historical growth in XRPL transaction activity and tokenization. Data summarized Sept. 2 showed average daily transactions rose 21% to 2.4 million during January through July. Tokenization represents assets, such as funds or bonds, as blockchain-based tokens that can be transferred between holders.
Ripple has also pursued infrastructure for issuing and trading tokenized assets, including investments in Zilo and Licuido announced in August.
The security amendment’s projected activation is Oct. 9 at approximately 10:12 a.m. EDT, followed by BatchV1_1 around 10:46 a.m. EDT, provided each retains the required validator majority.
