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.
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
fix: proportional slippage #424
fix: proportional slippage #424
Changes from 4 commits
dbe76d9
0c775bf
2fe13bd
99e9913
05f7c9b
1622b17
4df3ca5
9df37ef
5e85959
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
But I thought the SDK rounded down? The only reason the SDK calcs should fail with 0% slippage is if the pool balances move.
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.
The whole reason we are using 0% slippage is to help the user avoid dust.
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.
There are cases where rounding down is not enough due to SDK query not being 100% precise as the comment explains. @brunoguerios has more context but it's an SC limitation.
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.
Yeah, the problem lies in the AddLiquidityBoosted queries not matching the actual transaction 100%. It's an SC limitation.
The error is ~1000 wei, which is negligible on 18 decimal tokens, but not as much on 6 decimals tokens 😕
If you'd like to get even more context, we'd have to get SC team involved in the discussion.
For all other queries that are an exact match, rounding down should be enough.