Fix next fee estimation #4179
Merged
Fix next fee estimation #4179
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
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.
Description
Uses pricing of canonical asset any time fees are paid in local or adopted. This is because gelato will not support next assets on their API, and have inconsistent asset support across chains (i.e. mainnet DAI is okay, but BSC DAI is not supported).
Currently blocking execution of transfers where users have paid in these assets.
Type of change
High-level change(s) description - from the user's perspective
Related Issue(s)
Fixes (hopefully) #4140 / #4152
Related pull request(s)