LogoLogo
  • Overview
  • The Aera Approach
  • Aera Protocol in One Page
  • Contact Us
  • Solutions
  • Aera for Treasury Management
  • Core Concepts
  • BaseVault and core interactions
  • Guardians and Strategies
  • Operations and submit()
  • For Advanced Users
  • Entry/Exit with Provisioner
  • For Vault Owners
  • Fee Vaults
  • Merkle Trees
  • Using Configurable Hooks
  • Building Custom Hooks
  • Cross-chain Deployments
  • The Protocol
    • Oracle Registry
  • Links
    • Website
    • GitHub
  • V2 (ARCHIVE)
    • Introduction
    • The Aera Approach
    • How Aera V2 Works
    • Guides
      • 🏦Treasury
        • Using the Factory
        • Operating your Vault
          • Vault operation via Gnosis Safe
        • Managing the asset registry
        • Managing hooks
      • 🤖Vault Guardians
      • 💹Fee Recipient
      • 💻Developers
    • Concepts
      • Vault Assets
      • Objective Function
      • Vault Guardian
      • Vault Operation
    • Use Cases
      • For Treasuries
      • FAQ
    • Contracts
      • Security
      • AeraV2Factory
      • AeraVaultModulesFactory
      • AeraVaultV2
      • AeraVaultAssetRegistry
      • AeraVaultHooks
      • GitHub
  • UI
Powered by GitBook
On this page
  1. V2 (ARCHIVE)
  2. Concepts

Vault Guardian

Vault Guardian is elected by the Vault Owner (treasury) to rebalance the underlying assets to optimize for the Objective Function. The Guardian can submit operations to the vault.

The Guardian cannot (among other things):

  • Deposit or withdraw any funds/liquidity

  • Add or remove asset types

  • Execute instantaneous value-leaking operations (such as instantaneous weight changes)

  • Delegate Guardian responsibilities.

PreviousObjective FunctionNextVault Operation

Last updated 1 year ago