Online Deletion and Advisory Deletion Explained

Definition and scope

Online Deletion and Advisory Deletion Explained addresses a distinct part of server operations and security. Control local history retention while preserving enough data for the server's role.

Production XRPL infrastructure requires deliberate capacity, network, access, update, and recovery decisions. This collection turns the official server guidance into practical operating concepts without publishing secrets or pretending one configuration fits every workload. Infrastructure guidance is a baseline, not a substitute for threat modeling, release-specific documentation, monitoring, and tested recovery.

How it works

Online deletion limits locally retained history while the server continues running; advisory deletion lets an external process decide when old ledgers may be removed. Configuration balances storage growth with query requirements.

• online_delete: verify this field, object, or component against the cited protocol documentation.
• advisory_delete: verify this field, object, or component against the cited protocol documentation.
• ledger history: verify this field, object, or component against the cited protocol documentation.
• node database: verify this field, object, or component against the cited protocol documentation.

Practical example and checks

Choose a retention window larger than operational reconciliation needs, test historical API behavior, monitor disk growth, and document which upstream source supplies older history.

For production use, preserve the exact signed or queried data, record the network and validated ledger reference, and compare the result with the current primary documentation before changing off-ledger state.

Limits, risks, and common confusion

Deleting local history does not delete the public ledger, but it can break local queries, audits, and gap recovery. Retention changes should be backed by explicit application requirements.

Infrastructure guidance is a baseline, not a substitute for threat modeling, release-specific documentation, monitoring, and tested recovery.

Current network status

Network-independent guidance. This guide explains an operational or representational concept. Confirm live server values and service-specific behavior before relying on it in production.

Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.