-
Notifications
You must be signed in to change notification settings - Fork 32
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
Mirror verify error handling logic #367
Comments
@kayaelle this one was for us having Atomic Jolt create a shared library to display the verification status that could be used in both LCW and VerifierPlus. |
@dmitrizagidulin - was this delivered? If not, can you provide some details to help lead the development? Thanks! |
@dmitrizagidulin - have you been working on this as part of @contexts backwards-compatibility fix? |
Let me check to see if anything else remains... |
Moving this to LCW-Backlog. The aim is to extract the verifier code into a library for re-use. Will do some dev planning with Dmitri. |
Questions remain on how to implement/how to best do this. |
@dmitrizagidulin says refactor is needed |
This common verification library will likely be used by:
|
We will also need to add support for both the https://github.com/digitalbazaar/eddsa-rdfc-2022-cryptosuite suite in addition to the existing ed25519https://github.com/digitalbazaar/ed25519-signature-2020 suite and use whichever is appropriate for the given credential. |
verifier-core related issue, closing this one |
From pivotal list.
Labels: shared verification library, web verifierplus
status: delivered ?
Created Oct 26, 2022
Requested by Seth
The text was updated successfully, but these errors were encountered: