-
Notifications
You must be signed in to change notification settings - Fork 607
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
x/incentives: refactor create gauge and add to gauge fees to use txfees denom #2283
Conversation
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.
LGTM, nice work
Could you please add a changelog entry for this? This would be API breaking due to the constructor update. However, I think we should still backport this to v11 since it's not state-breaking |
if err != nil { | ||
return err | ||
} |
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.
This is technically a state break but the likelihood of this non-deterministically happening is low so I think we can still backport this
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.
Actually, since this is on the message path, it is possible to run out of gas. So I think we should avoid backporting
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.
Thanks for doing this, now the simulator will be happy again 😄
@czarcas7ic good to go Can't upset the simulator for too long :D |
Closes: #2236
What is the purpose of the change
In
#2227
we hard coded the fee denom for create gauge and add to gauge fees. This was done to minimize the changes for a smooth and expedited v11 release.However, the hard-coded denom causes issues with the simulator. Simulator assumes "stake" denom for majority of its tests by default. As a result, no account has the hard coded "uosmo" denom to pay the fee. The simulator doesn't run because no account has "uosmo", only "stake"
Brief Changelog
We should avoid backporting these changes to v11.x
Testing and Verifying
Use dynamic denom calculation instead of hardcoding it in these tests ;
Documentation and Release Note
Unreleased
section inCHANGELOG.md
? (yes)x/<module>/spec/
) / Osmosis docs repo / not documented)