Supported Integrations
Reference guide for the venue families Avana can support and the review gates used before any integration is enabled.
Overview
Avana does not treat every AMM venue as interchangeable. Support depends on whether the protocol can price a position conservatively, unwind it in stressed conditions, and manage it within the Borrow Spoke and Hub risk framework.
This page is an integration reference, not a live launch dashboard. For pool admission policy, see Allowed LP Pools. For valuation assumptions, see Price Oracles.
Venue Families
Concentrated liquidity venues
These integrations support range-based LP positions whose value depends on current price, active range, and inventory split.
Fungible stable and weighted pools
These venues expose ERC-20 LP shares that can be reconstructed from pool balances, external prices, and recoverable unwind assumptions.
Custom or hook-based designs
More advanced pool architectures can be supported only when the protocol has a clear oracle model, custody path, and liquidation adapter for them.
Enablement Status
Whether a venue is enabled on a specific network is an operational question, not a protocol invariant. A venue family may be supported in principle but disabled on a given deployment until oracle coverage, liquidation routing, and risk parameters are in place.
Review Requirements
- • A venue must support conservative position valuation from robust external prices and verifiable state reconstruction.
- • The protocol needs a reliable unwind path for liquidation, including fee collection and routing into the debt asset.
- • Pool depth, concentration risk, correlation assumptions, and operational monitoring must fit inside the risk framework.
- • New venue support should be treated as a governance and risk action, not just an interface update.