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

Implement our own did:key creation/resolution #43

Closed
amika-sq opened this issue Dec 5, 2023 · 2 comments · Fixed by #97
Closed

Implement our own did:key creation/resolution #43

amika-sq opened this issue Dec 5, 2023 · 2 comments · Fixed by #97

Comments

@amika-sq
Copy link
Contributor

amika-sq commented Dec 5, 2023

Similar to #41 and #42. There's a desire to implement did methods in our codebases, and not rely on third-party libraries that implement the current specs.

This task is to remove Spruce's did-method-key dependency (added in PR #25) from the dids crate and implement it ourselves.

@KendallWeihe
Copy link
Contributor

KendallWeihe commented Apr 21, 2024

We're currently relying on the spruce crate and mapping to/from our types. This will remain in place until it becomes an apparent blocker.

Reference #97

@KendallWeihe
Copy link
Contributor

Reopening, will close once PR merged

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 a pull request may close this issue.

2 participants