-
Notifications
You must be signed in to change notification settings - Fork 5
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
Tasks: Fix Hop bridger validations #107
Conversation
e7ca0a4
to
880bcb7
Compare
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.
Looking good!
const amountAfterFees = amount.sub(fee) | ||
const minAmountOut = amountAfterFees.mul(fp(1).sub(slippage)).div(fp(1)) |
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.
Where is the max fee being set?
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.
Nowhere. The config is being ignored
We discussed offline that it should raise an error when the max fee is not set and the fee is not 0
This PR introduces two changes related to Hop bridger validations:
fee
is considered inside themin amount out
max fee pct
is now an absolute value instead of a percentage. And thismax fee
config is now implemented in theBase Bridge Task