Add did:kxtid method

[energy-blockchian]

Instructions for Pull Requests

Please read these instructions thoroughly in order to ensure that your pull request is processed in a timely manner. This document contains detailed instructions for registering a DID Method. If your pull request concerns some other change to the repository, you may delete all of the text in this text box and write up a more relevant description.

There is a DID Method Registration form below that MUST be included in a DID Method Registration Request. The form includes check boxes that you are expected to fill out when you submit your request.

Once you submit your request, your pull request will be reviewed by the registry editors. Changes regarding the required criteria may be requested. If there are no objections or changes requested, your DID method will be registered after a minimum of 7 days.

DID Method Registration Process

In order to register a new DID method, you must add a JSON file to the ./methods directory.

Here is an example registration entry:

{
  // These fields are required
  "name": "example",
  "status": "registered",
  "specification": "https://w3c-ccg.github.io/did-spec/",
  // These fields are optional
  "contactName": "W3C Credentials Community Group",
  "contactEmail": "",
  "contactWebsite": "",
  "verifiableDataRegistry": "DID Specification"
}

Your Pull Request will be automatically validated, please ensure that all of the automated tests pass (no errors reported) or your submission will not be reviewed. Common reasons for failed validation includes invalidly formatted JSON files and missing mandatory fields.

----- DID METHOD REGISTRATION FORM: DELETE EVERYTHING ABOVE THIS LINE ------

DID Method Registration

As a DID method registrant, I have ensured that my DID method registration complies with the following statements:

• The DID Method specification defines the DID Method Syntax.
• The DID Method specification defines the Create, Read, Update, and Deactivate DID Method Operations.
• The DID Method specification contains a Security Considerations section.
• The DID Method specification contains a Privacy Considerations section.
• The JSON file I am submitting has passed all automated validation tests below.
• The JSON file contains a contactEmail address [OPTIONAL].
• The JSON file contains a verifiableDataRegistry entry [OPTIONAL].

[gatemezing]

The method passes the mimimum requirements.

[swcurran]

Technically, it appears that the minimum requirements for approval are met, but I found the spec to be quite incomplete. I don't know how anyone could use this to write a DID resolver or any piece of software using the DID Method.

Some issues that I found:

• What is "the national blockchain" referenced in the introduction and how does it come into the picture? There is a later line that says the public key is published on "the blockchain". How does that happen?
• The steps to generate the identifier are underspecified.
  • The first step uses the "SM2" encryption algorithm (what is it? reference?) and what is encrypted?
  • What type of public/private keys are generated? How are they encoded?
  • What is the "SM3" hash algorithm?
• The "KXTID Document Specification" seems to repeat the DID Core list of fields for a DIDDoc. It would be helpful to just point out what differs from any other DIDDoc, and how data from "the blockchain' gets inserted into the document. I'm guessing that is what is happening.,
• The CRUD DID Method operations provide no details about how they are used. Is there a server somewhere that handles the HTTP operations? Is there a defined API? Is there a central authority running the service, or is the goal to have others host servers?
• It looks like the "update" operation is allowed, but does not support key rotation. That is often a desirable feature of a DID Method. Can it be supported?

[ottomorac]

I also agree with the observations from @swcurran . Suggest to have these issues resolved and then we can review again.