Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/decentralized-identity/trustdidweb
Trust DID Web (did:tdw) DID Method is now "did:webvh" at http://identity.foundation/didwebvh/
https://github.com/decentralized-identity/trustdidweb
citz digital-trust ditp dts trust-over-ip verifiable-credentials verifiable-organizations-network von wg-id
Last synced: 15 days ago
JSON representation
Trust DID Web (did:tdw) DID Method is now "did:webvh" at http://identity.foundation/didwebvh/
- Host: GitHub
- URL: https://github.com/decentralized-identity/trustdidweb
- Owner: decentralized-identity
- License: apache-2.0
- Created: 2024-12-03T22:55:28.000Z (about 1 month ago)
- Default Branch: main
- Last Pushed: 2024-12-03T23:25:07.000Z (about 1 month ago)
- Last Synced: 2024-12-23T23:03:02.001Z (19 days ago)
- Homepage:
- Size: 44.9 KB
- Stars: 0
- Watchers: 4
- Forks: 1
- Open Issues: 0
Awesome Lists containing this project
README
# Trust DID Web - A DID Method
The spec repository for did:tdw -- Trust DID Web DID method.
Read the spec: [https://identity.foundation/trustdidweb](https://identity.foundation/trustdidweb)
Proof of concept implementations available:
- Typescript: [https://github.com/bcgov/trustdidweb-ts](https://github.com/bcgov/trustdidweb-ts)
- Python: [https://github.com/bcgov/trustdidweb-py](https://github.com/bcgov/trustdidweb-py)
- Go: [https://github.com/nuts-foundation/trustdidweb-go](https://github.com/nuts-foundation/trustdidweb-go)## Abstract
The `did:tdw` (Trust DID Web) method is an enhancement to the
`did:web` protocol, providing a complementary web-based DID method that addresses limitations
of `did:web`. It's features include the following.- Ongoing publishing of all DID Document (DIDDoc) versions for a DID instead of,
or alongside a `did:web` DID/DIDDoc.
- Uses the same DID-to-HTTPS transformation as `did:web`.
- Provides resolvers the full history of the DID using a verifiable chain of
updates to the DIDDoc from genesis to deactivation.
- A self-certifying identifier (SCID) for the DID that is globally
unique and derived from the initial DIDDoc that enables DID portability, such
as moving the DIDs web location (and so the DID string itself) while retaining
the DID's history.
- DIDDoc updates include a proof signed by the DID Controller(s) *authorized* to
update the DID.
- An optional mechanism for publishing "pre-rotation" keys to prevent loss of
control of the DID in cases where an active private key is compromised.
- An optional mechanism for having collaborating "witnesses"
that approve updates to the DID by the DID Controller before publication.
- DID URL path handling that defaults (but can be overridden) to automatically
resolving `/path/to/file` by using a comparable DID-to-HTTPS translation
as for the DIDDoc.
- A DID URL path `/whois` that defaults to automatically returning (if
published by the DID controller) a Verifiable Presentation containing
Verifiable Credentials with the DID as the `credentialSubject`,
signed by the DID.Combined, the additional features enable greater trust and security without
compromising the simplicity of `did:web`. The incorporation of the DID Core
compatible "/whois" path, drawing inspiration from the traditional WHOIS
protocol, offers an easy to use, decentralized, trust registry.
This `did:tdw` aims to establish a more trusted and secure web environment by
providing robust verification processes and enabling transparency and
authenticity in the management of decentralized digital identities.## Contributing to the Specification
Pull requests (PRs) to this repository may be accepted. Each commit of a PR must
have a DCO (Developer Certificate of Origin -
[https://github.com/apps/dco](https://github.com/apps/dco)) sign-off. This can
be done from the command line by adding the `-s` (lower case) option on the `git
commit` command (e.g., `git commit -s -m "Comment about the commit"`).Rendering and reviewing the spec locally for testing requires `npm` and `node`
installed. Follow these steps:- Fork and locally clone the repository.
- Install `node` and `npm`.
- Run `npm install` from the root of your local repository.
- Edit the spec documents (in the `/spec` folder).
- Run `npm run render`'
- Use `npm run edit` to interactively edit, render and review the spec.
- Review the resulting `index.html` file in a browser.The specification is currently in [Spec-Up] format. See the
[Spec-Up Documentation] for a list of Spec-Up features and functionality.[Spec-Up]: https://github.com/decentralized-identity/spec-up
[Spec-Up Documentation]: https://identity.foundation/spec-up/# Publishing Previous Spec Versions
[Spec-Up] allows for multiple versions of the spec to be rendered and accessed
on the same site. We use that feature for the `did:tdw` spec to snapshot
previous versions of the spec for reference.To create a snapshot of a version:
- Make a new folder in the root of the repository for the new version, called `spec-v`. For example `v0.3`.
- Copy the `spec` folder markdown files from the point of that version into the new folder. If you are doing this process as you are starting a new version, you can just copy the files from the `spec` folder of the main branch. Otherwise, you have to find the last commit of the version and get the files from that point in the GitHub history.
- Update the `specs.json` file to include a new specification:
- Copy the primary spec entry text.
- Paste that text into a new spec entry in the `"specs"` array.
- Update the `"spec_directory"` property to be the name of the new folder you created.
- Update the `"output_path"` property to be `./v`. For example `"./v0.3"`.
- Append to the `"title"` property the version ` - Version `, For example ` - Version 0.3`.
- Add a link to the versioned specification in the `Previous Drafts` bullet list, in the `header.md` file in the main spec, so that readers can click on it from the main specification.
- Update the `header.md` file of the new version spec folder (e.g in `spec-v0.3`) to:
- Change the status to `HISTORICAL -- **THIS IS NOT THE CURRENT VERSION OF THE SPECIFICATION**`
- As appropriate, add guidance for readers **WITHOUT** altering the version of the specification itself.
- Remove the `Past Drafts` section and put a relative link back to the current spec -- such as:```text
**Latest Version:**- Specification: [https://identity.foundation/trustdidweb/](../)
- Repository: [https://github.com/decentralized-identity/trustdidweb](https://github.com/decentralized-identity/trustdidweb)```