Router Contract

Overview

The router coordinates DEX-specific mechanics — deposits, withdrawals, fee claims, and unwind steps — so those actions do not have to be scattered across every flow that touches LP collateral.

The router does not decide risk. Collateral factors, health checks, and liquidation eligibility remain in the Borrow Spoke, Hub, oracle stack, and risk framework. See Borrow Spoke and Liquidation Framework.

Role in System

Different DEXs expose different entry, exit, and fee-collection methods. The router gives Avana one integration layer for those mechanics so builders are not forced to implement each DEX separately in every flow.

Adapter Model

Each supported DEX family has an adapter that knows how to claim fees, remove liquidity, and expose the actions the protocol needs for that LP format. That keeps DEX-specific behavior isolated instead of leaking into every user-facing code path.

Adapter support only matters when valuation and liquidation support exist for that DEX. A new adapter by itself does not make a pool safe for collateral admission.

Supported Operations

• Bundle DEX-specific deposit, withdraw, and fee-collection calls into one interface layer
• Coordinate unwind or routing steps needed for liquidation execution
• Support controlled position updates such as range changes when a DEX adapter exists
• Expose a consistent integration surface without deciding collateral factors or health checks

Deployment Status

Router addresses, adapter registries, and enabled networks are deployment-specific. Verify chain-specific addresses from the published contract registry or release notes.

• Confirm the DEX adapter you rely on is enabled on the target deployment
• Router support does not mean a pool is admitted for collateral