-
Notifications
You must be signed in to change notification settings - Fork 194
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
Revocation Clarification (does not work after the first revocation in a list) #1807
Comments
Thanks for the detailed description @vk1992op! Could you provide a repo with a minimal reproduction in Node.JS? That way i can easily dig in and see if there's a bug or whether your flow needs tweaking. |
https://github.com/vk1992op/revocation-demo This is a cut-down version of the project I am working on, you can follow the readme, and you should have it up and running in a few steps. A few important additional notes: you will need your own S3 compatible bucket for the revocation tails (s3, backblaze b2, cloudflare, digital ocean)the base url for the postman calls will be: http://0.0.0.0:8002 (if port is not changed in env)the files of interest are:
flow is the following:
|
@vk1992op I have encountered the same issue when trying to revoke a credential at index 2. Could you let me know if you found any solution? |
TLDR: Revocation works fine for the first credential but if I try to revoke a second one in the same status list the ledger returns:
There is a possibility that I do not fully understand how exactly the flow for revocation should work, so I will write down my flow.
Setup
I have done the flow as described in the test of the anoncreds package
However
If I revoke all other credentials in the list (all except the one at index 0, which is already revoked) -> OK, everything works as expected and all credentials are successfully revoked.
For the exact calling of methods and parameters I am using the tests in the anoncreds package as a reference.
Could it be that the status list has to be used to revoke all credentials inside it, but if that is the case then why does it successfully revoke one but only the first time?
The text was updated successfully, but these errors were encountered: