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

Was this helpful?

  1. Sovereign Pool
  2. The Modules

Gauge

PreviousRebase token supportNextInteracting with Pools

Last updated 1 year ago

Was this helpful?

gauge is an optional module that a pool manager can share a portion of poolManagerFees with.

The gauge plays an important role in the tentative Valantis token incentive mechanism.

feeProtocol0 and feeProtocol1 are the input variables in the Sovereign Pool function claimProtocolManagerFees that determine the percentage of pool manager fees shared with the gauge, represented in bips.

The initial Valantis incentive mechanism has not been launched, proper specs for this gauge will be released at this time. gauge can be set to any contract which benefits from having a portion of fees sent to it, such as an external protocol treasury or similarly designed token incentive mechanism. Any address can be set to gauge as long as it is able to call claimProtocolFees on the Sovereign Pool.

The Gauge’s only role is to call the claimProtocolFees. Protocol fees are incremented whenever poolManager calls the claimPoolManagerFees function, and if it chooses to allocate a non-zero portion of its earned fees into the gauge.

Note: Rebase tokens are not supported as protocol fees because pool manager fees are not incremented in the case of rebase tokens. This was a deliberate choice to yield a simpler design for the Sovereign Pool and peripheral governance contracts related to Gauges and VAL emissions.

Only protocolFactory can deploy and set a gauge for a Sovereign Pool, by calling setGauge, and it can do so only once.

Gauge in context