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. V1 (Archive)
  2. Concepts
  3. Aera Vault

Balancer Managed Pool

The Managed Pool primitive was chosen as it provides flexibility in defining weight changes while being able to scale to support a large number of assets (50). Please see Security for associated risks.

The Balancer Managed pool is deployed by the Aera Vault in the constructor function. The following additional constraints are applied to the pool:

  • Tokens are hardcoded upon deployment and assets cannot be added/removed

  • The Balancer Pool Token shares cannot be traded and are owned exclusively by the Aera Vault

  • No liquidity is ever removed or added, any withdrawals/deposits are handled by rebinding the vault.

PreviousAera VaultNextVault Guardian

Last updated 2 years ago