You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is that we might have custom coins for fees (which are non-fee tokens). Currently such tokens are burned, but in case of changing the API, we're going to send them to the community pool. This potentially leads to the community pool spamming (as mentioned in the ADR). Though this statement is not proven and requires additional research.
The text was updated successfully, but these errors were encountered:
We handle AMM and IRO fees, but we're still left with gas fees. The current design is:
We need to unify the approach. The non-DYM fees are handled in the x/txfees AnteHandler. In theory, this should be simply changed for
The problem is that we might have custom coins for fees (which are non-fee tokens). Currently such tokens are burned, but in case of changing the API, we're going to send them to the community pool. This potentially leads to the community pool spamming (as mentioned in the ADR). Though this statement is not proven and requires additional research.
The text was updated successfully, but these errors were encountered: