Skip to content
EnabledTier BUsability

BatchV1_1 XLS-56

The corrected Batch version processes two to eight transactions as one batch. BatchV1_1 is enabled on the XRP Ledger. xrpscan reports Oct 9, 2026 (UTC) as its activation date and xrpld 3.3.0 as its first version.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Enabled
XLS
XLS-56
Enabled
Oct 9, 2026 (UTC)

What does this amendment change?

Why does this amendment exist?

Previously, multistep workflows used separate transactions. If a later step failed, earlier steps remained effective. The first Batch version was disabled after a signature-verification bug, so the feature returns under a new amendment ID.

How does the mechanism work?

The outer Batch transaction carries the fee and signature. Inner transactions are unsigned, have a fee of 0, and carry tfInnerBatchTxn. A mode flag specifies whether all succeed together, at most one succeeds, processing stops at the first failure, or all execute independently. Other required signers, including delegates where applicable, sign through BatchSigners; their signature binds the outer account, Sequence or TicketSequence, and flags, plus the IDs of every inner transaction.

What changes compared with the predecessor?

BeforeAfter
Multiple transactions could only be submitted individually. The original Batch version has been marked unsupported since rippled 3.1.1 and cannot be activated.With the amendment enabled, an account can submit two to eight transactions in a batch, including transactions involving other accounts that cosign through BatchSigners. Inner transactions appear in the same ledger with their own metadata and a ParentBatchID reference.

Who is this change relevant to?

XRP holders and users

A batch can execute several payments or settings in one submission. Every inner transaction must be visible before signing because the signature authorizes the entire batch.

Wallets and app developers

The outer transaction reports tesSUCCESS even when inner transactions fail. Apps must therefore inspect inner transaction result codes and advance sequence handling only after validation.

Exchanges and issuers

Exchanges and services can implement atomic exchanges between accounts using the appropriate batch mode. Explorers and indexers associate inner transactions with their batch through ParentBatchID.

Node operators

Nodes verify each BatchSigners entry individually, accept inner transactions only as part of the outer transaction, and apply them through it.

What limitations and risks remain?

  • A batch contains at least two and at most eight inner transactions.
  • A batch cannot contain another batch.
  • The Batch transaction itself cannot be delegated. Inner transactions may carry the Delegate field.
  • Pseudo-accounts cannot sign BatchSigners entries.

What fee and performance figures does the specification provide?

  • The outer transaction costs twice the base fee, plus the fees required for all inner transactions and one base fee for each additional signature, such as those in BatchSigners.
Technical details: transactions, fields, codes and invariants

Transactions

  • Batch
  • inner transactions with tfInnerBatchTxn

Fields and flags

  • RawTransactions (2 to 8 entries)
  • BatchSigners (at most 24 entries, sorted by Account in ascending order)
  • ParentBatchID
  • tfAllOrNothing 0x00010000
  • tfOnlyOne 0x00020000
  • tfUntilFailure 0x00040000
  • tfIndependent 0x00080000
  • tfInnerBatchTxn 0x40000000

Result codes

  • temINVALID_FLAG
  • temARRAY_EMPTY
  • temARRAY_TOO_LARGE
  • temBAD_FEE
  • temBAD_SIGNATURE
  • temBAD_SIGNER
  • temINVALID_INNER_BATCH
  • temREDUNDANT
  • temSEQ_AND_TICKET
  • tefBAD_AUTH
  • tefBAD_QUORUM

What does a concrete workflow look like?

In a hypothetical exchange, Alice trades 1,000 XRP for 1,000 USD from Bob. Bob submits a batch in tfAllOrNothing mode containing both payments, Alice cosigns through BatchSigners, and the ledger executes both payments together or neither. These amounts are illustrative, not an exchange-rate quote.

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

BatchV1_1 is enabled on the XRP Ledger. xrpscan reports Oct 9, 2026 (UTC) as its activation date and xrpld 3.3.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

BatchV1_1 has no amendment family with other members on this site, so there is no progression to show here.

Which primary sources support this information?

← All XRPL amendments and XLS specifications