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
My understanding is that the intention for SwapV3 is to also handle BPT -> Token swaps. Currently this path is not implemented. The issue arose when working on balancer/backend#896. The pool used was part of the seventh vault deployment. The pool in question (deployed with the ExitFeeHook) is https://sepolia.etherscan.io/address/0xc7436329da34B54fAD1400f400931751E1D06Cf8. package version used was
"@balancer/sdk": "0.25.0"
My understanding is that the intention for SwapV3 is to also handle BPT -> Token swaps. Currently this path is not implemented. The issue arose when working on balancer/backend#896. The pool used was part of the seventh vault deployment. The pool in question (deployed with the ExitFeeHook) is https://sepolia.etherscan.io/address/0xc7436329da34B54fAD1400f400931751E1D06Cf8. package version used was
"@balancer/sdk": "0.25.0"
The relevant code:
const queryOutput = await sdkSwap.query(rpcUrl);
In this case is wanting do query a singleSwapExactIn where the BPT (TokenIn) and WETH (tokenOut). This leads to a
TokenNotRegistered["0xc7436329da34b54fad1400f400931751e1d06cf8"]
in the Vault - see this sim: https://dashboard.tenderly.co/mcquardt/project/simulator/14613a09-4243-46a2-9807-a0d5b47c5776
The pool used is:
The text was updated successfully, but these errors were encountered: