MORE
  • Introduction
  • MORE Vaults
    • Vaults Framework
      • Diamond Standard (EIP-2535)
      • Component Interactions
      • Upgrade & Governance Flow
    • Core Protocol Components
      • Factory
      • Core Facets
      • Registries
      • Internal Libraries
      • Accounting
    • Connectors
      • AMMs & DEXes
      • Staking
      • Lending
      • Leverage
      • Oracles
      • External Interfaces
      • Multicall
    • Security & Governance
      • Roles & Access Control
      • Upgrade Flow & Timelock
      • Configuration Guard Rails
      • Registries as Boundaries
      • Error & Event Catalogue
    • Developer Workflows
      • Deploying a New Vault
      • Extend with New Facets
      • Indexer Integration
    • Reference & Glossary
      • Event Index
      • Capabilities
      • Terms & Abbreviations
      • Contracts
  • MORE Markets
    • Markets Framework
      • Liquidity Protocol
      • Supply
      • Borrow
      • Repay
      • Withdraw
      • Liquidations
      • Flash Loans
      • Risks
    • Markets
      • Liquidity Pool
      • Reserve
      • Incentives
      • Oracles
    • Contracts
    • Build
  • Resources
    • Code, Licenses & Audits
    • Brand Assets
  • Privacy Policy
  • Terms of Use
Powered by GitBook
On this page
  1. MORE Vaults
  2. Security & Governance

Configuration Guard Rails

In conjunction with a multitude of exogenous factors, a vault’s risk profile can be determined across several parameters such as TVL caps, asset whitelists, slippage tolerance and fees.

  • TVL & Deposit Caps: Managers can raise or lower per-asset caps, but never above the hard ceiling stored in ConfigurationFacet. Exceeding limits reverts with ExceededMaxTVL.

  • Asset Whitelist: Each deposit and swap validates the token against an in-vault array; non-listed assets revert with UnsupportedAsset.

  • Global Slippage Ceiling: A basis-points constant bounds price deviation for every swap path executed by the vault.

  • Timelocked Fee Changes: Performance and management fees carry the same delay as code upgrades, giving users an exit window before higher fees apply.

All parameters live in MoreVaultsLib storage and are surfaced through read-only getters, keeping front-ends up to date. ​

PreviousUpgrade Flow & TimelockNextRegistries as Boundaries

Last updated 15 days ago