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
Currently we can create credential definitions that support revocation, and the issuer can call /revoke-credential after a credential has been issued. This is asserted in the tests.
One enhancement would be to assert the behavior during a proof request, after a cred has been revoked.
And other things, like asserting that a non-revocable credential should error when attempted to revoke ...
revocation_registry_rev_reg_id_fix_revocation_entry_state_put (Fix revocation state in wallet)
revocation_registry_rev_reg_id_issued_details_get (Get details of credentials issued against revocation registry)
revocation_registry_rev_reg_id_issued_indy_recs_get (Get details of revoked credentials from ledger)
update_registry (Update revocation registry with new public URI to its tails file)
upload_tails_file (Upload local tails file to server)
So, there you have it! Revocation is fairly complex and we should work towards implementing more of those unused methods in order to support it properly.
edit: added checkboxes for the methods that have since been implemented
Replicate demo test case: https://aca-py.org/main/demo/#revocation
The text was updated successfully, but these errors were encountered: