Label: Data Retention

The XRP Ledger is composed of a series of individual ledgers, or ledger versions, which rippled keeps in its internal database. Learn about the structure and contents of these ledgers.

rippled servers store a variable amount of transaction and state history locally.

Online deletion purges outdated transaction and state history.

History sharding divides the work of keeping historical ledger data among rippled servers.

Plan system specs and tune configuration for rippled in production environments.

Configure how far back your server should store transaction history.

Use advisory deletion to delete older ledger history on a schedule rather than as new history becomes available.

Set up a server to contribute to preserving shards of historical XRP Ledger data.

Full history servers provide a record of every transaction ever to occur in the XRP Ledger, although they are expensive to run.

Learn about individual data objects that comprise the XRP Ledger's shared state.

A unique header that describes the contents of a ledger version.

All objects in a ledger's state tree have a unique ID.

XRPL.org is a community-driven site for the XRP Ledger (XRPL), an open-source, public blockchain. Get technical documentation, reference materials, and tools.

Contains links to other objects.

Get all ledger objects owned by an account.

Get the raw contents of a ledger version.

Get one element from a ledger version.

Allow online deletion of ledgers up to a specific ledger.

Request information about which history shards peers have.

Download a specific shard of ledger history.

Configure the ledger cleaner service to check for corrupted data.

Query peer servers for a specific ledger version.

Get or modify log verbosity.

Reopen the log file.

Copy data from the ledger store into the shard store.