decentralized-id.github.io/_posts/web-standards/w3c/working-groups/did-wg/2020-01-10-decentralized-identifier-did.md
2020-12-01 00:05:03 -05:00

9.2 KiB
Raw Blame History

title description excerpt categories tags permalink canonical_url redirect_from last_modified_at
(DID) the Decentralized Identifier Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) that the controller of the DID decides that it identifies. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. Specifically, while other parties might be used to help enable the discovery of information related to a DID, the design enables the controller of a DID to prove control over it without requiring permission from any other party. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject.
Web Standards
W3C
Credentials Community Group
DID
BTCR
Blockstack
ERC725
IPID
lifeID
Dominode
Ontology
Ockam
JLinc
ION
Jolocom
Veres One
XDI
uPort
Ethereum
Bitcoin
IBM
Microsoft
Digital Bazaar
Consensys
Evernym
Hyland Credentials
BCGov
Ocean Protocol
Alastria
InfoWallet
ICON
Vivvo
Sovrin Foundation
Consent
Peer DID
web-standards/w3c/wg/did/decentralized-identifier/ https://decentralized-id.com/web-standards/w3c/wg/did/decentralized-identifier/
web-standards/w3c/did-wg/decentralized-identifier/
specs-standards/decentralized-identifier-did/
web-standards/decentralized-identifier-did/
adoption/
2020-11-23

  • Decentralized Identifiers (DIDs) v1.0

    Decentralized identifiers (DIDs) are a new type of identifier that enables verifiable, decentralized digital identity. A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.) that the controller of the DID decides that it identifies. In contrast to typical, federated identifiers, DIDs have been designed so that they may be decoupled from centralized registries, identity providers, and certificate authorities. Specifically, while other parties might be used to help enable the discovery of information related to a DID, the design enables the controller of a DID to prove control over it without requiring permission from any other party. DIDs are URIs that associate a DID subject with a DID document allowing trustable interactions associated with that subject.

  • DID Whitepaper

    A DID architecture should focus on the set of components that Mr. Gupta refers to as "the minimum required for people to be able to do business (or other critical functions) together".

    A Decentralized Identifier (DID) Registry and Discovery Service

    This "minimum required" is defined by a union of the proposed requirements identified by the W3C Credential Community Group, the XDI.org Registry Working Group, and the Rebooting the Web of Trust group. It consists of three functions that can be addressed by a combination of blockchain and DHT technology:

    • A DID registration function
    • A discovery function that enables looking up a registered DID in the blockchain
    • A master key recovery function
  • A Universally Unique IDentifier (UUID) URN Namespace <-DID's modeled after
  • Understanding Decentralized IDs (DIDs)
  • DID Primer [ϟ]
  • Decentralized IDentifers (DIDs)
  • Requirements for DIDs
  • DIDs in DPKI
  • What is a DID?
  • The Path from an id (DID) to a Real-Life Something

1A/ DID 101 Decentralized Identifiers & how they are the key to interoperable self-sovereign ID

DID Method Registry

Peer DID Method Spec