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 Operation

Vault operations are a series of transaction sequences used by the guardian to rebalance the vault. These transaction sequences are specified in the relevant submit call and checked and executed by the vault.

Constraints on vault operations

Both the asset registry and the hooks contract are used to limit what operations can be accepted. In particular, the current iteration of the hooks contract:

  • Restricts any outgoing allowances for vault tokens to be created as a result of an operation

  • Restricts the vault value from decreasing beyond a pre-specified threshold

  • Restricts the types of operations and contracts that are called in those operations to a whitelist

PreviousVault GuardianNextFor Treasuries

Last updated 1 year ago