Definition and scope
Decentralized Identifiers on the XRP Ledger addresses a distinct part of compliance, identity, and interoperability. Explore DID ledger objects, documents, and the difference between identifiers and verified claims.
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
The DID amendment adds DIDSet and DIDDelete transactions and a DID ledger entry containing URI, DIDDocument, and Data fields subject to size and encoding rules. It anchors identifier material to an account.
- DIDSet: verify this field, object, or component against the cited protocol documentation.
- DIDDelete: verify this field, object, or component against the cited protocol documentation.
- DIDDocument: verify this field, object, or component against the cited protocol documentation.
- URI: verify this field, object, or component against the cited protocol documentation.
- controller: verify this field, object, or component against the cited protocol documentation.
Practical example and checks
An account publishes a compact DID document or URI, relying parties retrieve and parse it under a defined DID method policy, and the controller updates or deletes stale material.
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
An identifier is not a verified identity. Trust depends on controller keys, document interpretation, credential issuers, revocation, and off-ledger evidence.
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. DID was enabled on XRPL Mainnet in feature responses from both official public servers at review time. Client and service support can still vary.
Status reviewed 2026-08-23. Amendment-dependent behavior must be rechecked against the network's live feature state before operational use.