-
Notifications
You must be signed in to change notification settings - Fork 307
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
Issues With BalancerV2 Liquidity Bootstrapping Pool Amounts #111
Comments
Looking over the code, it looks like weights for LBPs are computed with |
@shresthagrawal - Actually I think this might be a more general issue with Balancer weighted pools. We had a price route including this pool where the computed output amount was way off the actual output amount: Specifically, the price route expects
However, when simulating - the output amount is ~22% less and only
This is for a weighted pool trading USDC-WETH so it seems that the issue is not limited to LBPs. |
I wanted to report an issue we’ve been having with routes including a specific token
0x5c1892bb9e42b4bf89e5b0b21542e2f8622a0bb8
. It looks like its using liquidity from the Balancer V2 “Liquidity Bootstrapping Pool” id0xe9f7be5f534057b7ed5be82553e4da3c7aaac8b40002000000000000000001f9
.I noticed that the price route that is computed usually expects a much higher USDC return over what it is actually receiving. Just speculating, but could it be related to the fact that this pool has a dynamic fee or that the pool has gradual weight updates?
AFAICT, all price routes involving the above LBP are having issues.
Resources:
JS script that causes issue with ParaSwap API
Example invocation of script 👆 with issue
When simulating with Tenderly (with a fork where I set required allowances), I see that the actual swapped amount is:
Despite the route reporting that:
Which is a 5% difference.
The text was updated successfully, but these errors were encountered: