Anatomy of an XRP Ledger Address

Definition and scope

Anatomy of an XRP Ledger Address addresses a distinct part of xrp and ledger fundamentals. Understand classic addresses, their public role, and the checks that help detect mistyped destinations.

This collection establishes the language needed to evaluate every other XRP Ledger topic. It separates the asset from the network, explains the identifiers visible in explorers, and shows how individual transactions fit into an ordered ledger history. Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.

How it works

A classic XRPL address is a Base58Check-encoded account identifier, usually beginning with r. It identifies a public account location; authorization comes from cryptographic keys, not from the visible address itself.

• classic address: verify this field, object, or component against the cited protocol documentation.
• Base58Check: verify this field, object, or component against the cited protocol documentation.
• account ID: verify this field, object, or component against the cited protocol documentation.
• checksum: verify this field, object, or component against the cited protocol documentation.

Practical example and checks

Before a transfer, software can decode and checksum the address, confirm the intended network and asset, and separately capture any destination tag required by the recipient's off-ledger accounting system.

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

An address is not a secret and does not prove who controls it. A syntactically valid address can still be the wrong recipient, inactive, or incompatible with a service workflow.

Names and identifiers describe protocol state; they do not establish ownership, identity, market value, or an affiliation with Ripple.

Current network status

Enabled on XRPL Mainnet. The underlying protocol capability is available on XRPL Mainnet. Individual services can still impose additional rules, limits, or trust assumptions.

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