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
The CLR was made considering that pools that have buffers would always wrap / unwrap, and that doesn't seem to be the case in practice.
E.g. a pool with sDAI might have a buffer for it, but users will still want to operate with sDAI directly. So we might need to specify when to wrap / unwrap (as with the batch router).
The text was updated successfully, but these errors were encountered:
For non-nested ERC4626 pools, we'll include an array of flags in the same order as the limit amounts: wrap / unwrap if true, use the token in the pool if false. This applies to add (proportional, unbalanced) and remove proportional.
For nested pools we're specifying the tokens, so maybe we can be smart about it and only wrap / unwrap according to the existing inputs. In other words, we'll try to preserve the existing API.
The CLR was made considering that pools that have buffers would always wrap / unwrap, and that doesn't seem to be the case in practice.
E.g. a pool with sDAI might have a buffer for it, but users will still want to operate with sDAI directly. So we might need to specify when to wrap / unwrap (as with the batch router).
The text was updated successfully, but these errors were encountered: