Managed Pool Features
A Managed Pool is a highly configurable extension of a Balancer Weighted Pool. Using a “Managed Pool Controller” or MPC connected to the underlying managed pool allows for safe use of the following features.
Feature |
Description |
Invariant |
Constant Product |
Min Token Count |
2 |
Max Token Count |
50 |
Min Token Weight |
1% |
Max Token Weight |
99% |
Min Swap Fee |
0.0001% |
Max Swap Fee |
95% |
Swap Fee Mutability |
Allows for instantaneous and gradual changes after deployment |
Swap Enabling |
Can be enabled or disabled |
Token Weight Mutability |
Allows for instantaneous and gradual changes after deployment |
Token Composition Mutability |
Allows for add/remove token functionality after deployment |
Liquidity Provider Allowlist |
Allows for allowlist. Can be activated/deactivated after deployment. List can be mutated after deployment. |
Circuit Breakers |
Allows for setting circuit breaker values on tokens (on a per-token basis) to ensure weighted value ratios do not go outside of allowed bounds |
Management Fees |
Allows for optional AUM Management Fees |
To help us better understand the needs for your particular project, please fill out the “Response” column in the following tables. For a particular feature we’d like to know if it is:
- Not needed
- Nice to have
- Must have
Some features are specific to how you plan to use managed pools. There are specific tables for treasury management, indices, and automated systems. You can ignore/delete any of them that are not relevant for you.
General Features |
Response |
Token count: How many tokens are expected? |
|
Change weights of assets in the pool |
|
Add/remove assets in the pool |
|
Add/remove assets without requiring manager to take custody |
|
Will the default state of the pool have swaps enabled or disabled? |
|
*Swaps enabled allows for real time rebalancing. |
|
Swaps disabled implies a schedule for rebalancing, eg monthly or quarterly* |
Enabled/Disabled (pick one) |
Downside protection on tokens (circuit breakers) |
|
Would you be willing to pay for “pool operation services” such as setting optimal rebalancing parameters? |
|
Treasury Management Questions |
Response |
Will the treasury be the sole LP, or can others freely join the pool? |
|
Will the owner of the MPC also be the LP? If not, are timelocks or LP approvals required/desired for taking pool actions? |
|
Index Questions |
Response |
LP Access control (eg, do you want to only allow whitelisted LP’s) |
|
Allow list for tokens eligible to be added to the pool |
|
Any requirements for timelock durations? (pool actions are subject to timelocks so LP’s have time to react if desired) |
|
Are there custody considerations for the manager? |
|
Automated System Questions |
Response |
Are all actions predefined, or are settings (pool command arguments) determined by on-chain data? |
|
Are all triggers predefined, or can triggers be changed? Are they all calculable on-chain? |
|
Are there supposed to be authorized executors, or can executions be done trustlessly? |
|
Are there cooldown periods between executions? |
|
Are any arguments necessary for execution? |
|
Finally, any additional information that would be helpful for us to know: