VTID DID Identifier

About

The VTID 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

Abstract

VTID DID (The method specification meets the requirements of the DID specification currently published by the W3C community group. For more information about DID and DID method specifications, see DID Getting Started and DID Specifications

VTID is designed to protect the privacy of the sovereign identity and provide a unique identification of individuals, organizations, committed to get through the mobile web3.0 ecology

DID Method Name

The namestring that shall identify this DID method is: vtid.

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

vtid did format

vtid-did = "did:vtid:" id-string

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

<Base DID Document>:

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:vtid: 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:vtid: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 VTID DID method never exposes the private key. The user can however use and display the DID's private key locally.

In VTID system, all users' private data is stored in local area. Only the hash value or strings generated by crypt algorithms of the data are public on-chain, the attackers cannot derive the private data with the hash value or strings.

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

Security considerations

Record data in VTID is encrypted and signed using the private key which corresponds to the public key in the DID. This ensures that no message insertion or modification is possible and authenticity of the DID Documents is ensured. Only compromised private key is a threat to the integrity and authenticity of the DID.

VTID DID prevents forgery and tampering through hash value checking.

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.