Skip to main content
Avana icon

Router Contract

Operational interface layer for venue-specific actions, adapter calls, and unwind support.

Overview

The router is an execution helper, not the protocol's central source of truth. AMM Market's core policy decisions still come from the Borrow Spoke, Hub, oracle stack, and risk framework. The router exists to make venue-specific actions easier to compose and safer to standardize.

Read this page as an operational reference. For canonical architecture, start with Borrow Spoke and Liquidation Framework.

Role in System

Different AMM venues expose different entry, exit, and fee-collection methods. The router gives Avana an integration layer for those mechanics so builders do not need to treat every venue as a bespoke one-off.

The router should never be read as the place where collateral factors, health checks, or liquidation eligibility are decided. Those remain upstream protocol concerns.

Adapter Model

Each supported venue family should have a venue-aware adapter that knows how to claim fees, remove liquidity, or otherwise expose the actions needed by the protocol. This keeps venue-specific behavior isolated instead of spreading it across every user flow.

Adapter support only matters when it aligns with valuation and liquidation support. A new adapter by itself does not make a venue safe for collateral admission.

Supported Operations

  • Bundle venue-specific deposit, withdraw, and fee-collection calls into a cleaner interface layer
  • Coordinate unwind or routing steps needed for liquidation execution
  • Support controlled position updates such as range changes or migration flows when a venue adapter exists
  • Expose a consistent integration surface without becoming the protocol's risk or valuation authority

Deployment Status

Router addresses, adapter registries, and enabled networks are deployment data and should be published with releases. This documentation intentionally avoids placeholder addresses and future-date promises.

  • • Verify chain-specific addresses from the published contract registry or release notes.
  • • Confirm that the venue adapter you rely on is enabled on the target deployment.
  • • Treat router support as an operational dependency, not as proof that a pool is admitted for collateral.