Why XRP Ledger history begins at ledger 32,570

The early header gap is real

The earliest fully preserved ledger in the public XRPL history is ledger 32,570, dated January 1, 2013. The preceding early ledger headers are missing. This is different from a modern public server retaining only part of the available history.

In an archived 2013 Ripple forum post, David Schwartz described a software bug shared by the servers running at the time. He said transaction data was saved and that he believed the ledger nodes were saved, while the headers were not. His attempt to reconstruct the headers stopped at ledger 32,569.

Why a header matters

A ledger is more than a list of payments. It contains a header and authenticated structures describing account state and transactions. The header connects the ledger’s identity, sequence and other commitments. Keeping some constituent data is not the same as preserving a fully verifiable sequence of ledger snapshots.

This distinction explains why “all early transactions were erased” overstates the archived explanation, while “the earliest history is fully reconstructable” also goes too far. The missing headers limit what can be checked ledger by ledger about the early period.

Separate launch, preserved history and explanation

The ledger began operating in 2012. January 1, 2013 marks the date of the first fully preserved ledger, not the date when XRP was first created. The archived September 2013 forum discussion explains the storage and reconstruction problem.

A small missing fraction of today’s ledger count does not make the gap disappear. Its historical significance comes from which period is affected, not simply from its percentage of the current count. Likewise, the gap alone is not evidence that the current consensus process has failed.

A node’s history window is another question

XRPL servers can keep different history ranges. A request for an old transaction can fail because the server does not store that period, even when another history server has it. Check the server’s complete_ledgers range and use a suitable history service before concluding that a transaction never existed.

When checking ledger 32,570, request that sequence from a server with the relevant history, inspect whether it is validated, and retain its hash and close time. A recent-history node may be perfectly usable for current balances while unable to answer that old request.

What this means for a holder’s records

The early gap does not recreate your exchange purchases or replace recordkeeping for later activity. Modern transaction history can help reconcile movements, but an exchange’s internal trades and the USD price you paid may never appear on-chain.

Avoid absolute promises that every public node can return every transaction since 2013. Keep independent copies of the exchange records, wallet addresses, hashes, and valuation evidence you need. A missing explorer result is a reason to investigate the data source.

Keep exploring