1️⃣
AV1
  • AV1 Documentation
  • Core Concepts
    • Decentralized Identifiers (DIDs)
      • did:btco
      • did:peer
      • did:key
      • did:web
    • Verifiable Credentials (VCs)
    • DIDComm
  • Libraries
    • @aviarytech/crypto
    • @aviarytech/vcs
    • @aviarytech/dids
    • @aviarytech/didcomm
  • Reference
    • AV1 Documentation
      • Libraries
        • @aviarytech/crypto
        • @aviarytech/vcs
        • @aviarytech/dids
        • @aviarytech/didcomm
      • Applications
        • Assurance Studio
        • Verifiable Ink
        • 1Keep
      • Endpoints
        • Assurance Studio
        • Verifiable Ink
        • 1Keep
Powered by GitBook
On this page
  • Technical Details
  • Conclusion
  1. Core Concepts

Decentralized Identifiers (DIDs)

PreviousCore ConceptsNextdid:btco

Last updated 1 year ago

Decentralized Identifiers (DIDs) are a unique type of identifier that can be generated and controlled by users themselves, rather than relying on a centralized registration authority. This is made possible through the use of cryptographic techniques, providing users with greater privacy and control in the digital world. In essence, DIDs shift the point of control to individuals, fostering a more user-centric digital ecosystem.

Technical Details

Properties of a DID

A DID possesses several key properties:

  1. Persistent: It can be retained for as long as necessary.

  2. Resolvable: Its metadata can be discovered through lookup operations.

  3. Cryptographically-Verifiable: Ownership and control of the DID can be proven using cryptographic methods.

  4. Decentralized: It eliminates the need for a centralized registration authority.

Structure of a DID

A typical DID appears as follows: did:example:123456789abcdefghijk

DID Methods

DID methods define specific details including:

  • The syntax of the method-specific identifier.

  • The implementation of the DID operations: CREATE, RESOLVE, UPDATE, and DEACTIVATE.

  • The security and privacy requirements.

DID Core Properties

The core properties of a DID include:

  • Identifiers: Including subject, controller, and aliases.

  • Verification Methods: Methods for verification using public keys.

  • Verification Relationships: Including authentication, assertion, key agreement, capability invocation, and capability delegation.

  • Services: Methods of communication associated with the DID.

DID Resolution

The process of resolving a DID involves a function, resolve(did, resolutionOptions), which outputs the following elements:

  • didResolutionMetadata: Includes information like content type and errors.

  • didDocument: A document that contains the DID properties.

  • didDocumentMetadata: Contains data such as creation and update timestamps, deactivation status, and version details.

Conclusion

DIDs represent a significant leap towards user-centric digital identity, providing privacy and control without requiring centralized registration authorities. They form the core component of decentralized identity systems, underpinning secure and trustful digital interactions.