Aera

• Name: Aera
• URL: https://www.aera.finance/
• Category: Treasury management protocol / yield vault infrastructure
• Tags: ethereum-ecosystem
• Summary: Aera is constrained treasury-execution infrastructure. The point is not another multisig shell. The point is to let a vault owner pre-define where capital may go, then let guardians keep operating inside those bounds without handing them open-ended signer discretion.
• What it does:
  • Provides smart-contract vault infrastructure for treasury management, yield programs, and other allocator workflows where offchain strategy logic still needs onchain enforcement
  • Uses guardians to submit actions while enforcing protocol and calldata constraints onchain through whitelists, hooks, and Merkle-tree validation
  • Supports both single-depositor treasury vaults and multi-depositor tokenized vaults with provisioner-based deposit and redemption flows
  • Exposes modular contracts such as BaseVault, FeeVault, Provisioner, oracle registry, and fee calculators so deployments can adapt as strategies evolve
  • Publishes protocol docs, contract references, security materials, and public contract repositories for V1/V2/V3-era code and audit artifacts
• Key claims:
  • Official site calls Aera “crypto’s most scalable, institutional-grade vault infrastructure” and describes it as non-custodial treasury and fund-management infrastructure built by Gauntlet
  • Official overview docs say Aera “powers onchain vaults with off chain intelligence” and positions guardians as actors whose transactions are reverted if they violate whitelisted-contract or calldata constraints
  • The one-page protocol explainer says Aera is a “noncustodial trustless treasury management protocol” where guardians interact only with a whitelisted set of DeFi protocols chosen by each vault owner
  • Security docs emphasize that guardian flexibility is bounded by onchain hooks, granular role separation, modular upgrades, audits, competitive review, and an active bug bounty
  • Public GitHub materials show Aera maintaining public contract repositories covering multiple protocol versions and explicitly publishing some audit artifacts in-repo
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Aera’s official site, overview docs, one-page protocol explainer, security docs, documentation index, and public contract repositories; see ../whitepapers/aera-primary-sources-2026-04-25.md.
• Sources:
  • https://www.aera.finance/
  • https://docs.aera.finance/
  • https://docs.aera.finance/llms.txt
  • https://docs.aera.finance/aera-protocol-in-one-page.md
  • https://docs.aera.finance/the-protocol/security.md
  • https://github.com/aera-finance
  • https://github.com/aera-finance/aera-contracts-public

Internal linkages

• Best read with gauntlet, which sells managed allocator judgment on top of this substrate.
• Strongest authority-graph contrast: safe.
• Keep the note on bounded delegation and vault-level execution policy, not generic treasury-software similarity.

Protocol / company boundary

• Keep this note on the Aera substrate itself: vault contracts, guardian-constrained execution, owner-defined whitelists, hook logic, Merkle-validated action bounds, and the way treasury discretion is narrowed onchain.
• Use gauntlet when the sharper question is who curates supported markets, runs the guardian workflow in practice, packages the SDK/API layer, monitors risk offchain, and turns bounded delegation into a managed product.
• That split matters because what can the vault architecture enforce? and who is actually choosing and operating the allowed strategy set? are different questions. Aera provides the rails; Gauntlet packages much of the live allocator judgment running on those rails.

Control surface

• The protocol-level leverage sits in who owns the vault, who can act as guardian, how tight the whitelists and hooks are, what calldata patterns Merkle proofs authorize, and how upgrade or migration paths are structured across vault versions.

• The company-shaped leverage sits one layer up in gauntlet: market curation, offchain monitoring, guardian operations, integration defaults, and the business logic of which bounded strategies users are actually offered.

• Read Aera as constrained treasury-execution infrastructure, not as a generic multisig shell and not as a full substitute for the entity note describing who operationalizes the strategy layer.

• Last reviewed: 2026-08-11 UTC