Ticket

[Source]

A Ticket entry type represents a Ticket, which tracks an account sequence number that has been set aside for future use. You can create new tickets with a TicketCreate transaction.

(Added by the TicketBatch amendment.)

Example Ticket JSON

{
  "Account": "rEhxGqkqPPSxQ3P25J66ft5TwpzV14k2de",
  "Flags": 0,
  "LedgerEntryType": "Ticket",
  "OwnerNode": "0000000000000000",
  "PreviousTxnID": "F19AD4577212D3BEACA0F75FE1BA1644F2E854D46E8D62E9C95D18E9708CBFB1",
  "PreviousTxnLgrSeq": 4,
  "TicketSequence": 3
}

Ticket Fields

In addition to the common fields, Ticket entries have the following fields:

Name	JSON Type	Internal Type	Required?	Description
`Account`	String	AccountID	Yes	The account that owns this Ticket.
`LedgerEntryType`	String	UInt16	Yes	The value `0x0054`, mapped to the string `Ticket`, indicates that this is a Ticket entry.
`OwnerNode`	String	UInt64	Yes	A hint indicating which page of the owner directory links to this entry, in case the directory consists of multiple pages.
`PreviousTxnID`	String	Hash256	Yes	The identifying hash of the transaction that most recently modified this entry.
`PreviousTxnLgrSeq`	Number	UInt32	Yes	The index of the ledger that contains the transaction that most recently modified this entry.
`TicketSequence`	Number	UInt32	Yes	The Sequence Number this Ticket sets aside.

Ticket Reserve

Ticket entries count as one item towards the owner reserve of the account that placed the created it, as long as the entry is in the ledger. Using the ticket frees up the reserve.

Ticket Flags

There are no flags defined for Ticket entries.

Ticket ID Format

The ID of a Ticket object is the SHA-512Half of the following values, concatenated in order:

The Ticket space key (0x0054)
The AccountID of the owner of the Ticket
The TicketSequence number of the Ticket