# Introduction

Decentralized Identifiers (DIDs) form the foundation of a verifiable, decentralized digital identity, creating a new paradigm for identity management known as self-sovereign identity (SSI). This approach puts individuals in control of their personal data and how it's used across various services and locations.

MyID aims to establish a cross-chain identity protocol within Web 3.0. The objective is to aggregate identities linked to diverse blockchain and off-chain accounts, thereby representing the owner's credibility and reputation.

MYID allows users to aggregate identities from different chains. It introduces unique mechanisms of identity matching and staking. The former involves a blind matchmaking process with randomly selected anonymous identities. The matched DID is then offered to the buyer in exchange for $MYID tokens, MYID Network's native currency.<br>

<figure><img src="https://lh5.googleusercontent.com/Do6RaGR4PsZde-e7JzNmMw-FBHLMwDvcFHO8tdWCFE3thec2pAq-35adj9M4p4RqupZrh0Ha3oY7jynesIXwTS0jsVMZQ29beH1Nnig-ViHNkdor1NhHj-gWx3v6Sn1yrb3vku10FkrrC7WoLwWmHWw" alt=""><figcaption><p>Ecosystem</p></figcaption></figure>

Identity Staking refers to the process whereby an identity owner uploads a snapshot of their identity document and DID to the blockchain's identity pool, and grants read permissions to the validator node. In doing so, they qualify for staking and matching rewards in subsequent blocks. The identity document is encrypted and stored in a decentralized database, such as IPFS or an on-chain key-value store, while the DID is stored on the chain.

By coupling identity staking with identity matching, we establish a fundamental economic model for the identity-based network that operates without selling user data. This model benefits not only identity stakers and matching buyers, but also DApps connected to MYID which receive match fees as identity contributors. This strategy allows MYID to incentivize greater participation in the future of Web3.


---

# 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://myid-1.gitbook.io/web3/introduction.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.