LogoLogo
  • Introduction
  • The Aera Approach
  • How Aera V2 Works
  • Contact Us
  • 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
  • V1 (Archive)
    • Aera Introduction
    • Guides
      • 🏦Treasuries
        • Operating the Vault
      • 💹Arbitrageurs
      • 🤖Vault Guardians
      • 💻Developers
    • Concepts
      • Vault Assets
      • Lifecycle Model
      • Objective Function
      • Withdrawal Validator
      • Aera Vault
        • Balancer Managed Pool
      • Vault Guardian
        • Weight Update
      • Balancer Weights
    • Contracts
      • Contracts Overview
      • Security
      • AeraVaultV1
      • PermissiveWithdrawalValidator
  • Website
  • UI
  • GitHub
  • Whitepaper (2022)
Powered by GitBook
On this page
  1. 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