Revocation contracts - Need help with proxy #76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: vdsilveira <122502607+vdsilveira@users.noreply.github.com>
Signed-off-by: vdsilveira <122502607+vdsilveira@users.noreply.github.com>
|
Hello @vdsilveira ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have added credential revocation smart contracts and tests in Hardhat. The revocation worked when testing the contract directly on the network, but I was not successful using the proxy contract. I need help resolving the issue with the proxy.
@Toktar #54
About the design/specification:
I used the same design as Anoncreds. Basically, the revocation contract checks the credential and creates a credential revocation list, where the revocation status can be changed.
About the proxy:
I used yarn genesis/generate according to the instructions in the README, modified the genesis.json, and launched the network with the new revocation contract included. However, when testing the revocation contract through the proxy, I encountered an error. When testing the contract directly through Remix (as shown in the image below), it worked. Therefore, I believe I need help fixing the proxy error.