XRP Ledger activates bundled transactions feature

TLDR

XRP Ledger (XRP) has activated a new Batch / bundled transactions feature that lets users group multiple actions into a single on-chain operation.

1. The BatchV1_1 amendment is now live on mainnet, allowing two to eight bundled transactions with four execution modes, backed by a strong validator supermajority.
2. Bundled transactions enable atomic delivery-versus-payment, OTC deals, NFT swaps, and complex institutional workflows while keeping signatures and accounts separate.
3. Operators must run the latest xrpld version, and users should watch how wallets, exchanges, and apps integrate Batch and related upgrades over the coming months.

Deep Dive

1. What Bundled Transactions Do

The XRP Ledger has activated the BatchV1_1 amendment, which allows one outer transaction to carry two to eight inner transactions under a single envelope, as described in the official Batch upgrade overview.

The feature supports four execution modes:

1. All or Nothing (every inner transaction must succeed or the whole batch fails).
2. Only One (exactly one succeeds).
3. Until Failure (process in order until one fails).
4. Independent (each is attempted separately even if some fail).

Validators approved BatchV1_1 with 30 of 35 validators in favor, exceeding the roughly 80% supermajority that XRPL requires to activate amendments.

2. Why This Matters For Users

Bundled transactions make it easier to coordinate complex, linked actions without relying on external scripts or custodians.

Examples called out by XRPL ecosystem contributors include OTC trades, delivery-versus-payment settlement, NFT swaps, paired customer payments plus platform fees, and multi-account workflows where each party approves its own leg but everything settles together in one batch.

3. Risks, Safeguards, And What To Watch

Before activation, developers identified and fixed a structural bug in the original Batch implementation via a separate fixBatchV1_2 amendment, and an emergency xrpld 3.4.1 release patched a critical payment-engine overflow that was independent of Batch.

BatchV1_1 and fixBatchV1_2 activated together after network-wide upgrades, and older nodes now risk falling out of sync if they have not upgraded. Server operators and infrastructure providers therefore need to stay on supported versions.

Over the next phase, key things to watch are:

1. Wallet and SDK support for choosing Batch modes and reading per-transaction results.
2. Exchange and institutional adoption for DvP and treasury flows.
3. Any further security or decentralization debates around emergency upgrades and validator control.

Conclusion

XRP Ledgers bundled transactions bring atomic, multi-step operations directly into the base protocol, expanding what developers and institutions can build without external coordination layers. The upgrade comes with strengthened safeguards after a critical bug fix, so the main question now is how quickly wallets, exchanges, and enterprise users adopt Batch-based workflows and how consistently operators keep their infrastructure upgraded.