DID Document

A DID Document is the record you get back when you resolve a DID. If a DID is like a phone number, the DID Document is the contact card behind it, except instead of a name and address, it lists public keys and service endpoints, so anyone can check a signature or find where to reach the DID's owner, with no central directory doing the lookup.

Here is a real one, live on the public testnet right now, resolvable by anyone (the exact curl is in the DID Resolution entry). This is the raw RPC response, unedited:

{
  "context": "https://www.w3.org/ns/did/v1",
  "id": "did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J",
  "controller": "did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J",
  "verification_method": [
    {
      "controller": "did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J",
      "id": "did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J#key-0",
      "publicKeyHex": "4ac407d14cab5627f69f0b3067a3cd6c340c610c3c414f367b3bdac1343c2044",
      "type": "Ed25519VerificationKey2020"
    }
  ],
  "authentication": ["did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J#key-0"],
  "assertion_method": ["did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J#key-0"],
  "key_agreement": [],
  "capability_invocation": ["did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J#key-0"],
  "capability_delegation": ["did:solidus:testnet:46Hzv2Ek4MXwj1Kenvix4tWCPr1J#key-0"],
  "service": [],
  "active": true,
  "created_ms": 1783972405492,
  "updated_ms": 1783972405492,
  "version_id": "32352473f6c8399bd3612e621269b0f8438b884854212f3b7a5acba60daac012",
  "recovery_policy": null,
  "recovery_nonce": 0
}

verification_method (DID Core's verificationMethod) lists the public key(s) attached to the DID. authentication says which key(s) can prove "I am this DID", used for login and challenge-response. assertion_method (assertionMethod in the spec) says which key(s) can sign statements, including issuing a Verifiable Credential. One honest note on shape: the raw RPC serves the chain's native snake_case field names, not DID Core's camelCase JSON-LD serialization. The structure is DID Core's; the serialization is the chain's own.

Where it comes from

The document's shape belongs to W3C DID Core, not to Solidus. Our contribution is a working, on-chain store for it: DID Documents live in the chain's state tree, created and deactivated via native transactions, and served to anyone who asks.

Solidus status

Shipped, testnet-live. Every did:solidus DID has a real, resolvable document on the running public testnet. There is no mainnet equivalent.

Proof you can run yourself: resolve one directly, the exact curl command against rpc.solidus.network is in the DID Resolution entry, and it runs with no account.