Concept of Identity Hub and Relay Node

[Vishwas1]

DIDs are linked to DID Documents, a metadata file that contains two primary data elements:

1. Cryptographic material the DID owner can use to prove control over the associated DID (i.e. public keys and digital signatures)
2. Routing endpoints for locations where one may be able to contact or exchange data with the DID owner (e.g. Identity Hub personal data storage and relay nodes)

Identity Hub personal data storage and relay nodes

Most digital activities between people, organizations, devices, and other entities require the exchange of messages and data. For entities to exchange messages and data for credential, app, or service flows, they need an interface through which to store, discover, and fetch data related to the flows and experiences they are participating in.

Identity Hubs are a data storage and message relay mechanism entities can use to locate public or permissioned private data related to a given DID.

Identity Hubs are a mesh-like datastore construction that enable an entity to operate multiple instances that sync to the same state across one another.

This enables the owning entity to secure, manage, and transact their data with others without reliance on location or provider-specific infrastructure, interfaces, or routing mechanisms