added derive_operatorid command to egnkey #247
Merged
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
also refactored commands to be in their own packages to prevent var/flag conflicts
shrimalmadhur
approved these changes
May 30, 2024
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.
Not sure if this is the best place to have this but I really need something like this to help me debug wrong operator registration scenarios for tests and local devnets.
Typically generate a bunch of keys from some mnemonic, and want to quickly see their associated operatorId (hash of G1 pubkey associated with that private key). So with this command I'll just be able to pipe the private keys through this to also print their operatorId
What Changed?
also refactored commands to be in their own packages to prevent var/flag conflicts
Reviewer Checklist