The XRP Ledger has activated its Batch feature on mainnet, allowing users to combine between two and eight transactions into a single operation. The upgrade received support from 30 validators, while five voted against it, according to XRPScan data.
The amendment, known as BatchV1_1, completed the network’s two-week approval process before becoming active. With 30 of 35 validators supporting the change, approval reached approximately 85.7%.
The new feature is designed to make transactions involving multiple steps easier to manage. It could support over-the-counter trades, payments between businesses, NFT exchanges and other transactions where several actions need to be coordinated.
According to the XRP Ledger’s documentation, a Batch transaction contains an outer transaction and between two and eight inner transactions. Its execution mode determines whether all actions must succeed together or whether individual actions can proceed separately.
Batch opens new options for XRP Ledger users
XRPL validator Vet described the upgrade as an important development for both institutions and individual developers.
He pointed to potential uses such as over-the-counter trades, delivery-versus-payment settlement, NFT-for-NFT exchanges and payments that depend on other actions being completed.
Vet said the feature could create new opportunities for developers building applications on the XRP Ledger.
RippleX had previously said commercial projects using Batch were already under contract or in development. Examples included token swaps between users and customer payments combined with platform fees, although the companies involved were not identified.
The feature also includes rules for transactions that require approval from multiple accounts. These rules help ensure that participants authorize the actions included in a transaction bundle rather than treating each transfer as a separate payment.
Four execution modes control how transactions work
The Batch feature offers four execution modes, each designed for a different situation.
- All or Nothing: Every included transaction must succeed for the group to complete successfully.
- Only One: The group allows just one transaction to succeed, making it suitable for certain alternative-action scenarios.
- Until Failure: Transactions are processed in order until one fails, while earlier successful actions can remain completed under the protocol’s rules.
- Independent: Each transaction is attempted separately, so one failure does not automatically prevent the others from succeeding.
Developers must select an execution mode when creating a Batch transaction. The protocol also prevents one Batch from containing another Batch transaction and rejects duplicate inner transactions.
However, developers must still check the results of individual transactions. A successful result for the outer Batch does not necessarily mean every included action succeeded.
The XRP Ledger’s official guidance recommends reviewing individual transaction results and checking account balances. Even when a Batch fails under the All or Nothing mode, the transaction fee can still be deducted.
Security fixes preceded the activation
The Batch upgrade followed earlier work to address software issues identified during development.
Previous reporting said developers had fixed 11 issues before the approval process. A later emergency software release introduced additional security-related fixes through the fixBatchV1_2 amendment.
The XRP Ledger Foundation also urged operators to upgrade their software promptly ahead of the expected activation of a separate security amendment.
These steps highlight the importance of testing and reviewing protocol changes before they become active across the network.
XRPL lending update introduces new vault rules
Alongside Batch, another XRP Ledger amendment focuses on lending. LendingProtocolV1_1 introduces closed-ended vaults and changes how interest is recorded, according to the network’s version 3.4.0 release notes.
The lending design divides a vault’s life into subscription, investment and redemption periods.
During subscription, depositors can add or withdraw assets. Once the investment period begins, deposits and withdrawals stop while the funds are made available for loans. After that period ends, depositors can enter the redemption phase and recover their share as loans mature.
The revised accounting rules would also recognize interest when borrowers actually pay it instead of recording all scheduled interest at the beginning of a loan.
Existing vaults would retain their previous accounting model after the amendment activates, according to the documentation.
The release of supporting software does not automatically activate an amendment. Validator approval is still required under the XRP Ledger’s governance process.
Evernorth prepares for its planned Nasdaq listing
Separately, Evernorth is preparing for a planned Nasdaq listing that would give stock-market investors exposure to a company holding XRP.
The company previously moved its expected XRPN trading debut from Oct. 8 to Oct. 12 because of an administrative delay. Trading remains subject to the completion of the transaction and Nasdaq listing requirements.
Evernorth said it expected to hold approximately 473 million XRP at closing. Its Oct. 6 SEC filing also confirmed that shareholders of Armada Acquisition Corp. II had approved the business combination at a special meeting on Sept. 30.
The planned listing represents a separate development from the XRP Ledger’s technical upgrades, but it adds to the range of activity surrounding the XRP ecosystem.
Overall, the activation of Batch gives developers a new way to coordinate multiple transactions on the XRP Ledger. Its potential uses include linked payments, trades and digital asset exchanges, while the separate lending changes aim to establish clearer rules for vault operations and interest accounting.
