Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a way/convention for transitioning an existing did:web DID to be a did:tdw DID? #68

Open
swcurran opened this issue Jul 9, 2024 · 2 comments

Comments

@swcurran
Copy link
Collaborator

swcurran commented Jul 9, 2024

Raised by @PatStLouis asked on the CCG Presentation about did:tdw. Since the DID does not have a SCID, it cannot be “just used”. However, perhaps there is a good convention for adding a did.jsonl file beside the existing did:web such that the DID can transition to a did:tdw. Calculation of the SCID would have to be formalized, the numbering and so on.

A number of questions to consider.

@andrewwhitehead
Copy link
Contributor

It seems reasonable to me, and I like the use case much better than adding a generic did:web to a did:tdw for compatibility.

  1. Copy the current DID document, adding {SCID} placeholders and changing the method, and perform the genesis routine to create the SCID, assigning update keys and updating the document in the process.
  2. Update the did:tdw document to have an alsoKnownAs set to the did:web.
  3. Update the did:web document to have an alsoKnownAs set to the did:tdw (this is expected to be bidirectional).
  4. Publish did.jsonl and the updated did.json

On future updates, you would likely take the did:tdw document and simply update the document identifier to generate the did.json. Eventually, everything should be migrated to the new DID and the old one retired.

@swcurran
Copy link
Collaborator Author

Given the update in PR #77 that now puts the SCID in a fixed position, this becomes pretty easy -- the DID does not have to move.

To be added to a section of the specification. Arguably, should be in the Implementers Guide.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants