Skip to content
EnabledTier AIdentity & Oracles

DID XLS-40

W3C-compatible decentralized identifiers are anchored on the XRPL. DID is enabled on the XRP Ledger. xrpscan reports Oct 30, 2024 (UTC) as its activation date and rippled 2.0.0 as its first version.

Sources reviewed Oct 5, 2026 · English page updated Oct 5, 2026 · Phil · CryptoTuts founder

Status
Enabled
XLS
XLS-40
Enabled
Oct 30, 2024 (UTC)

What does this amendment change?

Why does this amendment exist?

An XRPL account should be able to publish a standardized decentralized identifier without a central authority controlling that identifier.

How does the mechanism work?

DIDSet creates or updates an account-linked DID object; DIDDelete removes it. An XRPL DID combines the network identifier with the AccountID or hexadecimal master public key. URI, Data, and DIDDocument can reference an external document or store small public values directly.

What changes compared with the predecessor?

BeforeAfter
An XRPL account had no native identity entry resolvable using W3C DID methodology.The account can publish a persistent DID anchor and update or delete it with its key.

Who is this change relevant to?

XRP holders and users

Using a DID is optional and does not verify a person's legal identity. Published information is public; creating or changing the ledger entry incurs transaction fees, and the entry requires an owner reserve.

Wallets and app developers

Resolvers and wallets can read the on-ledger anchor but must still verify the referenced DID document, signatures, and external endpoints themselves.

Exchanges and issuers

Institutions can associate a stable identifier with verification methods or service endpoints. This does not automatically create a KYC attestation.

Node operators

Nodes store one reserve-requiring DID object per account and validate field lengths, not the content of external documents.

What limitations and risks remain?

  • The ledger does not validate the content or W3C conformity of URI, Data, or DIDDocument.
  • Each of the three data fields is limited to 256 bytes.
  • DID content and linked public documents should not contain sensitive personal information.
  • A DID does not prove that a claimed real-world identity is correct.
  • Security depends on the associated XRPL account's key management and the availability of external content.

What fee and performance figures does the specification provide?

  • The DID object requires one owner reserve from the account.
Technical details: transactions, fields, codes and invariants

Transactions

  • DIDSet
  • DIDDelete

Ledger objects

  • DID

Fields and flags

  • DIDDocument (at most 256 bytes)
  • URI (at most 256 bytes)
  • Data (at most 256 bytes)

API methods

  • account_objects
  • ledger_entry

How does this amendment relate to others?

Every direct relationship has a type, an explanation and a primary source.

What happens next for this amendment?

DID is enabled on the XRP Ledger. xrpscan reports Oct 30, 2024 (UTC) as its activation date and rippled 2.0.0 as its first version.

These rules are already part of Mainnet. Server operators need a compatible xrpld (formerly rippled) version; ordinary wallet users do not need to enable anything manually.

Where does it sit within its amendment family?

Identity and Permissions: protocol progression

  1. DepositPreauthEnabled · from rippled 1.1.0
  2. DeletableAccountsEnabled · from rippled 1.4.0
  3. TicketBatchEnabled · from rippled 1.7.0
  4. DisallowIncomingEnabled · from rippled 1.10.0
  5. DIDEnabled · from rippled 2.0.0
  6. fixDisallowIncomingV1Enabled · from rippled 2.0.0
  7. fixEmptyDIDEnabled · from rippled 2.2.0
  8. CredentialsEnabled · from rippled 2.3.0
  9. fixInvalidTxFlagsEnabled · from rippled 2.4.0
  10. PermissionedDomainsEnabled · from rippled 2.4.0
  11. PermissionedDEXEnabled · from rippled 2.5.0
  12. PermissionDelegationDeprecated · from rippled 2.5.0
  13. SponsorOpen for voting · from xrpld 3.3.0
  14. PermissionDelegationV1_1Enabled · from xrpld 3.3.0
  15. fixCleanup3_3_0Enabled · from xrpld 3.3.0
  16. fixCleanup3_4_0Enabled · from xrpld 3.4.0

Which primary sources support this information?

← All XRPL amendments and XLS specifications