Indexed XRP LedgerBlockchain Data

The XRP Ledger has closed ledgers continuously since 2012, without mining and without staking. Validators agree on each version through the XRP Ledger Consensus Protocol, with every participant trusting a published list of validators it has chosen, and a new ledger closes every three to five seconds. All 100 billion XRP were created at the start, none can be issued since, and transaction fees are destroyed rather than paid to anyone, so supply only falls. XRP divides into a million drops. An account is an object in the ledger and must hold a reserve of XRP to exist, so addresses here are created deliberately rather than spun up and abandoned. There is no general-purpose contract VM. Transactions are typed instead: payments, offers on the ledger’s own order book, trust lines, escrows and checks. Issued assets are held in trust lines, a two-sided balance between issuer and holder rather than an entry in a token contract. Protocol changes arrive as amendments that activate only after sustained validator support, and two of them shape recent data: XLS-20 brought native NFTs in 2023 and an automated market maker followed in 2024.

SonarX indexes closed ledgers, typed transactions and their metadata, account objects, trust lines, order-book offers and the balances derived from all of it. Everything is normalized into the model SonarX uses across every network it covers, so an XRP Ledger question and a Stellar question can be answered in the same query language even though the two ledgers record assets differently.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery is enabled on request. Point-in-time balance tables are available for XRP Ledger.

Each close publishes a complete state tree, so the meaningful records are the differences between consecutive ledgers together with the metadata every transaction carries about the objects it touched. Balances take two forms and both have to be handled: XRP sits on the account object and is partly locked by reserves, while issued assets sit in trust lines whose balance is defined against a particular issuer, so a spendable position is a calculation rather than a field. Amendments are the third consideration, because they change transaction and object shapes partway through the history, and decoding has to be version-aware rather than assume today’s format applies to 2015.

The requests here come from payments and treasury teams. Corridor analysis is the first: following value between issuers, exchanges and end accounts to see where flow actually goes, which needs payments and trust-line changes together rather than transfer counts. Issuer monitoring is the second, since every issued asset is somebody’s liability and its outstanding balance is the sum of the trust lines that hold it. Reconciliation is the third, restating account positions as at a ledger with reserves netted out, which auditors ask for in exactly those terms. Market-structure work on the native order book is the fourth, now that pooled liquidity sits beside it. Token analytics covers the issuance side across chains, and Tempo comes up whenever a team is comparing payment rails built on different execution models.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. XRP Ledger history is available now as a share or a file delivery, and streaming is provisioned on request. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.