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

Resolve issues on sd-jwt-ts repository #84

Open
berendsliedrecht opened this issue Feb 22, 2024 · 3 comments
Open

Resolve issues on sd-jwt-ts repository #84

berendsliedrecht opened this issue Feb 22, 2024 · 3 comments
Assignees

Comments

@berendsliedrecht
Copy link
Contributor

As we will merge these two libraries, there will likely be some issues transferred as well from berendsliedrecht/sd-jwt-ts. These issues should be resolved in this repository (https://github.com/berendsliedrecht/sd-jwt-ts/issues). I can check out if they actually transfer and reopen an issue here.

@berendsliedrecht berendsliedrecht self-assigned this Feb 22, 2024
@berendsliedrecht berendsliedrecht changed the title Resolve issued on sd-jwt-ts repository Resolve issues on sd-jwt-ts repository Feb 22, 2024
@lukasjhan
Copy link
Member

Good.

I think these issues are need to be processed:

berendsliedrecht/sd-jwt-ts#14
berendsliedrecht/sd-jwt-ts#15

@lukasjhan
Copy link
Member

I'm currently processing merging sd jwt vc features.
I'm not sure how many features should be provided. The standard is quite simple(version 01).

Maybe we should focus the actual usage from Credo and Veramo

@berendsliedrecht
Copy link
Contributor Author

If we get feature parity with https://github.com/berendsliedrecht/sd-jwt-ts then it'll work with credo and that should be the first goal, yes. However, we can make some improvements and fixes where needed.

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