DID - is a new type that enables decentralized identification.
Conventional identity management systems are based on centralized authorities such as corporate directory services, certificate authorities, or domain name registries. From the standpoint of cryptographic trust verification, each of these centralized authorities serves as its own root of trust. To make identity management work across these systems requires implementing federated identity management.
The emergence of distributed ledger technology (DLT) and blockchain technology provides the opportunity for fully decentralized identity management. In a decentralized identity system, entities (that is, discrete identifiable units such as, but not limited to, people, organizations, and things) are free to use any shared root of trust. Globally distributed ledgers, decentralized P2P networks, or other systems with similar capabilities, provide the means for managing a root of trust without introducing a centralized authority or a single point of failure. In combination, DLTs and decentralized identity management systems enable any entity to create and manage their own identifiers on any number of distributed, independent roots of trust.
See the full details on DID in the official documentation.
DID Document is created from ECHO protocol object. We have added 3 types of operations for DID Document: create, update, delete.
Currently, ECHO DID supports 3 types:
All created keys will be verified for compliance with
Base58 encoding and must be derived from
The method specific identifier is composed of network type and id of object at ECHO network.
Network type can be '0' for mainnet, '1' for testnet and '2' for devnet. Next goes triplet of numbers devided by points: id of object at ECHO network.
Note: if it's not one of this networks, value will be '255'.
echo-did = "did:echo:" echo-specific-idstringecho-specific-idstring = [ echo-network ":" ] echo-object-idecho-network = "0" / "1" / "2" / "255"echo-object-id = 1*DIGIT "." 1*DIGIT "." 1*DIGIT