Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
sig nonce usecase
See original GitHub issueHi Team,
I am a software developer from Energy Web and have couple of queries regarding EthereumDIDRegistry contract.
The current deployed EthereumDIDRegistry doesn’t have sig nonce changes (PR). Is there any specific reason for it? The changes are quite old and it is neither merged to the master nor deployed. We are moving to production and want to confirm which version of the contract should we move ahead with.
Also, would it make sense to have an Upgradable EthereumDIDRegistry contract?
Apologies If I am not using the right channel / template for such queries.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This issue and other requests made me realize that this contract’s immutability is becoming an issue, so I started a governance topic for did:ethr on our discord: https://discord.gg/MTeTAwSYe7
You can fork this repository and push to your fork. Then you can make the PR from the forked repository to the main repository.