fix: take ICA into account for dyncomm ante #450
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
|
I guess this would then in theory also be necessary for the tax handler? @fragwuerdig |
StrathCole
reviewed
Mar 11, 2024
Yes. In theory. |
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.
Referencing closed PR #449
Let's be really pedantic.
ICA host capabilities are currently disabled on Terra Classic (ICA host parameter enabled is set to false). But if a param change governance prop passes that opens Terra Classic as ICA host chain, then the MsgEditValidator could be triggered via ICA - meaning MsgEditValidator comes wrapped inside a MsgRecvPackage.
Unit tests included.
Phew.