Skip to main content
Avana icon

Allowed LP Pools

Governance-controlled allowlist for the pools and LP families that may be admitted as collateral.

Overview

LP collateral is accepted only from pre-approved pools or templates. Admission is not based on brand name alone. Avana needs enough information to value the position, manage liquidation, and constrain exposure inside the protocol's risk framework.

Pool approval works alongside Collateral Factors and Risk Framework. The allowlist decides whether a pool may enter the system; collateral factors decide how much borrowable value each admitted position can contribute.

Review Criteria

  • Reliable external price coverage for the underlying assets
  • Sufficient pool depth and credible unwind paths during liquidation
  • Clear admissibility rules for the LP family or spoke template
  • Acceptable concentration, volatility, and peg-stability profile
  • Operational support for indexing, fee handling, and liquidation routing

Pool Families

Stable and correlated pools

Usually the simplest to admit when pricing, peg stability, and unwind depth are strong.

Blue-chip volatile pools

Can be supported with conservative collateral factors, liquidity checks, and stronger liquidation assumptions.

Concentrated liquidity positions

Require position-level valuation and careful handling of active range, one-sided inventory, and fee state.

Custom or experimental designs

Need explicit oracle, custody, and liquidation support before they can enter the allowlist.

Risk Application

Avana does not apply one blanket collateral factor to an entire spoke. Each admitted LP position is valued independently, discounted according to its risk treatment, and then added to the user's aggregate borrowing capacity inside that Borrow Spoke.

This is why pool approval and collateral valuation are tightly linked: a pool may be operationally valid for deposit, but still require conservative caps, lower LTVs, or stricter liquidation handling once it is admitted.

Integration Notes

Builders should think in terms of approved pool templates and deployment-specific allowlists, not an open-ended list of all LPs in a venue.

New pool families usually require updates across oracle handling, liquidation routing, risk limits, and monitoring infrastructure before they are safe to enable.