You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are evaluating the possibility of adding offline verification for W3C Verifiable Credentials, but we would like to seek some guidance before starting. I assume we would need to "cache" somehow the DID documents, contexts, definitions, revocation status, issuers and keys...
Obviously, we understand this is not a 100% safe approach as we will be using cached data, but whe are facing a use case where this is a requirement.
So my question is, what pieces should I change / improve on credoJS? Or should I directly go down to @digitalcredentials/vc package?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
Hi all,
We are evaluating the possibility of adding offline verification for W3C Verifiable Credentials, but we would like to seek some guidance before starting. I assume we would need to "cache" somehow the DID documents, contexts, definitions, revocation status, issuers and keys...
Obviously, we understand this is not a 100% safe approach as we will be using cached data, but whe are facing a use case where this is a requirement.
So my question is, what pieces should I change / improve on credoJS? Or should I directly go down to
@digitalcredentials/vc
package?Thanks in advance.
The text was updated successfully, but these errors were encountered: