How it operates
XRP Ledger groups transactions into a sequence of ledger versions. Each validated ledger records a shared, agreed state, including account balances, objects and transaction results.
- Data model
- Account-based ledger
- Native unit
- XRP
- Network fee
- Drops (1 XRP = 1,000,000 drops)
- Address format
- Classic addresses generally begin with r
- Programmability
- Built-in transaction types (payments, DEX, AMM, escrow)
- Supply
- 100 billion created at launch; fees are destroyed
What a record contains
Core protocol fields describe the contents, ordering and execution of a transaction.
TransactionTypeThe kind of transaction, such as Payment or OfferCreate.AccountThe sending account; it signs the transaction and pays the fee.SequencePer-account counter that orders transactions and prevents replay.FeeTransaction cost in drops; it is destroyed, not paid to validators.LastLedgerSequenceHighest ledger index the transaction may appear in before it expires.DestinationTagOptional 32-bit number that tells a shared receiving account, such as an exchange, which customer a payment is for.
A ledger becomes validated when the network reaches consensus; this is different from accumulating proof-of-work confirmations.