XRPL Batch Is Live: One Request, Several Actions. What to Check Before You Sign
XRPL turned on Batch on Oct. 9, 2026. A Batch groups several actions into one request. Here is what the four modes mean and what to check before you sign.
XRPL Batch Is Live: One Request, Several Actions. What to Check Before You Sign
On Oct. 9, 2026, the XRP Ledger (XRPL) turned on a feature called Batch on Mainnet, its main live network. A Batch groups several actions into one signed request. It can hold two to eight actions. XRPL calls each action a transaction.
If a wallet or app asks you to approve a Batch, ask one question: what happens if one action fails? The answer depends on a setting called the batch mode.
This article explains what changed, what the four modes mean, and what XRPL's own documentation says a wallet should show you before you sign. This is not a price story. Turning on Batch changes how actions can be grouped. None of the cited sources links it to the price of XRP.
What changed on Oct. 9
XRPL's Known Amendments page lists two amendments as enabled on 2026-10-09. An amendment is a protocol upgrade. BatchV1_1 adds Batch. fixBatchV1_2 fixes how Batch checks the actions inside it.
The fix appears in an Oct. 9 vulnerability disclosure on xrpl.org. It says the problem was found on Sept. 18. Using it required specially hand-built transaction data, and no Mainnet funds were affected. The report also says support for BatchV1_1 was withdrawn and then restored, so that Batch would turn on only together with the fix.
Batch has had other security review too. XRPL's Batch page says Halborn, a security firm, audited it in January and February 2025. Halborn audited a separate fix to signature checks in March and April 2026.
What a Batch does
A Batch wraps two to eight actions into one group. The documentation says Batch is meant to prevent half-finished or surprising results in multi-step tasks. It lists two examples. One is creating an NFT (a unique digital item) and making an offer for it in one request. The other is a swap of tokens or NFTs between two accounts, where neither side has to trust the other.
The four batch modes
The mode decides how the actions in the group are handled. Here is each one, using the documentation's definitions.
- All or nothing (ALLORNOTHING). Every action must succeed, or none of them count. In the documentation's example, if the offer for a newly created NFT fails, the creation is undone too.
- Only one (ONLYONE). Only the first action that succeeds counts. The others either failed or were never tried. The documentation gives an example of sending several offers that each allow a different amount of slippage, which means price movement.
- Until failure (UNTILFAILURE). The actions run in order until the first one fails. Anything after that failure is not applied.
- Independent (INDEPENDENT). Every action is tried, even if one or more fail.
The practical difference is simple. In all-or-nothing mode, you get the whole set or none of it. In the other three modes, only part of the set may happen. The mode tells you which part.
What to check before you sign
XRPL's documentation lists what wallets should do when they show or sign a Batch. Those tips also work as a checklist for you:
- Read every action. The documentation says wallets should clearly show all of them before asking for a signature. That way you understand everything you are approving.
- Find the mode. Wallets should show the batch mode and explain what it means.
- Look for other accounts. Everyone involved signs the whole batch. Your signature approves all of it, including other accounts' parts. Wallets should warn you when a batch includes actions from other accounts.
The documentation explains why the whole batch is signed. In its example, Alice and Bob swap 1,000 XRP for 1,000 USD. If only Alice's part were signed, Bob could change his part to send 1 USD and still receive the 1,000 XRP. Signing the whole batch prevents that.
How to see what happened
A success result on the group does not mean every action inside it succeeded. The documentation says the group's result can show success even when actions inside it fail. That is because the result only covers the batch's own processing and fee. Each action inside the group has its own result. The documentation tells developers to check each one. A block explorer, which is a website that shows ledger activity, can help. Look for one that shows the actions together with their batch.
The documentation adds two more details. Actions inside a batch carry no signature and no fee of their own. The batch fee covers them, so a batch costs more than a single standard transaction. Also, Batch does not work with the simulate method, which tests a transaction before it is sent. It cannot test several actions together.
What we do not know yet
- The pages cited here do not list which wallets or apps support Batch, so this article makes no claim about any specific product.
- Some kinds of actions, including Loan and Vault transactions, cannot currently be used inside a batch, according to the Batch reference.
- Batch changes how actions are grouped. It does not change what any single action in the group does.
What to take from this
If you never see a batch request, nothing changes for you. If you do, treat it like a contract with several clauses. Read every clause, check the mode, and confirm the result of each action afterward.
Sources
- XRPL.org, Known Amendments (BatchV1_1 and fixBatchV1_2, enabled 2026-10-09)
- XRPL.org, Batch Transactions concept page
- XRPL.org, Batch transaction reference
- XRPL.org, Vulnerability Disclosure Report, Oct. 9, 2026
Disclosure: This article summarizes XRPL's published documentation and amendment records. It does not say which wallets or apps support Batch, and it makes no statement about XRP's price. The featured illustration is generated artwork. This article is not financial, legal, or investment advice. AI-assisted research and writing. Cited sources, not AI alone, support the claims.