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
- Version
- xrpld 3.3.0
- Enabled
- Oct 9, 2026 (UTC)
What does this amendment change?
What changes compared with the predecessor?
Who is this change relevant to?
What limitations and risks remain?
What fee and performance figures does the specification provide?
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?
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?
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.