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
    • Security
  • gtUSDa
  • Integrating with gtUSDa
  • 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. V1 (Archive)
  2. Concepts

Aera Vault

Last updated 1 year ago

CtrlK

The Aera vault is a wrapper contract over the Balancer Managed Pool that restricts and facilitates certain functions (see https://docs.balancer.fi/getting-started/faqs/pools-and-lbps).

The following features are supported:

  • Vault owner can deposit funds or withdraw funds (according to Withdrawal Validator) in a way that preserves the Balancer spot price between different pairs of assets

  • Vault owner can finalize the fund and return all funds to treasury

  • Vault Guardian can set swap fees, create and cancel weight update schedules

  • Both owner and Guardian can pause trading but only owner can re-enable it.

For more detail on the API, see AeraVaultV1.