VTID DID Identifier


The VERTU DID method specification meets the requirements in the current DID specification published by the W3C community group. For more information about DID and DID method specifications, see Decentralized Identifiers (DIDs) v1.0


Based on the blockchain, a digital identity system that conforms to the W3C standard is established to provide users with decentralized digital identity, ensure the absolute control and absolute ownership of digital identity, and solve the problem of privacy leakage of users.

This is a draft document and will be updated.

Method Name

The name string that identifiers this DID method is:


A DID that uses this method MUST begin with the following prefix: did:vertu. Per the DID specification, this string MUST be in lowercase.

DID format

vertu-did = "did:vertu:" id-string

id-string = md5(sha256(<Base DID Document>)))

<Base DID Document>:

For example


DID Create

The process for creating DID is as follows:

  1. Generate a pair of public and private keys
  2. Generate the Base DID Document, and generate the idString based on the Base DID Document
  3. Add DID did:vertu: as the final DID identifier before idString

Sample document:

DID Read

Reading DID is the resolution of DID. The DID Resolver will return the corresponding DID Document according to DID

Sample request:

GET https://my-did.vertu.com/v1/did:vertu:3qszgXHNd4MvEccb2HrZPBPAWjvW4vPcZxKbGMAygoyqLq7DBgw3f7W

Sample response:

DID Update

Currently supported:

1.Updating Public Key Information

An example of an update request is as follows: (where signature is signed using the recovery key in the document of the previous version)

DID Delete

When you need to revoke a did, you need to send the following request: (where signature is signed with the recovery key in the document of the previous version)

Privacy and Security considerations

Privacy Considerations

· The private key that proves the DID ownership is only present on the user's device and will not be known to any third party.

· DID Document uses signature technology to prevent malicious tampering.

· All data stored in DID documents is considered public. DID documents do not contain any personal information about the user concerned.

Security considerations

vertu DID prevents forgery and falsification through hash value check.

Private keys(for signing operations) are to be held secret. In the event of a compromised key, the user is required to deactivate(revoke) any existing DID immediately.


· W3C DID Spec:https://w3c.github.io/did-core/

· W3C DID Method Registry:https://w3c-ccg.github.io/did-method-registry/

· W3C DID Resolution:https://w3c-ccg.github.io/did-resolution/