This repository contains a list of known DID Extensions that are tracked by the W3C Decentralized Identifier Working Group (DID WG) for the purpose of enhancing DID ecosystem interoperability. There might be extensions to DIDs other than the ones listed here; this is not meant to be an exhaustive or centralized list of extensions.
An Editor's Draft of this repository is available at https://w3c.github.io/did-extensions/.
In order to register a new DID method, you must add a JSON file to the ./methods directory and open a pull request to add the file to this repository.
Here is an example registration entry:
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. There will be a checklist that you are expected to complete and attest to its accuracy.
In addition to the automated validation, an AI-based preliminary
specification review runs automatically on your pull request. It fetches the
specification you link to and checks it against the
registration checklist (DID Method syntax,
CRUD operations, Security and Privacy Considerations, and so on), then posts an
advisory pass/fail report as a comment on your pull request. This review is a
preliminary aid for the registry editors and does not replace their review; if
it reports a failing required item, address it and push an update to re-run the
check. Editors can re-run the review at any time by commenting /ai-review on
the pull 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 at least two reviews by registry maintainers listed in the CODEOWNERS file, and no objections or changes requested, your DID method will be registered after a minimum of 7 days and a maximum of 30 days.
Use the standard fork, branch, and pull request workflow to propose changes to the registry. Please make branch names informative—by including the issue or bug number for example.
Editorial changes that improve the readability of the registry or correct spelling or grammatical mistakes are welcome.
Non-editorial changes MUST go through a review and approval process that is detailed in the registry.
Please read CONTRIBUTING.md, about licensing contributions.
W3C functions under a code of conduct.
{ // 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" }