Skip to content

Add zkred-did-webvh registry entry (GH-hosted) - #7

Open
sumitvekariya wants to merge 1 commit into
decentralized-identity:mainfrom
sumitvekariya:add-zkred-did-webvh
Open

Add zkred-did-webvh registry entry (GH-hosted)#7
sumitvekariya wants to merge 1 commit into
decentralized-identity:mainfrom
sumitvekariya:add-zkred-did-webvh

Conversation

@sumitvekariya

Copy link
Copy Markdown

Adds a GH-hosted registry entry for @zkred/did-webvh (source: Zkred/did-methods), a did-resolver adapter over didwebvh-ts.

Following the GH Hosted process from the README:

  • implementations/zkred-did-webvh/did.jsonl: single-entry DID log created with didwebvh-ts (Ed25519, eddsa-jcs-2022), origin identity.foundation:didwebvh-implementations:implementations:zkred-did-webvh. Self-resolution via resolveDIDFromLog verified before submission. No witness file (no witnesses configured).
  • implementations/registry.json: entry added with the directory property, meta.updated bumped.

Context: decentralized-identity/didwebvh-ts#147. With didwebvh-ts#138 merged, the adapter will slim down to a re-export once 3.0.0 ships; the registry entry is for interoperability testing of the resolver path in the meantime and after.

@sumitvekariya

Copy link
Copy Markdown
Author

Gentle ping @PatStLouis, when you have a moment. This follows the GH Hosted process from the README: a single-entry DID log created with didwebvh-ts (Ed25519, eddsa-jcs-2022) that self-resolves via resolveDIDFromLog, plus the registry.json entry with the directory property. Happy to rebase or adjust the entry format if anything has moved since mid-July.

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

Successfully merging this pull request may close these issues.

1 participant