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

HOT Signer

PreviousHOT ManagerNextLiquidity Provider

Last updated 10 months ago

Was this helpful?

Functions

  • Can sign HOT Quotes for HOT swaps.

Security Model

  1. The signer is responsible for market-making for all incoming solver swaps on behalf of the LPs.

  2. EOA signers should ensure their private key is managed securely, using industry-leading practices.

Trust Assumptions

All LPs trust the signer to run a competitive market-making algorithm on the backend and ensure their private key is secure.

A bad signer could cause losses to LP funds because of LVR or attacks.

Note: The HOT AMM infrastructure is flexible and can support various mechanisms for improving decentralization, fault-tolerance and trust. The signer itself can be an Externally Owned Account (EOA) or a smart contract. While an EOA is simpler to implement and more gas-efficient, it is more centralized and subject to the trust assumptions outlined above. Without any contract changes, one can transition to smart contract-based signers, which are compatible with off-chain batch auctions, decentralized validator sets, validity proofs, multi-signature schemes, and other mechanisms. This flexibility allows the backend to adapt and incorporate multiple decentralized solutions over time, ensuring fair price discovery and robust performance for LPs

malicious signer