-
Notifications
You must be signed in to change notification settings - Fork 8
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
Should we link to implementations? #1
Comments
Some of these APIs may not have any actual public testable interfaces.... I feel like thats gonna make them less likely to survive... I would like to link to at least 1 public free to test implementation of the issuer and verifier API... ideally open source... happy to contribute that, even if it only support a limited set of the API for testing purposes. |
Is this a link to a live, callable API -- or to code that could be downloaded and run (e.g., in a docker container)? If the former, then we have something live that explicitly contradicts the security model that was our design criterion (that we wouldn't cross trust boundaries between client and service). That feels a bit weird to me; it would set the wrong expectations. But maybe if we documented the weirdness, it would be okay. |
Co-authored-by: Orie Steele <orie@transmute.industries>
https://github.com/transmute-industries/issuer-verifier-vc-api
The text was updated successfully, but these errors were encountered: