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.
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
Ethermint support #1295
Ethermint support #1295
Changes from all commits
b5990f2
16bd818
042c69b
1668937
2d7842a
e07d221
06aee03
8f2a737
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering if it's a good idea to restrict the possible values that
pk_type
can take, either by making this an enum, or checking the String against a predefined list of accepted values.Beside
'/injective.crypto.v1beta1.ethsecp256k1.PubKey'
and"/ethermint.crypto.v1alpha1.ethsecp256k1.PubKey"
are there numerous other values thatpk_type
can take?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are potentially many more :
/ethermint.crypto.v1beta1.ethsecp256k1.PubKey
,/ethermint.crypto.v1.ethsecp256k1.PubKey
,/cosmos.crypto.ethsecp256k1.PubKey
...Right now, in order to be useful (given Ethermint has been copied over and modified), it makes sense to keep it a bit flexible -- otherwise, every chain would need to open a PR to modify the enum.
Later, once the ethsecp256k1 support lands in Cosmos SDK, it'll make sense to deprecate this with that Cosmos SDK release and recommend chains to migrate to
/cosmos.crypto.ethsecp256k1.PubKey
(or whatever the canonical proto ends up being)... and after that, remove this extra config.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like a plan, thanks for the detailed rationale! I agree with you.