Skip to content
DID resolver for HTTPS domains
Branch: develop
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.

title index category type source
Web DID Resolver

Web DID Resolver

This library is intended to use domains accessed through https as Decentralized Identifiers and retrieve an associated DID Document

It supports the proposed Decentralized Identifiers spec from the W3C Credentials Community Group.

It requires the did-resolver library, which is the primary interface for resolving DIDs.

DID method

To encode a DID for an HTTPS domain, simply prepend did:web: to domain name.

eg: ->

DID Document

The DID resolver takes the domain and forms a well-known URI to access the DID Document.

For a did, the resolver will attempt to access the document at

A minimal DID Document might contain the following information:

  '@context': '',
  id: '',
  publicKey: [{
       id: '',
       type: 'Secp256k1VerificationKey2018',
       owner: '',
       ethereumAddress: '0xb9c5714089478a327f09197987f16f9e5d936e8a'}],
  authentication: [{
       type: 'Secp256k1SignatureAuthentication2018',
       publicKey: ''}]

Note this uses the Secp256k1VerificationKey2018 type and an ethereumAddress instead of a publicKeyHex, meaning that this DID is owned by an entity that controls the private key associated with that address.

Resolving a DID document

The resolver presents a simple resolver() function that returns a ES6 Promise returning the DID document.

import { Resolver } from 'did-resolver'
import getResolver from 'web-did-resolver'

const webResolver = getResolver()
const didResolver = new Resolver(webResolver)
didResolver.resolve('').then(doc => console.log)

// You can also use ES7 async/await syntax
const doc = await didResolver.resolve('')
You can’t perform that action at this time.