Decentralized Identifiers (DIDs)

View Categories

Decentralized Identifiers (DIDs)

Overview #

Decentralized Identifiers (DIDs) are a core component of Blerify’s architecture, enabling secure, verifiable, and privacy-respecting interactions. 

A DID is a globally unique identifier that is created, controlled, and managed by the subject it identifies, without reliance on centralized authorities.

In Blerify, DIDs are used to issue, verify, and manage Verifiable Credentials. These DIDs comply with global standards such as the W3C DID Core Specification.

Structure of a DID #

A DID in Blerify follows the generic format defined by the W3C:

did:<method>:<unique-identifier>

Breakdown: #

  1. did: The fixed prefix for all DIDs.

  2. method: Specifies the DID method, such as lacchain for our implementation.

  3. unique-identifier: A unique string generated for each entity.

Example DID: #

did:lacchain:123456789abcdef

Blerify DID Method #

Blerify DID Method #

The lacchain method leverages the LACChain blockchain network to ensure high performance, resilience, and compliance with regional regulations. This method ensures:

  • Decentralization: DIDs are generated and resolved without centralized control.

  • Interoperability: Fully compatible with Verifiable Credentials and other DID-enabled systems.

  • Security: Enhanced with cryptography and resistance to quantum attacks.

DID Method Operations #

  1. Create: Generate a new DID using the LACChain infrastructure.

  2. Read: Resolve a DID to its associated DID Document.

  3. Update: Modify the DID Document (e.g., add a new verification method).

  4. Deactivate: Revoke or retire a DID.

DID Document #

The DID Document is a JSON-LD file that contains all the metadata and cryptographic material associated with a DID. A typical DID Document includes:

  1. id: The DID of the subject.

  2. @context: Specifies the context for interpreting the document.

  3. authentication: Lists public keys used to authenticate the DID.

  4. verificationMethod: Cryptographic methods for verifying the subject’s identity.

  5. service: Describes services related to the DID, such as credential issuance endpoints.

Example DID Document: #

{
  "@context": "https://www.w3.org/ns/did/v1",
  "id": "did:lacchain:123456789abcdef",
  "verificationMethod": [
    {
      "id": "did:lacchain:123456789abcdef#keys-1",
      "type": "EcdsaSecp256k1VerificationKey2019",
      "controller": "did:lacchain:123456789abcdef",
      "publicKeyHex": "02a3f2...f1b3e9"
    }
  ],
  "authentication": [
    "did:lacchain:123456789abcdef#keys-1"
  ],
  "service": [
    {
      "id": "did:lacchain:123456789abcdef#vc-issuer",
      "type": "VerifiableCredentialService",
      "serviceEndpoint": "https://api.blerify.com/vc"
    }
  ]
}

DID Resolution #

Blerify provides an API for resolving DIDs to their corresponding DID Documents. The resolution process involves:

  1. Inputting a DID.

  2. Querying the LACChain network.

  3. Returning the associated DID Document.

API Endpoint: #

  • URL: https://api.blerify.com/did/resolve

  • Method: GET

  • Parameters:

    • did: The DID to be resolved.

Sample Request: #

GET /did/resolve?did=did:lacchain:123456789abcdef

Sample Response: #

{
  "@context": "https://www.w3.org/ns/did/v1",
  "id": "did:lacchain:123456789abcdef",
  "verificationMethod": [...],
  "authentication": [...],
  "service": [...]
}

  #

Use Cases #

  1. Credential Issuance: Organizations issue credentials linked to a DID.

  2. Verification: Verifiers authenticate users via their DIDs and verify associated credentials.

  3. Interoperability: Enable seamless interaction across platforms supporting W3C DID standards.

Security Features #

  • Key Rotation: Support for updating public keys in the DID Document.

  • Quantum-Resistance: Integration of quantum-resistant algorithms in cryptographic operations.

  • Privacy: No unnecessary information stored on-chain; data resides in the DID Document.