[proposal] Define a credential revocation API
See original GitHub issueWe need a plugin interface for the credential revocation frontend.
At this time, there are 2 foreseeable actions that this interface should perform:
-
One is a call to revoke a credential. Probably this interface will be implemented by an aggregator that can look at a credential that is about to be revoked, inspect the
credentialStatus
entry and then forward the revocation call to the actual credentialStatus driver. -
The other (which may be optional?) is a call that a Credential Issuer might make to build a
credentialStatus
entry. Many credentialStatus methods work on collections of credentials, so it is likely that when a credential is being created it needs to know its place in the collection (its index, its merkle path, etc)
This task only refers to the interface for such a plugin, and should initially serve as a discussion board.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top GitHub Comments
Hi, @Eengineer1! I’m currently writing the interfaces we just described here and planning the implementation of the components for next Veramo version. It’s the right time to have you joining! Do you have something specific you want to collaborate on? It would be nice to get together to plan. Could you please get in touch with me through the Veramo Discord channel, please?
Hey, @italobb @mirceanis .
Keen on helping with this. A few questions: