XRP Ledger activates Batch upgrade for bundled transactions

The XRP Ledger switched on its Batch upgrade on October 9, 2026, a change that lets a single wallet run up to eight transactions as one all-or-nothing operation. Thirty of the network's 35 trusted validators backed it.

Confirmation came from XRPScan, the ledger's amendment tracker, and from XRP Ledger developer documentation, with crypto.news reporting the activation the same day. Batch, listed in the technical specs as XLS-56, had sat in a validator vote for weeks.

What the Batch upgrade does

Before Batch, a user who wanted to chain several steps on the XRP Ledger had to send each transaction on its own. If one failed, the others could still go through. That left people with half-finished trades.

Think of a swap that needs a payment to go out and a token to come back. Those were two separate sends. One could clear while the other failed. Batch ties them so they either both happen or neither does.

The key word is atomic. All or nothing. If any single transaction in the bundle fails, the whole batch reverts and nothing settles. The feature also allows multi-account execution, so transactions from more than one account can clear in the same ledger close. XRP Ledger documentation points to atomic swaps as one pattern it enables, where two parties exchange assets in a single step with no risk that one side pays and the other does not.

How the amendment cleared the validators

Changes to the XRP Ledger go live through amendments. Each one activates only after at least 80 percent of trusted validators vote yes and hold that support for two weeks. Batch reached 30 of 35 validators, about 85.7 percent, according to XRPScan figures cited by crypto.news. Five validators voted against it.

Getting there took time. An earlier version of Batch was disabled in server release 3.1.1 after developers found a bug. The code that went live, named BatchV1_1, is the revised version, shipped in xrpld 3.3.0 on August 6, 2026. A separate security fix, fixBatchV1_2, came out of a September 25 emergency release and was set to activate alongside Batch so the two would land together. Server operators who stayed on old software risked being locked out of the network once the amendment switched on.

What else shipped in the release

Batch arrived as part of a wider update. That same 3.3.0 release added Sponsor, which lets a company cover the fees and reserve costs for its users, plus a revised Permission Delegation feature that lets one account hand specific powers to another without sharing its keys. A Confidential Transfer amendment, which hides token amounts while keeping them checkable on the ledger, is also part of the release.

Not every amendment runs on the same clock. Each has its own validator vote, so they do not all switch on at once. RippleX, the Ripple team that builds on the open-source ledger, has pushed a separate lending amendment, LendingProtocolV1_1, into voting, part of a wider push to put DeFi lending on more networks.

What to watch

Batch is live now. Real use is the open question. Vet, who runs one of the network's trusted validators, called the feature "important functionality for the XRP Ledger" for both institutions and retail builders. RippleX said commercial projects using Batch were already under contract or in development.

It named none of them. That gap matters, because an amendment going live is not the same as products running on it. The next signal is simple. Watch for a named app that settles a real multi-step trade through Batch, and watch whether the lending amendment clears its own vote. For readers newer to the token, XRP is the ledger's native asset and not a stablecoin.