Definition and scope
What Is the xrp-ledger.toml File? addresses a distinct part of compliance, identity, and interoperability. Publish machine-readable information about accounts, validators, tokens, and organizational identity.
XRPL includes tools for controlled deposits, issuer compliance, public identity, and cross-network systems. Several features in this category are amendment-dependent or evolving, so every eventual article must verify current Mainnet status and distinguish protocol capability from a particular service's legal obligations. Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
How it works
xrp-ledger.toml is a machine-readable HTTPS document commonly hosted at /.well-known/xrp-ledger.toml. It can list accounts, validators, currencies, contacts, and metadata associated with a domain.
- xrp-ledger.toml: verify this field, object, or component against the cited protocol documentation.
- .well-known: verify this field, object, or component against the cited protocol documentation.
- ACCOUNTS: verify this field, object, or component against the cited protocol documentation.
- VALIDATORS: verify this field, object, or component against the cited protocol documentation.
- CURRENCIES: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
Publish the file with correct TOML syntax, set the matching hex Domain on relevant accounts, validate both directions, and keep operational contacts and token identifiers current.
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.
Open the related live demo or evidence lab →Limits, risks, and common confusion
The file is self-published identity information, not an XRPL Foundation endorsement, license, audit, or proof of reserves. Consumers should verify HTTPS, domain control, and on-ledger matches.
Protocol controls can support a policy but do not establish identity, trustworthiness, regulatory compliance, or legal permission by themselves.
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.