Add whitelist for fee denoms #564
Open
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
codchen
force-pushed
the
tony/restrict-fee-token-type
branch
from
8c6153a to
b425180
Compare
codchen
force-pushed
the
tony/restrict-fee-token-type
branch
from
b425180 to
f5406f1
Compare
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.
Describe your changes and provide context
It is possible for tx sender to include "garbage" tokens as fees which may decrease chain performance if in large quantity (in terms of the number of different denoms, which may be created via tokenfactory). This PR introduces a new parameter to whitelist denoms that can be used for fees. Note that
useiis always whitelisted.Testing performed to validate your change
local sei with tokenfactory tokens