> For the complete documentation index, see [llms.txt](https://docs.empe.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empe.io/develop/wallet-server/terminology-and-concepts.md).

# Terminology and Concepts

**Self‑Sovereign Identity (SSI)** User‑centric identity where control of identifiers and credentials belongs to the subject.

**Decentralized Identifier (DID)** A globally unique identifier. Wallet Server supports:

* `did:empe` (mainnet)
* `did:empe:testnet` (testnet)
* `did:web` (hosted over HTTPS)

**DID Document** The document resolved from a DID containing verification methods, services, and controller info.

**Verifiable Credential (VC)** A cryptographically signed credential asserting claims about a subject.

**Claim Flow** The process a holder uses to claim a credential from an issuer, typically initiated by scanning an issuer QR.

**Presentation Flow** The process a holder uses to present one or more credentials to a verifier, typically initiated by scanning a verifier QR.

**did:web** A DID method where the DID document is hosted at a well‑known HTTPS path on a domain you control.

**Tenant Scoping** Wallet data is partitioned by the JWT `sub`. Each request is evaluated in the context of the authenticated user.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.empe.io/develop/wallet-server/terminology-and-concepts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.