Skip to content
EnabledTier AUsability

TicketBatch XLS-13

Tickets allow transactions outside the normal sequence order. TicketBatch is enabled on the XRP Ledger. xrpscan reports Nov 18, 2021 (UTC) as its activation date and rippled 1.7.0 as its first version.

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

Status
Enabled
XLS
XLS-13
Enabled
Nov 18, 2021 (UTC)

What does this amendment change?

Why does this amendment exist?

An account's sequential Sequence forces independently prepared transactions into one shared order. This complicates parallel withdrawals, offline signatures, and multisigning workflows.

How does the mechanism work?

TicketCreate reserves up to 250 single-use TicketSequence values. A later transaction sets Sequence to zero and consumes exactly one ticket instead. Independent transactions from the same account can therefore be signed in advance and processed outside normal Sequence order.

What changes compared with the predecessor?

BeforeAfter
Before Tickets, transactions from one account were validated in sequential Sequence order; a pending transaction could hold up later sequence numbers.Precreated tickets allow parallel signing and submission without sacrificing unique transaction hashes.

Who is this change relevant to?

XRP holders and users

Ordinary wallet users do not need tickets. Complex or jointly signed accounts can use them to avoid blocking Sequence conflicts.

Wallets and app developers

Signing services must inventory available tickets, assign them atomically, and mark them consumed even after a tec result.

Exchanges and issuers

Exchanges and treasury systems can prepare several withdrawals in parallel but must monitor owner reserves and ticket inventories.

Node operators

Nodes order ticket transactions canonically, verify ticket ownership, and remove the object after tesSUCCESS or a tec result.

What limitations and risks remain?

  • A ticket can be used only once.
  • An account can hold at most 250 tickets at a time, and one TicketCreate transaction can create at most 250.
  • Tickets have no expiration or dedicated cancel transaction. They can be consumed, or removed through account deletion when its conditions are met.
  • TicketSequence and AccountTxnID must not appear together in a transaction.
  • The submission order of ticket transactions is not guaranteed. The canonical ledger order determines execution.
  • A tec result consumes the ticket just as tesSUCCESS does.

What fee and performance figures does the specification provide?

  • Each unused ticket requires one owner reserve.
  • TicketCreate reduces multisigning effort because one jointly signed transaction creates up to 250 tickets.
Technical details: transactions, fields, codes and invariants

Transactions

  • TicketCreate
  • transactions with TicketSequence

Ledger objects

  • Ticket (ltTICKET)
  • AccountRoot

Fields and flags

  • TicketCount
  • TicketSequence
  • Sequence = 0 when using a ticket
  • AccountTxnID is invalid with TicketSequence

API methods

  • account_objects: type ticket
  • ledger_data: type ticket
  • ledger_entry
  • account_tx

Result codes

  • tecDIR_FULL
  • tecINSUFFICIENT_RESERVE
  • temINVALID
  • tefPAST_SEQ
  • tesSUCCESS

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?

TicketBatch is enabled on the XRP Ledger. xrpscan reports Nov 18, 2021 (UTC) as its activation date and rippled 1.7.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?

AMM and Clawback: protocol progression

  1. DeletableAccountsEnabled · from rippled 1.4.0
  2. TicketBatchEnabled · from rippled 1.7.0
  3. DisallowIncomingEnabled · from rippled 1.10.0
  4. AMMEnabled · from rippled 1.12.0
  5. ClawbackEnabled · from rippled 1.12.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixInnerObjTemplateEnabled · from rippled 2.1.0
  8. fixAMMOverflowOfferEnabled · from rippled 2.1.1
  9. fixAMMv1_1Enabled · from rippled 2.2.0
  10. fixPreviousTxnIDEnabled · from rippled 2.2.0
  11. AMMClawbackEnabled · from rippled 2.3.0
  12. fixAMMv1_2Enabled · from rippled 2.3.0
  13. fixInnerObjTemplate2Enabled · from rippled 2.3.0
  14. fixFrozenLPTokenTransferEnabled · from rippled 2.4.0
  15. DeepFreezeEnabled · from rippled 2.4.0
  16. PermissionedDEXEnabled · from rippled 2.5.0
  17. fixAMMv1_3Enabled · from rippled 2.5.0
  18. PermissionDelegationDeprecated · from rippled 2.5.0
  19. fixAMMClawbackRoundingEnabled · from rippled 3.0.0
  20. SponsorOpen for voting · from xrpld 3.3.0
  21. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  22. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  23. fixCleanup3_4_0Enabled · from xrpld 3.4.0
  24. MPTokensV2In development

Which primary sources support this information?

← All XRPL amendments and XLS specifications