This page gives you one model of identity on IXO: what a DID is, who controls it, how a claim differs from a verifiable credential, and where each record is kept. Read it before you work with the identity, claims or credentials APIs and SDKs.
The same ideas appear on the platform pages for Emerging digital identifiers and credential issuance. This page puts them in one place.
IXO follows the W3C work on decentralized identifiers and verifiable credentials:
Decentralized Identifiers (DIDs) v1.0 and the
Verifiable Credentials Data Model. On-chain and interchain
specifics use the did:ixo: namespace and the protocol modules documented under
IXO Protocol.
Terms
| Term | Meaning |
|---|---|
| Decentralized Identifier (DID) | A stable, resolvable identifier for a domain or an account, for example did:ixo:…. It names a subject without needing one central account system. |
| DID document | Metadata bound to a DID: verification methods, controllers, services, and links used for authentication and discovery. |
| Controller | The party (a person, an organisation or an automated process) allowed to update the DID document or act for that identifier, within the rules of the protocol and the domain. |
| Subject | What a statement is about. In a verifiable credential, the credential subject is identified by a DID, often the holder's DID. |
| Claim | A structured statement, usually about a domain, that can be evaluated, disputed or accepted against a protocol or rubric. A claim carries or references evidence. A signed claim shows who said what. It is not proof that the statement is true. |
| Verifiable credential (VC) | A tamper-evident bundle of claims about a subject, signed by its issuer. A verifier can rely on it without trusting only the holder's copy. Status and revocation may be checked against registry or service endpoints. |
| Issuer | The party that signs and issues the VC once the validation rules are met. |
| Holder | The party that presents the VC, often the subject. |
| Verifier | The party that checks signatures, issuer authority, schema and status before it trusts the content. |
In credentials, a verifier is the party that checks a credential. On asks.world the same word names a decision oracle. See the Glossary.
From identity to credential
- Register an identity. Create or obtain a DID and a domain record, so the domain exists on IXO. See digital twins and domain registration.
- Submit a claim. State something about that domain, with evidence and context. See claims.
- Validate or evaluate. People, services or agentic oracles check the claim against the programme's rules. Outcomes may be recorded on chain or in linked services.
- Issue a VC. After validation, an issuer may bind selected statements into a verifiable credential whose subject is the holder's DID. See credential issuance.
- Verify or revoke. Verifiers check proofs and status. Issuers or governance may revoke or supersede a credential when its state changes.
How the pieces relate
| Store | What it holds |
|---|---|
| Registry and chain | Pointers and state for domains, the claims lifecycle and credential status, depending on the deployment. See registry and IXO Protocol. |
| Matrix | Optional encrypted rooms and events, for evidence or payloads that must not be on chain. See IXO Matrix. |
When you build on it
- Match each interface to its credentials and base URL with the Authentication matrix and Networks and endpoints. The interfaces are listed in the Choose an IXO API, and Choose how to authenticate to an IXO API walks through the choice.
- For TypeScript patterns (client setup, entities, claims), start with Developer workflows and Implementation examples.
- To issue, hold, share and revoke credentials for people with SD-JWT VC, OpenID4VCI and OpenID4VP, use IXO Credentials.