Valantis Documentation
Valantis Website
  • Welcome to Valantis
  • Sovereign Pool
    • The Modules
      • Pool Manager
      • Liquidity Module
      • Swap Fee Module
      • Verifier Module
      • Oracle Module
      • Sovereign Vault
        • Rebase token support
      • Gauge
    • Interacting with Pools
      • Swap Parameters
      • Swap Steps
      • Multi Token Support
      • Deposit Liquidity
      • Withdraw Liquidity
      • Flash Loans
  • Hybrid Order Type (HOT)
    • Understanding HOT: A Graphical Overview
    • HOT API
      • HTTP request parameters
      • HTTP request response
      • Reasoning for Request structure
      • Solver Integration
      • Market Maker integration
    • HOT Smart Contracts
      • Interfaces
      • State variables and roles
      • AMM
      • HOT Swap
      • AMM Swap
      • Hybrid Order Type (HOT) struct parameters
      • Alternating Nonce Bitmap
      • Deposits
      • Withdrawals
      • Deployment Assumptions
    • Liquidity Manager Docs
      • Reference Oracle
      • Deposit
      • Withdraw
      • Signature
    • Swap
      • Swap Context
      • AMM Swap
      • HOT Swap
      • HOT Quote Parameters
        • Bitmap Nonce Instructions
    • Solver Docs
      • Solver Request
      • Simple HOT Swap Example
      • Partial Fill HOT Swap Example
    • Risks and Trust Assumptions
      • Roles
        • Sovereign Pool Manager
        • HOT Manager
        • HOT Signer
        • Liquidity Provider
      • Threats
        • Deposit Sandwich
        • Malicious Price Bound
        • Malicious Signer
        • Mispriced HOT Quote
  • Validly
    • Understanding Validly
    • Swap
    • Deposits and Withdrawals
    • Deployments
  • Stake Exchange (stHYPE AMM)
    • Swap
      • Instant Withdrawals (LST -> Native Token)
      • New Stake (Native Token -> LST)
    • LP Positions
      • LP Withdrawals Instant
      • LP Withdrawal Queued
    • Ratio Fee
    • Lending of Reserves
    • Smart contracts
      • STEXAMM.sol
      • StHYPEWithdrawalModule.sol
      • StexRatioSwapFeeModule.sol
      • DepositWrapper.sol
      • AaveLendingModule.sol
    • Risks and Trust Assumptions
    • Integration examples
  • Deploy and Build
  • Resources
    • Audits
    • Links
    • Get HYPE on HyperEVM
Powered by GitBook
On this page
  • Functions
  • Security Model
  • Trust Assumptions

Was this helpful?

  1. Hybrid Order Type (HOT)
  2. Risks and Trust Assumptions
  3. Roles

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.

PreviousRolesNextHOT Manager

Last updated 1 year ago

Was this helpful?