Deployment Assumptions

Sovereign Pool and HOT deployment assumptions

After deploying an instance of the HOT contract bound to a Sovereign Pool pool, the following assumptions are made:

  • pool cannot have an external Sovereign Vault (meaning that reserves are always kept in pool)

  • pool cannot have a Verifier Module.

  • Once an HOT instance is deployed, poolManager will set it as the Liquidity Module and Swap Fee Module in pool. poolManager should not change Swap Fee Module to any another address.

Last updated