Router Contract

Overview

The router coordinates deposits, withdrawals, fee claims, and liquidation steps through DEX-specific adapters. Each caller can use this shared execution layer instead of assembling the underlying DEX calls independently. 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

DEXs expose different methods for entering a position, removing liquidity, and collecting fees. The router connects Avana's transaction flows to those methods through a common integration layer.

Adapter Model

Each supported DEX family has an adapter for operations such as fee collection and liquidity removal. The adapter implements the calls required by that LP format, keeping DEX-specific execution separate from the rest of the transaction flow. An adapter provides execution support for an LP format. Collateral admission also requires compatible valuation and liquidation support, so deploying an adapter alone does not enable a pool for borrowing.

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