-
Notifications
You must be signed in to change notification settings - Fork 415
Open
Description
Looking at the constructor of the composable pool, it can be seen that the asset manager for the tokens is 'empty' by default. Is this for a reason?
| new address[](params.tokens.length + 1), |
I get that some new logic should be added in order to correctly match the asset manager with the pool token, or to make sure that the asset managers are only applied to the 'actual' tokens in the pool (depending on if you want to allow an asset manager for the BPT token).
But apart from that, is there any logical reason to not allow an asset manager for tokens in a composable pool?
Metadata
Metadata
Assignees
Labels
No labels