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
  • Advantages
  • Disadvantages
  1. Core Concepts
  2. Decentralized Identifiers (DIDs)

did:web

Previousdid:keyNextVerifiable Credentials (VCs)

Last updated 1 year ago

Specification:

The did:web method allows domain name owners to express Decentralized Identifiers (DIDs) and DID Documents in a manner compatible with the existing web architecture. It directly derives DIDs from domain names, using standard HTTP protocols for resolution.

Advantages

  • Web-Native: As it's designed to be compatible with the existing web architecture, the did:web method is easier to use and understand for developers already accustomed to web technologies.

  • Interoperability: This method works seamlessly with existing web infrastructure, ensuring smooth integration and operation.

  • Non-Blockchain Based: The did:web method does not rely on a blockchain, thus it circumvents potential scalability issues and transaction costs that blockchain-based systems may encounter.

Disadvantages

  • Centralization: The did:web method's reliance on domain names introduces a degree of centralization into its operation. This is because domain names are typically managed by centralized entities, which somewhat contradicts the decentralized ethos of DIDs.

https://w3c-ccg.github.io/did-method-web/