-
Notifications
You must be signed in to change notification settings - Fork 608
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
Auto-swap non-osmo tx fees to osmo #1121
Comments
Later
|
Hi, I was just wondering why the epoch part of this is important? Would it still be important even if the fees were not distributed to stakers? Thanks a lot |
Its run at epoch in order for the fees that got transformed into osmo to the be distributed. It could happen at faster or slower intervals, but just makes sense to run at epoch prior to distribution. |
Thanks @czarcas7ic I understand it needs to be transformed into osmo, but I was just curious why the need to do this at epoch and not on the fly? thanks! |
The main reason is gas efficiency for users. If every transaction included an additional swap to settle fees, users would have to pay much more in gas to compensate. This approach amortizes the cost across many users. Keep in mind that it would be fully secure even if we never swapped to OSMO, so there's no security risk with this parameter. Doing this at epoch just happened to be both very effective and very convenient. |
Ok thanks! |
Currently when a transaction fee is paid in a valid non-OSMO token, the token is collected and distributed as-is to stakers. While this doesn't affect the core user flow since gas fees are zero for the time being anyway, it causes confusing UX around claiming staking rewards (since epochs with too many additional denoms used as tx fees breach the auto set gas limit on Keplr) and dust for random denoms showing up in wallets. The goal of this change would be to implement the following logic:
More specifically, one relatively clean way of implementing this would be to take the following steps:
The text was updated successfully, but these errors were encountered: