# Self-Sovereign Identity (SSI)

The InterLink ID architecture follows the principles of **Self-Sovereign Identity (SSI)** - empowering each user to be the sole owner and controller of their digital identity. In this model, credentials (such as age, nationality, or verification status) are issued by trusted entities or systems and are stored securely within the user’s InterLink ID.

These credentials are never held by a central server. Instead, they remain encrypted and under the user’s control, often stored locally or via decentralized infrastructure. When needed, users can generate **verifiable proofs,** such as **zero-knowledge attestations,** to present only the required information (e.g. “Over 18”) to any verifier, without revealing full personal data.

## Core Components of InterLink ID’s SSI Model

<figure><img src="/files/SlJfS3cXKAbt6JIKT8PC" alt=""><figcaption><p>InterLink ID's SSI Model</p></figcaption></figure>

### 1. Issuer - Credential Provider

Entities that issue verifiable credentials to users. These credentials are digitally signed and can later be used to prove facts without revealing unnecessary personal information.

Examples:

* Passport Department → Issues age, nationality, legal identity.
* Crypto Wallet Platform → Issues wallet ownership or transaction activity.
* Bank → Issues financial trust scores or fiat-KYC verification.

### 2. Holder - User & Identity Owner

The individual who receives and controls credentials. All credentials are encrypted and stored in the user’s InterLink ID wallet, not on any centralized server.

Key Abilities:

* Store credentials securely.
* Control who sees what.
* Generate selective disclosures (e.g., “Over 18” without sharing birthdate).
* Generate zero-knowledge proofs to prove facts without revealing raw data.

### 3. Verifier - Credential Consumer

Any system, service, or platform that requests and validates credential proofs from a holder to make access, compliance, or governance decisions.

Examples:

* Decentralized Applications → Validate user uniqueness, reputation.
* Payment Infrastructure → Require identity proof for fraud protection or regulatory compliance.
* Web3 Services → Assess identity-based access for governance, lending, or airdrop participation.

## Why This Matters

Traditional KYC systems store your data on central servers. InterLink ID flips that model:

* You own your credentials.
* You choose what to share, when, and with whom.
* Your identity becomes portable across all of Web3 - with privacy intact.


---

# Agent Instructions: 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:

```
GET https://whitepaper.interlinklabs.ai/interlink-network/interlink-id/core-principles/self-sovereign-identity-ssi.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.