We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After #267 is implemented, there would be a need to restore the revoked asset / instance.
This may help in a 'suspension' of asset to see if the particular transfer query would come on the revoked asset.
The text was updated successfully, but these errors were encountered:
This issue is no more required as we implemented 'status-change' instead of revoke - restore. now same call can be used for all state change.
Sorry, something went wrong.
No branches or pull requests
After #267 is implemented, there would be a need to restore the revoked asset / instance.
This may help in a 'suspension' of asset to see if the particular transfer query would come on the revoked asset.
The text was updated successfully, but these errors were encountered: