Aqua0
Security & Trust

Audits & security process

How we approach audits, monitoring, and incident response.

Scope

Aqua0's vaults, adapters, and Composer are built on audited OpenZeppelin primitives, not custom re-implementations of that plumbing.

ContractsBuilt onUpgrade path
Per-asset vaultAccessControlUpgradeable, PausableUpgradeable, ReentrancyGuardShared UpgradeableBeacon, upgrades pass through a timelock delay
Composer, vault factory, vault registryUUPSUpgradeableEach singleton upgrades itself, gated to the same timelocked upgrade authority

Audit effort is scoped to the thin Aqua0-specific layer built on top of those primitives, not a re-audit of the underlying OpenZeppelin code.

  • the async withdrawal request/claim path and its settlement guard
  • the hybrid PnL harvest, reconciliation, and clawback logic
  • adapter wiring
  • the Composer's routing and authorization

Security process (high-level)

  • staged deployments and controlled rollouts
  • monitoring and alerting
  • fast incident response and clear communications

On this page