Sovereign Pool Manager

Functions

• setALM: Initializes the Liquidity Module (LM) address of the pool. Can only be called once.

• setPoolManager: Sets the address of poolManager.

• setPoolManagerFeeBips: Sets fee in BIPS for poolManager.

• setSovereignOracle: Sets Sovereign Oracle Module in this pool.

• setSwapFeeModule: Sets the Swap Fee Module for this pool.

Security Model

1. The HOT should be set as the pool's LM and swapFeeModule. The manager can only set the ALM once, but the swap fee module can be changed. Therefore the Pool Manager should be a smart contract that cannot change the swapFeeModule once it is set to the HOT.

2. Adding a new Sovereign Oracle to the pool has no security implications for the HOT.

3. The Sovereign Pool Manager should not be able to change the pool manager address arbitrarily once it is set.

Trust Assumptions

1. The Sovereign Pool Manager should set the poolManagerFeeBips reasonably. Setting this variable to a high value could lead to high fees being charged from LPs. This fee is also capped at 50% ( of all accumulated swap fees ) in the smart contracts.