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. Contracts

Contracts Overview

An Aera vault can be deployed by deploying the following two contracts:

  • AeraVaultV1 – the main vault, pointing to a Withdrawal Validator

  • PermissiveWithdrawalValidator – a permissive withdrawal validator contract that allows withdrawals of an arbitrary size

Deployment Flow

An Aera Vault can be deployed by following the below steps:

  • Deploy a withdrawal validator contract that inherits from a IWithdrawalValidator interface

  • Deploy the Aera Vault with a given selection of tokens

  • Make an initial deposit by approving token amounts and calling initialDeposit. This step is essential as it helps establish an initial spot price for the underlying Balancer pool.

PreviousContractsNextSecurity

Last updated 1 year ago