01What
Creates or updates the decentralized identifier (DID) attached to your account — a self-controlled identity record following the W3C standard, stored on or linked from the ledger.
02Why you'd use it
A DID lets apps and partners resolve who or what your account represents — a person, a company, a device — without relying on any central registry. It is the foundation for verifiable credentials.
03How
- 1Prepare your DID document — the JSON record describing your identity and its verification keys (the AI builder can generate a minimal one).
- 2For anything beyond tiny documents, host it off-chain (like IPFS) and put the link in URI.
- 3Or paste a very small document directly into DID Document.
- 4Optionally add public Attestation Data.
- 5Submit and confirm tesSUCCESS. Your DID is now resolvable as did:xrpl:...
Watch out
- Everything you store here is public forever — identity pointers only, never personal data like names or documents.
- The DID object locks 0.2 XRP of owner reserve until deleted.
- You must set at least one of the fields — an empty DIDSet has nothing to store and is rejected.
- If the URI points to ordinary web hosting that later dies, your DID resolves to nothing — prefer content-addressed storage like IPFS.
For example
A logistics company attaches a DID to its operational account, pointing to a document listing its official signing keys. Partners resolving the DID can now verify that a signed shipping manifest really came from the company.